SiteMinder Wants to Be Your Hotel's Front Door to AI Search. The Plumbing Isn't Ready.

So SiteMinder announced it's extending its Demand Plus and Channels Plus products into AI-driven booking environments... ChatGPT, Claude, and whatever comes next. The pitch is straightforward: travelers are increasingly using AI tools to plan trips, so hotels need to be discoverable inside those conversations. Their inaugural partner is an outfit called DirectBooker, which positions itself as an aggregator connecting live hotel rates to AI platforms. The underlying tech uses something called Model Context Protocol (MCP), which is essentially a standardized way for AI systems to pull real-time data from hotel inventory. On paper, this is the logical next step in distribution. In practice, I have questions.

Let's start with what actually matters. SiteMinder manages over 2.5 million rooms, processes 300 million room nights annually, and generates north of A$85 billion in booking revenue for its customers. Those aren't startup numbers. This is a company with real distribution infrastructure. And their own research says 80% of travelers now want AI-powered capabilities during the booking journey... a four-fold increase from last year. Forty percent of travelers under 35 have already experimented with AI for trip planning. The demand signal is real. I'm not disputing that. What I'm disputing is the readiness of the receiving end.

Here's where my engineering brain starts twitching. MCP is a protocol for giving AI platforms access to live hotel data. Live rates. Live availability. In real time. That means your inventory is now exposed to a new class of automated queries from platforms whose behavior you don't control, whose error-handling you haven't tested, and whose booking flow doesn't look like anything your front desk team has ever seen. I consulted with a hotel group last year that integrated a new channel manager endpoint and spent three months debugging phantom reservations that showed up in the PMS with no source attribution. Three months. And that was a conventional OTA connection, not an AI agent making decisions on behalf of a traveler who may or may not understand what they just booked. The question I keep coming back to is the one I ask about every new distribution pathway: what does the night auditor see? When a reservation comes through from an AI conversation on Claude, what does that look like in your PMS? Is it attributed correctly? Does it carry rate parity? Does the cancellation policy match what the AI told the guest? Because if there's a gap between what the AI promised and what your system recorded, the guest is going to be standing at your front desk at 11 PM with a screenshot of a conversation you've never seen, and your front desk agent is going to have zero tools to resolve it.

Look, I get the strategic logic. OTA commissions are brutal, and if AI becomes a significant discovery channel, hotels need to be present there. SiteMinder's stat that direct bookings generate 65% more revenue than OTA bookings (excluding commission) is the right argument for why this matters. But here's the part that got buried: only 8% of travelers currently feel comfortable actually booking through an AI platform. Eight percent. Sixty-eight percent prefer a trusted brand for the transaction itself. So we're building infrastructure for a behavior that barely exists yet, and the infrastructure itself introduces new failure modes at property level. That's not a reason to ignore it... it's a reason to test it carefully instead of rushing to flip the switch because the press release sounds exciting.

The real concern for independents (and SiteMinder's sweet spot is independents) is control. Every new distribution channel is a new surface area for rate leakage, attribution confusion, and guest expectation mismatches. SiteMinder says this is about giving hotels "new ways to be found." Fine. But being found is the easy part. Delivering on whatever the AI told the guest... that's the hard part. And that happens at your property, with your staff, at 2 AM. Not in Sydney. Not in a demo. At your front desk.