Sony VAIO: This has been the worst customer service of my...
A Sony VAIO customer review by GetHuman user ~mlknight77 from November 19th, 2017
Background on ~mlknight77's case
GetHuman: ~mlknight77 - can you tell our other Sony VAIO customers when your case took place?
~mlknight77: Yes. It was morning, on November 12th.
GetHuman: Did you reach out to Sony VAIO, and if so, how?
GetHuman: And which of these common Sony VAIO customer issues best describes the reason you wanted to talk to them?
(Shows ~mlknight77 a list of common Sony VAIO problems)
~mlknight77: "Warranty claim" was why I was trying to call.
~mlknight77's review of Sony VAIO customer service
GetHuman: So how would you sum up your experience for GetHuman's Sony VAIO 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.
~mlknight77: This has been the worst customer service of my life. My Vaio crashed after ** days of owning it, and Sony refused to do anything. It has crashed two more times, and Sony still refuses to take responsibility for this lemon. No one will help me or listen to me. They are horrible.
GetHuman: Let's quantify your experience contacting Sony VAIO. On a scale of 1 to 5, how easy is it go get help on a Sony VAIO problem?
~mlknight77: 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?
~mlknight77: I'd give them a three out of five on communication.
GetHuman: And what about Sony VAIO's ability to quickly and effectively address your problem?
~mlknight77: For that I would say four out of five.
GetHuman: And finally- any advice for other Sony VAIO customers?
~mlknight77: Call them early in the day or late. Don't forget any personal or account information you might need for Sony VAIO to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~mlknight77 taken from his Sony VAIO customer service problem that occurred on November 12th, 2017.