Netflix (UK): Asked me a question(American) then when I answe...
A Netflix (UK) customer review by GetHuman user ~mandy from November 28th, 2017
Background on ~mandy's case
GetHuman: ~mandy - can you tell our other Netflix (UK) customers when your case took place?
~mandy: Yeah. It was middle of the night, on November 18th.
GetHuman: Did you reach out to Netflix (UK), and if so, how?
GetHuman: And which of these common Netflix (UK) customer issues best describes the reason you wanted to talk to them?
(Shows ~mandy a list of common Netflix (UK) problems)
~mandy: "Technical Support" was why I was trying to call.
~mandy's review of Netflix (UK) customer service
GetHuman: So how would you sum up your experience for GetHuman's Netflix (UK) customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~mandy: Asked me a question(American) then when I answered kept saying hold. Arrrrgghhhhh. This happened * times. I had to repeatedly relay my problem number although saying it phonetically. Whats wrong with these people. Then gave up after ** mins. just kept putting me on hold with no explination.
GetHuman: Let's quantify your experience contacting Netflix (UK). On a scale of 1 to 5, how easy is it go get help on a Netflix (UK) problem?
~mandy: I'd give them a five out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~mandy: I'd give them a five out of five on communication.
GetHuman: And what about Netflix (UK)'s ability to quickly and effectively address your problem?
~mandy: For that I would say five out of five.
GetHuman: And finally- any advice for other Netflix (UK) customers?
~mandy: Call them early in the day or late. Don't forget any personal or account information you might need for Netflix (UK) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~mandy taken from his Netflix (UK) customer service problem that occurred on November 18th, 2017.