Green Dot: my card was blocked because a merchant screwd u...
A Green Dot customer review by GetHuman user ~outofluck from November 22nd, 2017
Background on ~outofluck's case
GetHuman: ~outofluck - can you tell our other Green Dot customers when your case took place?
~outofluck: Sure. It was morning, on November 20th.
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 ~outofluck a list of common Green Dot problems)
~outofluck: "Card Activation" was why I was trying to call.
~outofluck'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.
~outofluck: my card was blocked because a merchant screwd up while reloading the card. i can never have a greendot card again. if you want to speak to a real person go through the prompt" refund card " but otherwise a worthless company who sells your personal information to *rd party companies, dont get one
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?
~outofluck: 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?
~outofluck: I'd give them a one out of five on communication.
GetHuman: And what about Green Dot's ability to quickly and effectively address your problem?
~outofluck: For that I would say four out of five.
GetHuman: And finally- any advice for other Green Dot customers?
~outofluck: 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 ~outofluck taken from his Green Dot customer service problem that occurred on November 20th, 2017.