Netspend: was scheduled to receive a call back at *:**a a...
A Netspend customer review by GetHuman user ~smplysuces from November 23rd, 2017
Background on ~smplysuces's case
GetHuman: ~smplysuces - can you tell our other Netspend customers when your case took place?
~smplysuces: Yup. It was middle of the night, on November 19th.
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 ~smplysuces a list of common Netspend problems)
~smplysuces: "Account Access" was why I was trying to call.
~smplysuces'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.
~smplysuces: was scheduled to receive a call back at *:**a and i never received a call when i called back the machine stated it notices i am scheduled to receive a call back **min from my initial time give when i called at *:**a, so irritated that it takes so long just to speak with someone
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?
~smplysuces: 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?
~smplysuces: I'd give them a four out of five on communication.
GetHuman: And what about Netspend's ability to quickly and effectively address your problem?
~smplysuces: For that I would say three out of five.
GetHuman: And finally- any advice for other Netspend customers?
~smplysuces: 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 ~smplysuces taken from his Netspend customer service problem that occurred on November 19th, 2017.