NET 10: OK I cant find how to edit my previous review...
A NET 10 customer review by GetHuman user ~puppyskunky from November 28th, 2017
Background on ~puppyskunky's case
GetHuman: ~puppyskunky - can you tell our other NET 10 customers when your case took place?
~puppyskunky: Sure. It was afternoon, on November 24th.
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 ~puppyskunky a list of common NET 10 problems)
~puppyskunky: "Complaint" was why I was trying to call.
~puppyskunky'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.
~puppyskunky: OK I cant find how to edit my previous review, so let me write a new review. I was calling *** not ***. my bad!! sorry. when i called *** I reached someone fairly quickly. She wasnt able to resolve my problem, but she tried and was pleasant. She said a tech would contact me and fix the issue within ** hrs. We will see.
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?
~puppyskunky: I'd give them a four 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?
~puppyskunky: I'd give them a five out of five on communication.
GetHuman: And what about NET 10's ability to quickly and effectively address your problem?
~puppyskunky: For that I would say two out of five.
GetHuman: And finally- any advice for other NET 10 customers?
~puppyskunky: 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 ~puppyskunky taken from his NET 10 customer service problem that occurred on November 24th, 2017.