Hotels.com: the person I was talking to was no help at all...
A Hotels.com customer review by GetHuman user GetHuman-428739 from November 22nd, 2017
Background on GetHuman-428739's case
GetHuman: GetHuman-428739 - can you tell our other Hotels.com customers when your case took place?
GetHuman-428739: Yes. It was middle of the night, on November 20th.
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-428739 a list of common Hotels.com problems)
GetHuman-428739: "Make a booking" was why I was trying to call.
GetHuman-428739'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-428739: the person I was talking to was no help at all I am telling about the chagers on my credit card that someone made on my card he wants a ** dig number that I don't have I tell him I didn.t make the resv
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-428739: 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-428739: 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-428739: For that I would say one out of five.
GetHuman: And finally- any advice for other Hotels.com customers?
GetHuman-428739: 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-428739 taken from his Hotels.com customer service problem that occurred on November 20th, 2017.