AI agents that plan and book trips have moved from demos to dated rollouts in the last two months, and I think every hotel group and independent should decide, in writing and before the first quarter of 2027, which agents may see its rates, where those bookings land and how it will measure them. Leaving the decision to whichever channel the agent happens to reach first is how hotels ended up paying for metasearch and OTA demand they could have owned.
The agents have dates attached
The evidence is in vendor releases from the last eight weeks. Booking Holdings announced a planned $100 million investment in Vayo, a personal travel agent in private beta that it says works across Booking Holdings brands and beyond, including reservations made directly with hotels. Cloudbeds announced an integration with Meta’s Muse agent that will show participating properties with live rates and availability and complete bookings in the hotel’s own Cloudbeds booking engine, with a US rollout scheduled for the first quarter of 2027. We reported both at the time: the Vayo launch and its planned investment, and the Cloudbeds integration with Muse.
Cloudbeds CEO Adam Harris put the stakes plainly: “When an agent finds a property that runs on Cloudbeds, the booking lands where it belongs: in the hotelier’s own system, as a direct booking, with the guest relationship intact.” That is a vendor describing its own product, and I take it as such. The point that matters for operators is the architecture it describes. An agent can reach a hotel through an intermediary, through the hotel’s own booking engine, or by scraping a public website. Each route sets a different cost per booking and a different owner of the guest.
Advertisement
The strongest case for keeping agents out
The best argument against letting agents book at all is control. An agent can choose the wrong room type, misread a cancellation policy or book a rate the guest did not understand, and the hotel absorbs the dispute at the front desk. A property cannot easily tell a legitimate agent acting for a real guest from a bot scraping rates for a competitor. Blocking automated traffic at the website and waiting for the market to settle looks like the prudent choice.
I disagree, for two reasons. First, blocking only closes the direct route. An intermediary-owned agent such as Vayo still sells the hotel through the intermediary’s existing contracts, so the hotel that blocks agents keeps the demand and pays the commission. Second, the identity problem now has an open standard behind it. On November 10 the Linux Foundation took on Agent Name Service, a specification that uses DNS and existing website certificates to name AI agents and verify their identities, with 11 supporting organizations. Linux Foundation CEO Jim Zemlin said autonomous agents “can’t succeed without verifiable identity.” A hotel’s booking engine vendor can be asked whether and when it will check that identity. With that check in place, a hotel can keep a list of named agents it admits and turn the rest away.
Measure agent bookings like a channel
The second half of the policy is measurement, and here the warning comes from outside travel. Invoca’s survey of 451 US consumer marketing leaders, released November 10, found that 74% of those running AI agents cannot fully track an agent-handled lead from first click to conversion, and only 27% use revenue, bookings or conversion rate as the main measure. Invoca CEO Gregg Johnson said “you ultimately measure sales channels on revenue, not conversations or activity.” Hotels that let agents in without a code on the booking, a rate plan or a source tag will repeat that result and will not know what the channel costs or earns.
What I would put in the policy
Revenue and distribution leaders can write it on one page. Name the agents you will accept bookings from and the route each must use, with your own booking engine first. Ask your booking engine and PMS vendors, in writing, for their agent roadmap: which agents they connect to, when, and whether they will verify agent identity under a standard such as Agent Name Service. Set a booking source code for each agent so revenue, cancellations and cost per booking show up in the same report as your OTA and brand.com numbers. Decide who handles a disputed agent booking at check-in, and train the desk on it. Review the list every quarter, because the agents and their routes are changing that fast.
Hotels that skip this step will still get agent bookings. They will arrive through someone else’s contract, under someone else’s terms, and the hotel will learn the cost from its commission statement.
Source: Cloudbeds
