IHOP Restaurants: We had a rare moment for a date, and only had...
A IHOP Restaurants customer review by GetHuman user ~0305 from November 4th, 2017
Background on ~0305's case
GetHuman: ~0305 - can you tell our other IHOP Restaurants customers when your case took place?
~0305: Yes. It was evening, on October 30th.
GetHuman: Did you reach out to IHOP Restaurants, and if so, how?
GetHuman: And which of these common IHOP Restaurants customer issues best describes the reason you wanted to talk to them?
(Shows ~0305 a list of common IHOP Restaurants problems)
~0305: "Complaint" was why I was trying to call.
~0305's review of IHOP Restaurants customer service
GetHuman: So how would you sum up your experience for GetHuman's IHOP Restaurants 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.
~0305: We had a rare moment for a date, and only had * hours. We sat down, ordered our drinks in the restaurant that wasn't even *** full, and proceeded to wait *** minutes for food that never came. We eventually had to get up and leave and go eat at another restaurant next door.
GetHuman: Let's quantify your experience contacting IHOP Restaurants. On a scale of 1 to 5, how easy is it go get help on a IHOP Restaurants problem?
~0305: I'd give them a three 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?
~0305: I'd give them a one out of five on communication.
GetHuman: And what about IHOP Restaurants's ability to quickly and effectively address your problem?
~0305: For that I would say five out of five.
GetHuman: And finally- any advice for other IHOP Restaurants customers?
~0305: Call them early in the day or late. Don't forget any personal or account information you might need for IHOP Restaurants to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~0305 taken from his IHOP Restaurants customer service problem that occurred on October 30th, 2017.