Netgear: their number now comes back as non working, cal...
A Netgear customer review by GetHuman user ~angry custoemr from November 23rd, 2017
Background on ~angry custoemr's case
GetHuman: ~angry custoemr - can you tell our other Netgear customers when your case took place?
~angry custoemr: Yeah. It was afternoon, on November 16th.
GetHuman: Did you reach out to Netgear, and if so, how?
GetHuman: And which of these common Netgear customer issues best describes the reason you wanted to talk to them?
(Shows ~angry custoemr a list of common Netgear problems)
~angry custoemr: "Account Access" was why I was trying to call.
~angry custoemr's review of Netgear customer service
GetHuman: So how would you sum up your experience for GetHuman's Netgear 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.
~angry custoemr: their number now comes back as non working, call their business support line and got stuck in an endless loop of press * for tech support then it redials to the main menu. chat support is no help keep being disconnected after waiting in line.
GetHuman: Let's quantify your experience contacting Netgear. On a scale of 1 to 5, how easy is it go get help on a Netgear problem?
~angry custoemr: 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?
~angry custoemr: I'd give them a one out of five on communication.
GetHuman: And what about Netgear's ability to quickly and effectively address your problem?
~angry custoemr: For that I would say one out of five.
GetHuman: And finally- any advice for other Netgear customers?
~angry custoemr: Call them early in the day or late. Don't forget any personal or account information you might need for Netgear to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~angry custoemr taken from his Netgear customer service problem that occurred on November 16th, 2017.