Belkin: Being on the phone for ** minutes with someone...
A Belkin customer review by GetHuman user GetHuman-234891 from November 13th, 2017
Background on GetHuman-234891's case
GetHuman: GetHuman-234891 - can you tell our other Belkin customers when your case took place?
GetHuman-234891: Sure. It was morning, on November 9th.
GetHuman: Did you reach out to Belkin, and if so, how?
GetHuman: And which of these common Belkin customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-234891 a list of common Belkin problems)
GetHuman-234891: "None of those really matches why I wanted to call Belkin that day." was why I was trying to call.
GetHuman-234891's review of Belkin customer service
GetHuman: So how would you sum up your experience for GetHuman's Belkin 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-234891: Being on the phone for ** minutes with someone who doesn't listen to exactly what is wrong, is why using non-technical people for issues just doesn't work. What an embarrassment for Belkin. I will not buy anything from them again
GetHuman: Let's quantify your experience contacting Belkin. On a scale of 1 to 5, how easy is it go get help on a Belkin problem?
GetHuman-234891: I'd give them a five 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-234891: I'd give them a four out of five on communication.
GetHuman: And what about Belkin's ability to quickly and effectively address your problem?
GetHuman-234891: For that I would say three out of five.
GetHuman: And finally- any advice for other Belkin customers?
GetHuman-234891: Call them early in the day or late. Don't forget any personal or account information you might need for Belkin to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-234891 taken from his Belkin customer service problem that occurred on November 9th, 2017.