netTALK: I was on hold for almost * hours. None of the e...
A netTALK customer review by GetHuman user GetHuman-20700 from November 24th, 2017
Background on GetHuman-20700's case
GetHuman: GetHuman-20700 - can you tell our other netTALK customers when your case took place?
GetHuman-20700: Yes I can. It was middle of the night, on November 15th.
GetHuman: Did you reach out to netTALK, and if so, how?
GetHuman: And which of these common netTALK customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-20700 a list of common netTALK problems)
GetHuman-20700: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-20700's review of netTALK customer service
GetHuman: So how would you sum up your experience for GetHuman's netTALK 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-20700: I was on hold for almost * hours. None of the extensions work save for the one for tech support and I believe there is no one there at all. You just sit on hold. They just have this just to make you think there is someone there.
GetHuman: Let's quantify your experience contacting netTALK. On a scale of 1 to 5, how easy is it go get help on a netTALK problem?
GetHuman-20700: I'd give them a two 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-20700: I'd give them a one out of five on communication.
GetHuman: And what about netTALK's ability to quickly and effectively address your problem?
GetHuman-20700: For that I would say two out of five.
GetHuman: And finally- any advice for other netTALK customers?
GetHuman-20700: Call them early in the day or late. Don't forget any personal or account information you might need for netTALK to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-20700 taken from his netTALK customer service problem that occurred on November 15th, 2017.