SiteMinder Is Betting Your Next Guest Will Never See Your Website. They Might Be Right.

So here's what actually happened. SiteMinder... the platform that connects something like 53,000 hotels across 150 countries to distribution channels... just announced two products that wire their entire inventory into AI booking environments. Demand Plus now lets a traveler ask ChatGPT for a hotel in, say, Savannah, see live rates from SiteMinder-connected properties, and complete a reservation on the hotel's own booking page. Channels Plus does something different and arguably more consequential: it gives AI-enabled OTAs and intermediaries direct access to SiteMinder's hotel inventory, meaning the search, comparison, and booking all happen inside the partner's platform. The traveler never leaves the AI interface. They never see your homepage. They never see your brand story or your pool photos or that carefully written "Our Story" page you paid a copywriter $2,000 for.

The underlying tech here is something called the Model Context Protocol (MCP), and I want to be precise about this because it matters. MCP is an open standard that lets AI platforms pull live, structured data from external sources in real time. It's not a proprietary SiteMinder invention... it's an emerging protocol that multiple companies are adopting. What SiteMinder did is build the connective layer between MCP-compatible AI tools and their existing hotel inventory. That's a real technical achievement, but let's be clear about what it is: plumbing. Very good plumbing. The kind that could become essential infrastructure if AI-driven booking actually scales. But plumbing nonetheless. The question isn't whether the pipes work. It's whether the water flows.

And that's where I start squinting. SiteMinder's own research says eight out of ten travelers want AI assistance during booking. Fine. But an Expedia study found that only 8% of travelers are comfortable actually completing a booking through an AI platform. Eight percent. That's a canyon between "help me plan" and "here's my credit card." Demand Plus is smart about this... it routes the traveler back to the hotel's own booking page for the transaction, which sidesteps the trust problem. But Channels Plus, where everything happens inside the partner platform? That's betting the 8% number is going to move fast. Maybe it will. Maybe SiteMinder's $280M in annual recurring revenue and 39% growth in transaction revenue gives them the runway to wait for that shift. But if you're a hotel operator evaluating this today, you need to understand you're being asked to optimize for a booking channel that 92% of travelers don't trust yet.

Look, I've consulted with hotel groups that spent two or three years and real money building direct booking funnels... SEO, metasearch, retargeting, the whole stack. Everything about that strategy assumed the traveler would land on your website at some point. That assumption is what's under threat here. Not today, maybe not this year, but the direction is obvious. AI tools are going to become a discovery and booking layer, and if your property isn't surfaced in that layer, you functionally don't exist for a growing segment of travelers. SiteMinder is positioning itself as the toll bridge between your inventory and that new layer. The question every operator needs to ask is: what does that toll bridge cost me, what do I get back, and who owns my guest relationship on the other side?

Here's what I'd actually want to know before signing up. When a booking comes through Channels Plus and the entire transaction happens inside an AI partner's platform... who owns the guest data? Does the hotel get a name and email, or does it get a reservation number and a payment? Because if it's the latter, you just traded your direct relationship for occupancy, which is exactly the deal OTAs offered 20 years ago, and we all know how that story ended. SiteMinder's CEO talks about ensuring hotels are "present and bookable at every new point of discovery." That sounds great. But present and bookable isn't the same as present and in control. The difference between those two things is the difference between distribution strategy and distribution dependency. And my family's hotel learned that lesson the hard way with the OTAs a long time ago... I don't want to learn it again with AI.