Yelp: We have two reviews that are not by clients and...
A Yelp customer review by GetHuman user ~Sarah from November 12th, 2017
Background on ~Sarah's case
GetHuman: ~Sarah - can you tell our other Yelp customers when your case took place?
~Sarah: Yeah. It was afternoon, on November 10th.
GetHuman: Did you reach out to Yelp, and if so, how?
GetHuman: And which of these common Yelp customer issues best describes the reason you wanted to talk to them?
(Shows ~Sarah a list of common Yelp problems)
~Sarah: "Someone is Harassing Me" was why I was trying to contact.
~Sarah's review of Yelp customer service
GetHuman: So how would you sum up your experience for GetHuman's Yelp 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.
~Sarah: We have two reviews that are not by clients and are clearly against Yelp Guidelines, yet I can not get a response to get them removed. One is by someone we know that is trying to harm our business (Julia B) and the other even states in the review that she is reviewing for someone else. Yelp states on their voice messaging service that they do not take calls and can take up to * days to fix a problem.
GetHuman: Let's quantify your experience contacting Yelp. On a scale of 1 to 5, how easy is it go get help on a Yelp problem?
~Sarah: 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?
~Sarah: I'd give them a two out of five on communication.
GetHuman: And what about Yelp's ability to quickly and effectively address your problem?
~Sarah: For that I would say one out of five.
GetHuman: And finally- any advice for other Yelp customers?
~Sarah: Call them early in the day or late. Don't forget any personal or account information you might need for Yelp to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Sarah taken from his Yelp customer service problem that occurred on November 10th, 2017.