Hotels.com: The company only responds to you while you are...
A Hotels.com customer review by GetHuman user GetHuman-259975 from November 27th, 2017
Background on GetHuman-259975's case
GetHuman: GetHuman-259975 - can you tell our other Hotels.com customers when your case took place?
GetHuman-259975: Yes I can. It was afternoon, on November 24th.
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 GetHuman-259975 a list of common Hotels.com problems)
GetHuman-259975: "Insurance claim" was why I was trying to call.
GetHuman-259975'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.
GetHuman-259975: The company only responds to you while you are still making a booking and paying. When you get challenges and you want to change they stop communicating. Still waiting after three days. Hoping to get help!
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?
GetHuman-259975: 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-259975: I'd give them a one out of five on communication.
GetHuman: And what about Hotels.com's ability to quickly and effectively address your problem?
GetHuman-259975: For that I would say two out of five.
GetHuman: And finally- any advice for other Hotels.com customers?
GetHuman-259975: 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 GetHuman-259975 taken from his Hotels.com customer service problem that occurred on November 24th, 2017.