Rodeway Inn: I was robbed by one of the housekeepers at one...
A Rodeway Inn customer review by GetHuman user ~disappointed from November 24th, 2017
Background on ~disappointed's case
GetHuman: ~disappointed - can you tell our other Rodeway Inn customers when your case took place?
~disappointed: Sure. It was afternoon, on November 19th.
GetHuman: Did you reach out to Rodeway Inn, and if so, how?
GetHuman: And which of these common Rodeway Inn customer issues best describes the reason you wanted to talk to them?
(Shows ~disappointed a list of common Rodeway Inn problems)
~disappointed: "Change booking" was why I was trying to call.
~disappointed's review of Rodeway Inn customer service
GetHuman: So how would you sum up your experience for GetHuman's Rodeway Inn 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.
~disappointed: I was robbed by one of the housekeepers at one of your hotels with a DO Not Disturb sign on the door and Im being told by the owner of that establishment and the customer service that theres nothing I can do....Bad Business
GetHuman: Let's quantify your experience contacting Rodeway Inn. On a scale of 1 to 5, how easy is it go get help on a Rodeway Inn problem?
~disappointed: 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?
~disappointed: I'd give them a one out of five on communication.
GetHuman: And what about Rodeway Inn's ability to quickly and effectively address your problem?
~disappointed: For that I would say two out of five.
GetHuman: And finally- any advice for other Rodeway Inn customers?
~disappointed: Call them early in the day or late. Don't forget any personal or account information you might need for Rodeway Inn to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~disappointed taken from his Rodeway Inn customer service problem that occurred on November 19th, 2017.