Restaurant.com: Finally it went to a fast beep and disconnected...
A Restaurant.com customer review by GetHuman user GetHuman-290844 from November 11th, 2017
Background on GetHuman-290844's case
GetHuman: GetHuman-290844 - can you tell our other Restaurant.com customers when your case took place?
GetHuman-290844: Yes. It was afternoon, on November 10th.
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-290844 a list of common Restaurant.com problems)
GetHuman-290844: "Refund request" was why I was trying to call.
GetHuman-290844'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-290844: Finally it went to a fast beep and disconnected. Twice! Not happy, I'm again on hold, it my anniversary and it says I'm not a vaiid email address. How did I buy from you then?
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-290844: I'd give them a two 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-290844: 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?
GetHuman-290844: For that I would say two out of five.
GetHuman: And finally- any advice for other Restaurant.com customers?
GetHuman-290844: 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-290844 taken from his Restaurant.com customer service problem that occurred on November 10th, 2017.