Green Dot: You have to choose option **, any other option...
A Green Dot customer review by GetHuman user ~anonymous from November 22nd, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other Green Dot customers when your case took place?
~anonymous: Yeah. It was morning, on November 14th.
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 ~anonymous a list of common Green Dot problems)
~anonymous: "Report a problem" was why I was trying to call.
~anonymous'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.
~anonymous: You have to choose option **, any other option will take you through unnecessary chatter then disconnect you. I had to hang up twice and call back and choose option ** in order to finally get a live person. Overall, I'm not happy with their product so I'm moving on. Good luck to you all.
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?
~anonymous: I'd give them a one 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?
~anonymous: 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?
~anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other Green Dot customers?
~anonymous: 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 ~anonymous taken from his Green Dot customer service problem that occurred on November 14th, 2017.