VIZIO: ill never buy again bought **inch * months ago...
A VIZIO customer review by GetHuman user GetHuman-291447 from November 26th, 2017
Background on GetHuman-291447's case
GetHuman: GetHuman-291447 - can you tell our other VIZIO customers when your case took place?
GetHuman-291447: Yeah. It was late at night, on November 18th.
GetHuman: Did you reach out to VIZIO, and if so, how?
GetHuman: And which of these common VIZIO customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-291447 a list of common VIZIO problems)
GetHuman-291447: "Complaint" was why I was trying to call.
GetHuman-291447's review of VIZIO customer service
GetHuman: So how would you sum up your experience for GetHuman's VIZIO 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.
GetHuman-291447: ill never buy again bought **inch * months ago and broke you want to give me a reconditioned one in * to ** days REALLY they said my warranty starts before I even bought it REALLY wait till I get on social media had no trouble with other brands I spend ****$ on yours pure junk
GetHuman: Let's quantify your experience contacting VIZIO. On a scale of 1 to 5, how easy is it go get help on a VIZIO problem?
GetHuman-291447: 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?
GetHuman-291447: I'd give them a five out of five on communication.
GetHuman: And what about VIZIO's ability to quickly and effectively address your problem?
GetHuman-291447: For that I would say three out of five.
GetHuman: And finally- any advice for other VIZIO customers?
GetHuman-291447: Call them early in the day or late. Don't forget any personal or account information you might need for VIZIO to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-291447 taken from his VIZIO customer service problem that occurred on November 18th, 2017.