Booking.com: Booked a hotel in May (* months from now) - I w...
A Booking.com customer review by GetHuman user ~PAOracle from November 26th, 2017
Background on ~PAOracle's case
GetHuman: ~PAOracle - can you tell our other Booking.com customers when your case took place?
~PAOracle: Yes. It was morning, on November 19th.
GetHuman: Did you reach out to Booking.com, and if so, how?
GetHuman: And which of these common Booking.com customer issues best describes the reason you wanted to talk to them?
(Shows ~PAOracle a list of common Booking.com problems)
~PAOracle: "Missing item" was why I was trying to call.
~PAOracle's review of Booking.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Booking.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.
~PAOracle: Booked a hotel in May (* months from now) - I was to pay after arriving. Billed for full amount ($****) but confirmation stills says needs to be paid. French accent heavy for Rep and he seemed unsure how to proceed - "we will get back to you". ** hours later no response!
GetHuman: Let's quantify your experience contacting Booking.com. On a scale of 1 to 5, how easy is it go get help on a Booking.com problem?
~PAOracle: 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?
~PAOracle: I'd give them a five out of five on communication.
GetHuman: And what about Booking.com's ability to quickly and effectively address your problem?
~PAOracle: For that I would say five out of five.
GetHuman: And finally- any advice for other Booking.com customers?
~PAOracle: Call them early in the day or late. Don't forget any personal or account information you might need for Booking.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~PAOracle taken from his Booking.com customer service problem that occurred on November 19th, 2017.