Restaurant.com: The Rest.com rep was hard to hear due to a very...
A Restaurant.com customer review by GetHuman user ~Tom from November 27th, 2017
Background on ~Tom's case
GetHuman: ~Tom - can you tell our other Restaurant.com customers when your case took place?
~Tom: Yup. It was evening, on November 26th.
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 ~Tom a list of common Restaurant.com problems)
~Tom: "Refund request" was why I was trying to call.
~Tom'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.
~Tom: The Rest.com rep was hard to hear due to a very bad connection. I did not understand her explanation, which I don't know if it was me or her or a combination. I'll try again if I can get a clean connection.
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?
~Tom: 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?
~Tom: 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?
~Tom: For that I would say three out of five.
GetHuman: And finally- any advice for other Restaurant.com customers?
~Tom: 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 ~Tom taken from his Restaurant.com customer service problem that occurred on November 26th, 2017.