Google AI Bookings: What Restaurants Must Know

Google just made a move that every restaurant owner with a dining room needs to pay attention to. The company announced it's rolling out what it calls 'agentic capabilities' inside its AI Mode, starting with restaurant reservations in the UK. The short version: a customer asks Google's AI to find them a table, and Google handles the whole thing. It searches, checks availability, and confirms the booking without the customer ever clicking over to your website, your reservation platform, or anything else you control.

What Google Actually Did Here

This isn't a tweak to how Google surfaces restaurant results. It's a fundamental shift in what Google is trying to be. Search used to send people somewhere. Now Google wants to complete the task itself and keep the user inside its own environment the entire time.

The new feature lets someone type or spea

k a request like 'book me a table for four at a good Italian restaurant on Saturday night' and Google's AI takes it from there. It identifies options, pulls availability, and confirms the reservation. No browsing. No visiting your site. No direct interaction with your brand at all before that guest shows up at your door.

It launched in the UK first, which means US operators have a window to watch how this plays out before it lands here. But if you think it isn't coming stateside, you haven't been watching how quickly these things move.

Why This Should Make You Think Twice About Who Owns Your Guest Relationship

The reservation itself might show up on your books. But the guest's entire experience leading up to that moment happened inside Google. They didn't read your menu. They didn't see your story. They didn't interact with your brand in any way you designed or controlled. Google made the match, Google confirmed the seat, and you got a name on a list.

That guest relationship belongs to Google now, at least in the pre-visit window. And you can bet Google will figure out how to monetize that position over time, whether that means promoted placements, preferred partners, or fees for bookings made through the AI. It's the same playbook that's already happened in delivery.

Speaking of delivery: restaurants already know what happens when a platform inserts itself between you and your customer. You lose pricing control, you lose data, and you lose margin. Every third-party tool that sits between you and a guest is a relationship you don't fully own. That applies to reservations now just as much as it applies to delivery orders. If you've ever had to fight for your own revenue on a delivery platform, services like Jelly exist precisely because platforms don't have your interests in mind. The same instinct applies here.

What You Can Do Right Now

You can't stop Google from building this. But you can make sure your restaurant is positioned correctly and that you're not caught flat-footed when it fully arrives.

• Lock down your Google Business Profile. If Google's AI is pulling reservation availability and matching guests to restaurants, your profile is the foundation it's working from. Your hours, your category tags, your photos, your reviews, and your booking integration all need to be accurate and current. Outdated or thin profiles will get passed over.

• Know how your reservation system connects to Google. If you use OpenTable, Resy, SevenRooms, or any other platform, find out now whether that system feeds availability into Google's booking layer. Understand what data you're sharing, whether there are fees attached to AI-sourced bookings, and what the terms actually say. Don't wait until you see a charge on a statement.

• Build direct booking habits with your regulars now. Email lists, loyalty programs, direct reservation links in your own marketing, anything that creates a path to book with you that doesn't run through a middleman. The guests who know your brand and seek you out directly are the ones you'll actually have a relationship with long-term.

Google's move into agentic bookings isn't necessarily bad for restaurants in the short term. More reservations is more reservations. But the pattern here is familiar. A platform inserts itself into a transaction, provides convenience, builds dependency, and eventually charges for access. The time to think about this clearly is before that last step happens, not after.