Groupon: After waiting ** minutes, the answer they gave...
Groupon Ulasan pelanggan oleh pengguna GetHuman GetHuman-316305 dari November 26, 2017
Background on GetHuman-316305's case
GetHuman: GetHuman-316305 - can you tell our other Groupon customers when your case took place?
GetHuman-316305: Yes I can. It was morning, on November 23.
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-316305 a list of common Groupon problems)
GetHuman-316305: "Voucher Code Won't Work" was why I was trying to contact.
GetHuman-316305'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-316305: After waiting ** minutes, the answer they gave me was the same I had from the website. The impression that I get is that after they make the sale , it's not their problem anymore. For sure it's going to be my last purchase from them.
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-316305: 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-316305: 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-316305: For that I would say five out of five.
GetHuman: And finally- any advice for other Groupon customers?
GetHuman-316305: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Groupon mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-316305 taken from his Groupon customer service problem that occurred on November 23, 2017.