Restaurant.com: I was discouraged by the many negative comments...
A Restaurant.com customer review by GetHuman user ~Optimist from November 14th, 2017
Background on ~Optimist's case
GetHuman: ~Optimist - can you tell our other Restaurant.com customers when your case took place?
~Optimist: Sure. It was afternoon, on November 8th.
GetHuman: Did you reach out to Restaurant.com, and if so, how?
GetHuman: And which of these common Restaurant.com customer issues best describes the reason you wanted to talk to them?
(Shows ~Optimist a list of common Restaurant.com problems)
~Optimist: "Complaint" was why I was trying to call.
~Optimist's review of Restaurant.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Restaurant.com 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.
~Optimist: I was discouraged by the many negative comments but decided to wait it out! Idris answered all my questions and did an excellent job taking care of my problem. I don't usually post but felt I need to share a pleasant experience. GOOD job!!!!!!
GetHuman: Let's quantify your experience contacting Restaurant.com. On a scale of 1 to 5, how easy is it go get help on a Restaurant.com problem?
~Optimist: I'd give them a four 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?
~Optimist: I'd give them a five out of five on communication.
GetHuman: And what about Restaurant.com's ability to quickly and effectively address your problem?
~Optimist: For that I would say two out of five.
GetHuman: And finally- any advice for other Restaurant.com customers?
~Optimist: Call them early in the day or late. Don't forget any personal or account information you might need for Restaurant.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Optimist taken from his Restaurant.com customer service problem that occurred on November 8th, 2017.