Groupon: I was placed in the virtual hold line so I left...
A Groupon customer review by GetHuman user ~Groupon customer from November 27th, 2017
Background on ~Groupon customer's case
GetHuman: ~Groupon customer - can you tell our other Groupon customers when your case took place?
~Groupon customer: Sure. It was middle of the night, on November 23rd.
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 ~Groupon customer a list of common Groupon problems)
~Groupon customer: "Fraud" was why I was trying to contact.
~Groupon customer'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.
~Groupon customer: I was placed in the virtual hold line so I left my number and they called me back. That was great. We had my problem resolved within seconds. It took me more than * days to try to fix the problem over email support.
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?
~Groupon customer: 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?
~Groupon customer: 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?
~Groupon customer: For that I would say five out of five.
GetHuman: And finally- any advice for other Groupon customers?
~Groupon customer: Try to deal with them early in the day or later. 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 ~Groupon customer taken from his Groupon customer service problem that occurred on November 23rd, 2017.