Green Dot: Well,I have been happy with money pack.but they...
A Green Dot customer review by GetHuman user GetHuman-376972 from November 24th, 2017
Background on GetHuman-376972's case
GetHuman: GetHuman-376972 - can you tell our other Green Dot customers when your case took place?
GetHuman-376972: Yeah. It was middle of the night, on November 21st.
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-376972 a list of common Green Dot problems)
GetHuman-376972: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-376972'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-376972: Well,I have been happy with money pack.but they stop having numbers.how I can load my paypall account now.hope they help on that .please visit my blog for great incomome working at home http:**facebook-chat.com
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-376972: 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-376972: 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?
GetHuman-376972: For that I would say four out of five.
GetHuman: And finally- any advice for other Green Dot customers?
GetHuman-376972: 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-376972 taken from his Green Dot customer service problem that occurred on November 21st, 2017.