Hotels.com: ** yr old son booked hotel that required ** yr...
A Hotels.com customer review by GetHuman user ~trixierogers from November 3rd, 2017
Background on ~trixierogers's case
GetHuman: ~trixierogers - can you tell our other Hotels.com customers when your case took place?
~trixierogers: Yup. It was afternoon, on November 2nd.
GetHuman: Did you reach out to Hotels.com, and if so, how?
GetHuman: And which of these common Hotels.com customer issues best describes the reason you wanted to talk to them?
(Shows ~trixierogers a list of common Hotels.com problems)
~trixierogers: "Change a Reservation" was why I was trying to call.
~trixierogers's review of Hotels.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Hotels.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.
~trixierogers: ** yr old son booked hotel that required ** yr old age limit - was charged one full day for cancellation even though I have in writing they do not charge for changes or cancellations. I WILL NEVER USE HOTELS.COM EVER AGAIN!!!
GetHuman: Let's quantify your experience contacting Hotels.com. On a scale of 1 to 5, how easy is it go get help on a Hotels.com problem?
~trixierogers: I'd give them a four 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?
~trixierogers: I'd give them a three out of five on communication.
GetHuman: And what about Hotels.com's ability to quickly and effectively address your problem?
~trixierogers: For that I would say two out of five.
GetHuman: And finally- any advice for other Hotels.com customers?
~trixierogers: Call them early in the day or late. Don't forget any personal or account information you might need for Hotels.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~trixierogers taken from his Hotels.com customer service problem that occurred on November 2nd, 2017.