NET 10: got thru ok, but kept getting transferred to an...
Una recensione del cliente NET 10 da parte dell'utente GetHuman ~screenname da novembre 27º, 2017
Background on ~screenname's case
GetHuman: ~screenname - can you tell our other NET 10 customers when your case took place?
~screenname: Yes I can. It was morning, on novembre 22º.
GetHuman: Did you reach out to NET 10, and if so, how?
GetHuman: And which of these common NET 10 customer issues best describes the reason you wanted to talk to them?
(Shows ~screenname a list of common NET 10 problems)
~screenname: "Technical support" was why I was trying to call.
~screenname's review of NET 10 customer service
GetHuman: So how would you sum up your experience for GetHuman's NET 10 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.
~screenname: got thru ok, but kept getting transferred to another dept* no one had an answer for what to do when the phone I bot from them didn't work* spoke to * different persons and had to explain same thing over and over* had to give my address*details to * persons because of "system" error* just wasted * hours of my time
GetHuman: Let's quantify your experience contacting NET 10. On a scale of 1 to 5, how easy is it go get help on a NET 10 problem?
~screenname: I'd give them a three 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?
~screenname: I'd give them a four out of five on communication.
GetHuman: And what about NET 10's ability to quickly and effectively address your problem?
~screenname: For that I would say five out of five.
GetHuman: And finally- any advice for other NET 10 customers?
~screenname: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per NET 10 sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~screenname taken from his NET 10 customer service problem that occurred on novembre 22º, 2017.