Green Dot: My card was blocked from loading some cash on t...
A Green Dot customer review by GetHuman user GetHuman-392502 from November 20th, 2017
Background on GetHuman-392502's case
GetHuman: GetHuman-392502 - can you tell our other Green Dot customers when your case took place?
GetHuman-392502: Yeah. It was afternoon, on November 17th.
GetHuman: Did you reach out to Green Dot, and if so, how?
GetHuman: And which of these common Green Dot customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-392502 a list of common Green Dot problems)
GetHuman-392502: "Technical support" was why I was trying to call.
GetHuman-392502's review of Green Dot customer service
GetHuman: So how would you sum up your experience for GetHuman's Green Dot 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.
GetHuman-392502: My card was blocked from loading some cash on to it. The website & agent I spoke with repeated the same thing-just that it was blocked, and I can no longer use any G.D. account. Was like speaking to a robot.
GetHuman: Let's quantify your experience contacting Green Dot. On a scale of 1 to 5, how easy is it go get help on a Green Dot problem?
GetHuman-392502: I'd give them a two 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?
GetHuman-392502: I'd give them a three out of five on communication.
GetHuman: And what about Green Dot's ability to quickly and effectively address your problem?
GetHuman-392502: For that I would say four out of five.
GetHuman: And finally- any advice for other Green Dot customers?
GetHuman-392502: Call them early in the day or late. Don't forget any personal or account information you might need for Green Dot to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-392502 taken from his Green Dot customer service problem that occurred on November 17th, 2017.