The Reservation Bots Showed Up Before the Rules Did
A host at a thirty-six seat restaurant in Austin told me about a Friday night last month. Three reservation requests landed within the same minute for the 7:30 slot. Three different names. Three different phone numbers. The same note attached to each one, word for word: flexible on time, no allergies, celebrating a birthday. Nobody celebrates a birthday three times in sixty seconds. She canceled two of the three and still isn't sure she picked the right one to keep.
That's not a glitch. That's agentic booking showing up at the host stand before anyone agreed on the rules for it.
The national version of this story has been running for a couple weeks now. CNN reported in September that AI agents are starting to compete for dinner reservations the same way bots once scalped Beyoncé tickets, and NBC followed with diners openly admitting they're using personal assistants to grab tables they couldn't get on their own. Resy's response was blunt: no unapproved third-party bots or agents get to access or interact with its platform. Full stop. That's the sentence worth sitting with, because it's not about whether AI can book a table. It's about who gets to decide which AI is allowed to.
Who's actually booking that table?
Every AI travel agent story this fall has been framed as a fight between giants. Booking Holdings launched Lola at the end of September, a conversational assistant that can search and book across Booking.com, OpenTable, KAYAK, Priceline, Agoda, and FareHarbor, plus partners like GetYourGuide and SeatGeek. Google is testing hotel bookings that complete inside its AI Mode chat, with Amadeus doing the plumbing underneath. Meta's Muse showed up the same week, partnered with Expedia, conspicuously without Booking Holdings in the room. Stock prices moved. Analysts picked sides.
None of that argument touches what happened at that Austin host stand. The restaurant fight isn't about which billion-dollar platform wins distribution. It's about whether the person asking for a table is a person at all, and whether the reservation system can tell the difference fast enough to matter.
Resy drawing a line around unapproved bots is the restaurant industry's version of a bouncer checking IDs. It's not rejecting the idea of an assistant making a booking. OpenTable and Resy both clearly expect that to keep happening, which is exactly why Lola bundles in OpenTable as a booking partner. What they're rejecting is an assistant nobody vetted, acting on rules nobody agreed to, hitting their system at a volume a normal guest never could. A platform that doesn't gatekeep that gets flooded, and a flooded reservation book is just as useless to you as an empty one. Worse, actually, because an empty book at least tells the truth.
The part that actually costs you money
Here's what the bot fight looks like from your side of the host stand, not the platform's.
Say a legitimate, approved assistant books a table for six on your busiest Saturday. Card on file, deposit taken, confirmation sent. Good. Except nobody asked about the shellfish allergy, because the assistant was optimizing for availability and price, not reading your allergy policy buried in a PDF three clicks from the reservation page. Nobody mentioned that two of the six are driving in from out of town and might run twenty minutes late, which used to be the kind of thing a person says when they call and talk to an actual human. The guest shows up, the food's already moving, and now you're improvising a dietary substitution during service because the system that made the booking didn't carry the information that matters.
That's not hypothetical. That's the gap between what a reservation holds and what a kitchen needs to know, and it was already a problem with online booking forms before any assistant got involved. Agentic booking just makes the gap bigger and faster, because the assistant isn't trying to build a relationship with you. It's trying to close a transaction and move on to the next request in its queue.
And then there's the no-show question, which is the one that should actually keep you up at night. Independent hotels already eat an OTA cancellation rate of 21.8 percent, more than double the 10.6 percent rate on direct bookings, according to Cloudbeds' latest State of Independent Hotels report. Nobody has a clean number yet for AI-assisted restaurant no-shows, because the whole thing is maybe six weeks old as a visible phenomenon. But ask yourself what happens to that rate when the party booking the table isn't the party committed to showing up. An assistant exploring three restaurants on behalf of an indecisive guest, holding all three tables until the last possible hour, is a rational thing for the assistant to do and a brutal thing for your Friday night.
This isn't only a restaurant problem
The same gatekeeping question is coming for everyone else in this business, just a few months behind.
Lola's activity partners include GetYourGuide and FareHarbor, which means a guide running half-day kayak trips out of a small coastal town is about to face the identical question Resy just answered: who's allowed to book my calendar automatically, and under what rules. A boutique inn with eleven rooms and a booking widget built by a nephew in 2019 is going to find out the hard way whether its availability calendar is even readable by a system like Google's AI Mode or Lola, let alone trustworthy enough to transact against. The Hotel Blueprint's distribution reporting this fall makes the practical issue plain: assistants need structured, current information to recommend and book with confidence. A big chain has the systems to supply that. A single property usually doesn't, which is exactly why an OTA keeps getting the booking even when the guest never looks at an OTA page.
So the fight over unapproved bots at Resy and the fight over who shows up first in a Google AI Mode recommendation are the same fight, wearing different uniforms. It's a fight over who gets to act on your behalf, who verifies that they're allowed to, and who eats the cost when the verification fails. Right now the platforms are writing those rules one at a time, under deadline pressure, in response to whatever broke that week. You are not in the room when they write them.
What you actually control
You don't get a vote on Resy's bot policy or Google's AI Mode rollout schedule. You do get to control what any legitimate assistant finds when it goes looking for you, and that's not nothing.
Put your actual policies in plain text where a system can read them, not inside a PDF or a photo of a laminated card at the host stand. Deposit amount, cancellation window, allergy protocol, party size limits, the stuff a human used to learn by calling and asking. If that information is structured and current, an approved agent booking through OpenTable, Resy, or your own site gets it right automatically, and you stop relitigating your own policy at the table every time someone's assistant skipped the fine print.
Keep pushing people toward direct bookings, loudly and specifically, the way you always have, just update the pitch. A guest who books through your own site, where your information is exactly as you wrote it, is a guest whose assistant had to read your terms to get the booking right. A guest routed through three layers of platform API has terms translated twice before they reach you. One of those is a relationship. The other is a transaction wearing a relationship's clothes.
And check, plainly, whether an assistant could even find you accurately right now. Not whether you rank on Google. Whether the structured facts about your restaurant, your inn, your boat trip are sitting somewhere an AI assistant bookings system can actually parse without guessing. Bookaible's whole reason for existing is to show you that answer. That's the one plug in this piece, and I'm done after this sentence.
The bot fight at the host stand isn't going away because a platform wrote a rule about it in September. More assistants are coming, approved and not, and the restaurants and inns that survive the next version of this aren't the ones waiting for OpenTable or Resy to sort it out. They're the ones whose information was already clean, already true, and already theirs before anyone asked.