Restaurant.com: Auto message stated the hours, then proceeded t...
A Restaurant.com customer review by GetHuman user ~stranoization from November 23rd, 2017
Background on ~stranoization's case
GetHuman: ~stranoization - can you tell our other Restaurant.com customers when your case took place?
~stranoization: Yes I can. It was evening, on November 19th.
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 ~stranoization a list of common Restaurant.com problems)
~stranoization: "Setup service" was why I was trying to call.
~stranoization'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.
~stranoization: Auto message stated the hours, then proceeded to redirect the caller (me) to the company website's FAQ section, then call was disconnected. Horrible service!
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?
~stranoization: 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?
~stranoization: I'd give them a one out of five on communication.
GetHuman: And what about Restaurant.com's ability to quickly and effectively address your problem?
~stranoization: For that I would say five out of five.
GetHuman: And finally- any advice for other Restaurant.com customers?
~stranoization: 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 ~stranoization taken from his Restaurant.com customer service problem that occurred on November 19th, 2017.