Groupon: I waited on the phone for over ** minutes and n...
A Groupon customer review by GetHuman user GetHuman-199255 from November 25th, 2017
Background on GetHuman-199255's case
GetHuman: GetHuman-199255 - can you tell our other Groupon customers when your case took place?
GetHuman-199255: Yes I can. It was middle of the night, on November 20th.
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-199255 a list of common Groupon problems)
GetHuman-199255: "Update Account Info" was why I was trying to contact.
GetHuman-199255'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-199255: I waited on the phone for over ** minutes and no one answered so I hung up. I usually have great experiences with Groupon, the the customer service via email isn't much better. He basically told me to contact the company directly. WTH?
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-199255: I'd give them a five 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-199255: I'd give them a four out of five on communication.
GetHuman: And what about Groupon's ability to quickly and effectively address your problem?
GetHuman-199255: For that I would say one out of five.
GetHuman: And finally- any advice for other Groupon customers?
GetHuman-199255: 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-199255 taken from his Groupon customer service problem that occurred on November 20th, 2017.