LivingSocial: I did not have to wait for a rep to answer my c...
A LivingSocial customer review by GetHuman user ~4happypups from November 27th, 2017
Background on ~4happypups's case
GetHuman: ~4happypups - can you tell our other LivingSocial customers when your case took place?
~4happypups: Yeah. It was middle of the night, on November 25th.
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 ~4happypups a list of common LivingSocial problems)
~4happypups: "Lower my bill" was why I was trying to call.
~4happypups'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.
~4happypups: I did not have to wait for a rep to answer my call* however, it did take ** minutes for the rep to handle the administrative processing. All was good and I was very pleased with the rep. Happy to have this number!
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?
~4happypups: 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?
~4happypups: I'd give them a one out of five on communication.
GetHuman: And what about LivingSocial's ability to quickly and effectively address your problem?
~4happypups: For that I would say two out of five.
GetHuman: And finally- any advice for other LivingSocial customers?
~4happypups: 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 ~4happypups taken from his LivingSocial customer service problem that occurred on November 25th, 2017.