Sanyo: TV purchased had cracked screen (manufacturer d...
A Sanyo customer review by GetHuman user ~shea from November 27th, 2017
Background on ~shea's case
GetHuman: ~shea - can you tell our other Sanyo customers when your case took place?
~shea: Yup. It was middle of the night, on November 22nd.
GetHuman: Did you reach out to Sanyo, and if so, how?
GetHuman: And which of these common Sanyo customer issues best describes the reason you wanted to talk to them?
(Shows ~shea a list of common Sanyo problems)
~shea: "Technical support" was why I was trying to call.
~shea's review of Sanyo customer service
GetHuman: So how would you sum up your experience for GetHuman's Sanyo 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.
~shea: TV purchased had cracked screen (manufacturer defect). Store where purchased would not take back (more than ** days), but told to contact Sanyo. Representative told me he would forward info to headquarters and someone from hq would respond within ** hours. No response* after a week went by, I called again. Updated information from representative said there was nothing Sanyo could do.
GetHuman: Let's quantify your experience contacting Sanyo. On a scale of 1 to 5, how easy is it go get help on a Sanyo problem?
~shea: I'd give them a three 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?
~shea: I'd give them a five out of five on communication.
GetHuman: And what about Sanyo's ability to quickly and effectively address your problem?
~shea: For that I would say one out of five.
GetHuman: And finally- any advice for other Sanyo customers?
~shea: Call them early in the day or late. Don't forget any personal or account information you might need for Sanyo to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~shea taken from his Sanyo customer service problem that occurred on November 22nd, 2017.