NET 10: He could not help me because a perverted and na...
A NET 10 customer review by GetHuman user ~ravhnt from November 23rd, 2017
Background on ~ravhnt's case
GetHuman: ~ravhnt - can you tell our other NET 10 customers when your case took place?
~ravhnt: Yes I can. It was evening, on November 21st.
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 ~ravhnt a list of common NET 10 problems)
~ravhnt: "Overcharge on Account" was why I was trying to call.
~ravhnt'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.
~ravhnt: He could not help me because a perverted and nasty man is emailing my ** year old son sin he had this phone in January and sending him pictures of his gentials and this is distrubing, Net** rep told me they can not trace the person number and you guys issue the phone out and we have service with you. No help. And I filed a police report and Net** cant seem to help.
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?
~ravhnt: 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?
~ravhnt: I'd give them a one out of five on communication.
GetHuman: And what about NET 10's ability to quickly and effectively address your problem?
~ravhnt: For that I would say five out of five.
GetHuman: And finally- any advice for other NET 10 customers?
~ravhnt: 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 ~ravhnt taken from his NET 10 customer service problem that occurred on November 21st, 2017.