Netgear: My call was answered right away, but I could ba...
A Netgear customer review by GetHuman user ~Lizzie from November 23rd, 2017
Background on ~Lizzie's case
GetHuman: ~Lizzie - can you tell our other Netgear customers when your case took place?
~Lizzie: Yup. It was evening, on November 18th.
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 ~Lizzie a list of common Netgear problems)
~Lizzie: "Service problem" was why I was trying to call.
~Lizzie'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.
~Lizzie: My call was answered right away, but I could barely understand the man on the other line. And since I've had my router for more than ** days, he refused to help me without purchasing a protection plan. For the cost of the router, I expect it to last and not be roped into paying more money just to fix an issue. I haven't even had my router for a year!
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?
~Lizzie: I'd give them a four 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?
~Lizzie: I'd give them a three out of five on communication.
GetHuman: And what about Netgear's ability to quickly and effectively address your problem?
~Lizzie: For that I would say four out of five.
GetHuman: And finally- any advice for other Netgear customers?
~Lizzie: 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 ~Lizzie taken from his Netgear customer service problem that occurred on November 18th, 2017.