Netgear: Helpful at first, gave me solutions I had alrea...
A Netgear customer review by GetHuman user GetHuman-228691 from November 14th, 2017
Background on GetHuman-228691's case
GetHuman: GetHuman-228691 - can you tell our other Netgear customers when your case took place?
GetHuman-228691: Sure. It was morning, on November 5th.
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 GetHuman-228691 a list of common Netgear problems)
GetHuman-228691: "Device Setup" was why I was trying to call.
GetHuman-228691'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.
GetHuman-228691: Helpful at first, gave me solutions I had already tried. Then I went to terminal hold - (had their music playing on my speaker phone for an hour). Surprisingly, they had the nerve to come back on with, "sorry for your wait, can we call you back?"
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?
GetHuman-228691: 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?
GetHuman-228691: 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?
GetHuman-228691: For that I would say four out of five.
GetHuman: And finally- any advice for other Netgear customers?
GetHuman-228691: 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 GetHuman-228691 taken from his Netgear customer service problem that occurred on November 5th, 2017.