Groupon: I held for *** minuets to be told my problem wa...
A Groupon customer review by GetHuman user GetHuman-315380 from November 26th, 2017
Background on GetHuman-315380's case
GetHuman: GetHuman-315380 - can you tell our other Groupon customers when your case took place?
GetHuman-315380: Yes I can. It was afternoon, on November 25th.
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-315380 a list of common Groupon problems)
GetHuman-315380: "Update Account Info" was why I was trying to contact.
GetHuman-315380'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-315380: I held for *** minuets to be told my problem was resolved when in reality no changes were made and I have to start over. Also they close at *pm central time, which means mountain time I have no choice but to call on lunch or not at all.
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-315380: 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-315380: I'd give them a five out of five on communication.
GetHuman: And what about Groupon's ability to quickly and effectively address your problem?
GetHuman-315380: For that I would say four out of five.
GetHuman: And finally- any advice for other Groupon customers?
GetHuman-315380: 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-315380 taken from his Groupon customer service problem that occurred on November 25th, 2017.