A couple arrived at their hotel after 10 hours of travel to find their Booking.com reservation didn't exist—despite holding a confirmation email with booking ID and dates. When they called support for help at 3 a.m., the customer service representative disconnected the call and left them stranded.
The incident, detailed on r/travel, highlights serious reliability issues with online booking platforms that millions of travelers depend on. When confirmations can't be trusted and support abandons customers in crisis, it raises fundamental questions about these services.
What Happened
The travelers reached their hotel around 3 a.m. after nearly 10 hours of travel. The front desk had no record of their reservation in the hotel's system. The couple showed their Booking.com confirmation email containing all relevant details—booking ID, dates, hotel name, confirmation number.
Still no reservation in the system.
They called Booking.com customer service from the hotel lobby, exhausted and with luggage in tow. The representative "kept giving the same scripted 'sorry for the inconvenience' lines over and over but wasn't actually helping," according to the travelers.
Their request was straightforward: help find alternative accommodation nearby since it was past midnight and searching online themselves was becoming difficult. The response: the representative disconnected the call.
"That part honestly blew my mind more than the booking issue itself," the traveler wrote. "Mistakes happen, sure. But abandoning customers stranded at 3 a.m. in a different city after THEY confirmed a reservation that apparently never properly existed? Crazy."
The Confirmation Problem
This isn't about user error—these travelers had proper confirmation. The failure occurred somewhere in the chain between 's system, the hotel's property management system, and the actual reservation record.
