Groupon: Unprofessional customer service
Groupon отзыв клиента от пользователя GetHuman GetHuman-stokesc из декабрь 1-го, 2017
Background on GetHuman-stokesc's case
GetHuman: GetHuman-stokesc - can you tell our other Groupon customers when your case took place?
GetHuman-stokesc: Yup. It was afternoon, on ноябрь 30-го.
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-stokesc a list of common Groupon problems)
GetHuman-stokesc: "Change My Order" was why I was trying to contact.
GetHuman-stokesc'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-stokesc: Unprofessional customer service
GetHuman: Can you tell the rest of us a bit more from what happened on 11/30/17?
GetHuman-stokesc: I am not happy with the unprofessional demeanour of the customer service agent I spoke with.
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-stokesc: 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?
GetHuman-stokesc: 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-stokesc: For that I would say three out of five.
GetHuman: And finally- any advice for other Groupon customers?
GetHuman-stokesc: Позвоните им рано днем или поздно. Не забывайте личную информацию или информацию об учетной записи, которая может вам понадобиться, чтобы Groupon знал, кто вы.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-stokesc taken from his Groupon customer service problem that occurred on ноябрь 30-го, 2017.