NET 10: Call was never answered... Net** has done a fin...
A NET 10 customer review by GetHuman user ~Digruntled Angry Customer from November 15th, 2017
Background on ~Digruntled Angry Customer's case
GetHuman: ~Digruntled Angry Customer - can you tell our other NET 10 customers when your case took place?
~Digruntled Angry Customer: Yes. It was morning, on November 6th.
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 ~Digruntled Angry Customer a list of common NET 10 problems)
~Digruntled Angry Customer: "Refund" was why I was trying to call.
~Digruntled Angry Customer'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.
~Digruntled Angry Customer: Call was never answered... Net** has done a fine job of downgrading their customer service. I guess their customers don't matter - typical of many businesses these days.
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?
~Digruntled Angry Customer: 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?
~Digruntled Angry Customer: 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?
~Digruntled Angry Customer: For that I would say two out of five.
GetHuman: And finally- any advice for other NET 10 customers?
~Digruntled Angry Customer: 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 ~Digruntled Angry Customer taken from his NET 10 customer service problem that occurred on November 6th, 2017.