NET 10: They couldn't resolve my issue, which was getti...
A NET 10 customer review by GetHuman user ~Anonymous from November 20th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other NET 10 customers when your case took place?
~Anonymous: Yes I can. It was evening, on November 12th.
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 ~Anonymous a list of common NET 10 problems)
~Anonymous: "Overcharge on Account" was why I was trying to call.
~Anonymous'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.
~Anonymous: They couldn't resolve my issue, which was getting my phone reactivated. I was switched to multiple different representatives and spent * hours on the phone total. I still don't have my problem solved. They told me to call back later, which now I can't get to a live person because my "phone number is invalid"
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?
~Anonymous: 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?
~Anonymous: I'd give them a two out of five on communication.
GetHuman: And what about NET 10's ability to quickly and effectively address your problem?
~Anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other NET 10 customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for NET 10 to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his NET 10 customer service problem that occurred on November 12th, 2017.