Restaurant.com: Gentleman this time. Same horrible background n...
A Restaurant.com customer review by GetHuman user ~Hungry from November 25th, 2017
Background on ~Hungry's case
GetHuman: ~Hungry - can you tell our other Restaurant.com customers when your case took place?
~Hungry: Yup. It was afternoon, on November 22nd.
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 ~Hungry a list of common Restaurant.com problems)
~Hungry: "Cancel service" was why I was trying to call.
~Hungry'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.
~Hungry: Gentleman this time. Same horrible background noise. Was told that since I purchased through Offers.com I had to contact them. I explained that my bank statement says Restaurants.com??? He stated that they are a *rd party and have nothing to do with it. Again???
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?
~Hungry: 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?
~Hungry: I'd give them a two out of five on communication.
GetHuman: And what about Restaurant.com's ability to quickly and effectively address your problem?
~Hungry: For that I would say three out of five.
GetHuman: And finally- any advice for other Restaurant.com customers?
~Hungry: 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 ~Hungry taken from his Restaurant.com customer service problem that occurred on November 22nd, 2017.