Restaurant.com: Phone customer service was great. Email custom...
A Restaurant.com customer review by GetHuman user GetHuman-260349 from November 26th, 2017
Background on GetHuman-260349's case
GetHuman: GetHuman-260349 - can you tell our other Restaurant.com customers when your case took place?
GetHuman-260349: Yes. 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 GetHuman-260349 a list of common Restaurant.com problems)
GetHuman-260349: "Update account information" was why I was trying to call.
GetHuman-260349'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.
GetHuman-260349: Phone customer service was great. Email customer service is non-existent, waited for * months for a response before I decided to look up a phone number.
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?
GetHuman-260349: 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?
GetHuman-260349: 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?
GetHuman-260349: For that I would say one out of five.
GetHuman: And finally- any advice for other Restaurant.com customers?
GetHuman-260349: 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 GetHuman-260349 taken from his Restaurant.com customer service problem that occurred on November 19th, 2017.