Netspend: I was on the phone for aleast ** mins speaking...
A Netspend customer review by GetHuman user ~mrs.faithful from November 14th, 2017
Background on ~mrs.faithful's case
GetHuman: ~mrs.faithful - can you tell our other Netspend customers when your case took place?
~mrs.faithful: Sure. It was evening, on November 10th.
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 ~mrs.faithful a list of common Netspend problems)
~mrs.faithful: "Complaint" was why I was trying to call.
~mrs.faithful'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.
~mrs.faithful: I was on the phone for aleast ** mins speaking to the representative. About the same issue and what make it so bad he kept going in circles. Right then I knew that conversation wasn't going anywhere. So I ask for a manager no questions ask the issue was resolve.
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?
~mrs.faithful: 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?
~mrs.faithful: I'd give them a two out of five on communication.
GetHuman: And what about Netspend's ability to quickly and effectively address your problem?
~mrs.faithful: For that I would say three out of five.
GetHuman: And finally- any advice for other Netspend customers?
~mrs.faithful: 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 ~mrs.faithful taken from his Netspend customer service problem that occurred on November 10th, 2017.