I cancelled a groupon but I noticed it still sh...
A Groupon customer review by GetHuman user ~GrouponFriend from November 26th, 2017
Background on ~GrouponFriend's case
GetHuman: ~GrouponFriend - can you tell our other Groupon customers when your case took place?
~GrouponFriend: Yes. It was late at night, on November 18th.
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 ~GrouponFriend a list of common Groupon problems)
~GrouponFriend: "Update Account Info" was why I was trying to contact.
~GrouponFriend'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.
~GrouponFriend: I cancelled a groupon but I noticed it still showed up on my account, so I called, and the customer service rep was very nice, and friendly. She confirmed that the groupons were cancelled and told me to wait *-* days to see the money returned to my account.
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?
~GrouponFriend: I'd give them a three 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?
~GrouponFriend: 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?
~GrouponFriend: For that I would say five out of five.
GetHuman: And finally- any advice for other Groupon customers?
~GrouponFriend: 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 ~GrouponFriend taken from his Groupon customer service problem that occurred on November 18th, 2017.