Asus: my *mth old zenbook screen went white. they ask...
A Asus customer review by GetHuman user ~jared from November 19th, 2017
Background on ~jared's case
GetHuman: ~jared - can you tell our other Asus customers when your case took place?
~jared: Yes. It was morning, on November 14th.
GetHuman: Did you reach out to Asus, and if so, how?
GetHuman: And which of these common Asus customer issues best describes the reason you wanted to talk to them?
(Shows ~jared a list of common Asus problems)
~jared: "Warranty claim" was why I was trying to call.
~jared's review of Asus customer service
GetHuman: So how would you sum up your experience for GetHuman's Asus 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.
~jared: my *mth old zenbook screen went white. they asked for an invoice as a jpeg. then a pdf, then a fax. each process took days. i still didnt get past the first guy. meanwhile the service dept is demanding money for the repairs. the people you talk to first are supervisors so when you ask to talk to a supervisor they put you on hold and the same person comes back. DO NOT BUY ASUS, they do not honor their warranty.
GetHuman: Let's quantify your experience contacting Asus. On a scale of 1 to 5, how easy is it go get help on a Asus problem?
~jared: 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?
~jared: I'd give them a five out of five on communication.
GetHuman: And what about Asus's ability to quickly and effectively address your problem?
~jared: For that I would say two out of five.
GetHuman: And finally- any advice for other Asus customers?
~jared: Call them early in the day or late. Don't forget any personal or account information you might need for Asus to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jared taken from his Asus customer service problem that occurred on November 14th, 2017.