Groupon: On hold ** minutes, when told *-*. No one ever...
A Groupon customer review by GetHuman user GetHuman-226166 from November 25th, 2017
Background on GetHuman-226166's case
GetHuman: GetHuman-226166 - can you tell our other Groupon customers when your case took place?
GetHuman-226166: Sure. It was middle of the night, on November 21st.
GetHuman: Did you reach out to Groupon, and if so, how?
GetHuman: And which of these common Groupon customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-226166 a list of common Groupon problems)
GetHuman-226166: "Technical support" was why I was trying to contact.
GetHuman-226166's review of Groupon customer service
GetHuman: So how would you sum up your experience for GetHuman's Groupon 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-226166: On hold ** minutes, when told *-*. No one ever answered. Had to hang up when my battery died. Called back requesting a call return... * days later and still nothing. I wouldn't bother, except this was agift. I will never spend my money here!
GetHuman: Let's quantify your experience contacting Groupon. On a scale of 1 to 5, how easy is it go get help on a Groupon problem?
GetHuman-226166: I'd give them a four 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-226166: I'd give them a one out of five on communication.
GetHuman: And what about Groupon's ability to quickly and effectively address your problem?
GetHuman-226166: For that I would say five out of five.
GetHuman: And finally- any advice for other Groupon customers?
GetHuman-226166: Call them early in the day or late. Don't forget any personal or account information you might need for Groupon to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-226166 taken from his Groupon customer service problem that occurred on November 21st, 2017.