LivingSocial: To complain about meal deal
A LivingSocial customer review by GetHuman user GetHuman-sueatty from November 30th, 2017
Background on GetHuman-sueatty's case
GetHuman: GetHuman-sueatty - can you tell our other LivingSocial customers when your case took place?
GetHuman-sueatty: Yes. It was morning, on November 28th.
GetHuman: Did you reach out to LivingSocial, and if so, how?
GetHuman: And which of these common LivingSocial customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-sueatty a list of common LivingSocial problems)
GetHuman-sueatty: "Complaint" was why I was trying to call.
GetHuman-sueatty's review of LivingSocial customer service
GetHuman: So how would you sum up your experience for GetHuman's LivingSocial 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-sueatty: To complain about meal deal
GetHuman: Can you tell the rest of us a bit more from what happened on 11/28/17?
GetHuman-sueatty: we had meal deal for Grain Store in Wolverhampton - went last night and it was dreadful
GetHuman: Let's quantify your experience contacting LivingSocial. On a scale of 1 to 5, how easy is it go get help on a LivingSocial problem?
GetHuman-sueatty: 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-sueatty: I'd give them a two out of five on communication.
GetHuman: And what about LivingSocial's ability to quickly and effectively address your problem?
GetHuman-sueatty: For that I would say one out of five.
GetHuman: And finally- any advice for other LivingSocial customers?
GetHuman-sueatty: Call them early in the day or late. Don't forget any personal or account information you might need for LivingSocial to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-sueatty taken from his LivingSocial customer service problem that occurred on November 28th, 2017.