Sony: Spoke with Mia (?Mie)... could not understand h...
A Sony customer review by GetHuman user ~NoHelpFrom Sony from November 25th, 2017
Background on ~NoHelpFrom Sony's case
GetHuman: ~NoHelpFrom Sony - can you tell our other Sony customers when your case took place?
~NoHelpFrom Sony: Sure. It was late at night, on November 16th.
GetHuman: Did you reach out to Sony, and if so, how?
GetHuman: And which of these common Sony customer issues best describes the reason you wanted to talk to them?
(Shows ~NoHelpFrom Sony a list of common Sony problems)
~NoHelpFrom Sony: "Complaint" was why I was trying to call.
~NoHelpFrom Sony's review of Sony customer service
GetHuman: So how would you sum up your experience for GetHuman's Sony 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.
~NoHelpFrom Sony: Spoke with Mia (?Mie)... could not understand her, kept having to ask to speak slowly, but not much help. She was NOT able to tell me how to get our Wireless Internet conx back on our Blu Ray... all of a sudden no conx. SHE HUNG UP ON ME AFTER ** MIN!!! Will NEVER BUY SONY AGAIN!
GetHuman: Let's quantify your experience contacting Sony. On a scale of 1 to 5, how easy is it go get help on a Sony problem?
~NoHelpFrom Sony: I'd give them a two 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?
~NoHelpFrom Sony: I'd give them a five out of five on communication.
GetHuman: And what about Sony's ability to quickly and effectively address your problem?
~NoHelpFrom Sony: For that I would say one out of five.
GetHuman: And finally- any advice for other Sony customers?
~NoHelpFrom Sony: Call them early in the day or late. Don't forget any personal or account information you might need for Sony to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~NoHelpFrom Sony taken from his Sony customer service problem that occurred on November 16th, 2017.