Netspend: This company does not listen to the customers...
A Netspend customer review by GetHuman user ~Chilly from November 28th, 2017
Background on ~Chilly's case
GetHuman: ~Chilly - can you tell our other Netspend customers when your case took place?
~Chilly: Yup. It was late at night, on November 22nd.
GetHuman: Did you reach out to Netspend, and if so, how?
GetHuman: And which of these common Netspend customer issues best describes the reason you wanted to talk to them?
(Shows ~Chilly a list of common Netspend problems)
~Chilly: "Technical Support" was why I was trying to call.
~Chilly's review of Netspend customer service
GetHuman: So how would you sum up your experience for GetHuman's Netspend 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.
~Chilly: This company does not listen to the customers. If you dispute a transaction they hit any transaction they want not the one you are requesting. Then I call this number and if you do not have the proper extension you have to leave a voice mail. Which I did, but I doubt they will call back. I will be cancelling this card very soon. It is not worth it.
GetHuman: Let's quantify your experience contacting Netspend. On a scale of 1 to 5, how easy is it go get help on a Netspend problem?
~Chilly: 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?
~Chilly: I'd give them a five out of five on communication.
GetHuman: And what about Netspend's ability to quickly and effectively address your problem?
~Chilly: For that I would say four out of five.
GetHuman: And finally- any advice for other Netspend customers?
~Chilly: Call them early in the day or late. Don't forget any personal or account information you might need for Netspend to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Chilly taken from his Netspend customer service problem that occurred on November 22nd, 2017.