netTALK: I was on hold for ** minutes and an automated p...
A netTALK customer review by GetHuman user ~ladyofspirit from November 14th, 2017
Background on ~ladyofspirit's case
GetHuman: ~ladyofspirit - can you tell our other netTALK customers when your case took place?
~ladyofspirit: Yeah. It was morning, on November 6th.
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 ~ladyofspirit a list of common netTALK problems)
~ladyofspirit: "Complaint" was why I was trying to call.
~ladyofspirit'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.
~ladyofspirit: I was on hold for ** minutes and an automated person came on the line several times telling me what order my calls was and how long I had to wait then when it became my turn to be serviced the phone disconnected. I am calling again hopefully my call will not be disconnected this time.
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?
~ladyofspirit: I'd give them a one 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?
~ladyofspirit: 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?
~ladyofspirit: For that I would say one out of five.
GetHuman: And finally- any advice for other netTALK customers?
~ladyofspirit: 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 ~ladyofspirit taken from his netTALK customer service problem that occurred on November 6th, 2017.