Gateway Computers: I used *-*** *. I found the ID * automated res...
A Gateway Computers customer review by GetHuman user ~Dee from November 23rd, 2017
Background on ~Dee's case
GetHuman: ~Dee - can you tell our other Gateway Computers customers when your case took place?
~Dee: Sure. It was morning, on November 15th.
GetHuman: Did you reach out to Gateway Computers, and if so, how?
GetHuman: And which of these common Gateway Computers customer issues best describes the reason you wanted to talk to them?
(Shows ~Dee a list of common Gateway Computers problems)
~Dee: "Warranty claim" was why I was trying to call.
~Dee's review of Gateway Computers customer service
GetHuman: So how would you sum up your experience for GetHuman's Gateway Computers 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.
~Dee: I used *-*** *. I found the ID * automated response was seeking, input it, and the response said: "This ID is not supported by Acer." It hung up. Tried again, hung up. Then used "chat line", they quoted me the same phone *!!! Chat line also didn't help w*problem.
GetHuman: Let's quantify your experience contacting Gateway Computers. On a scale of 1 to 5, how easy is it go get help on a Gateway Computers problem?
~Dee: I'd give them a one 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?
~Dee: I'd give them a four out of five on communication.
GetHuman: And what about Gateway Computers's ability to quickly and effectively address your problem?
~Dee: For that I would say five out of five.
GetHuman: And finally- any advice for other Gateway Computers customers?
~Dee: Call them early in the day or late. Don't forget any personal or account information you might need for Gateway Computers to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Dee taken from his Gateway Computers customer service problem that occurred on November 15th, 2017.