Gemini's OpenTable Link Moves the Assistant From Recommending to Booking

Google has published documentation for an OpenTable integration in Gemini Apps that lets eligible users check restaurant availability and complete reservations through natural-language requests ^[1]. The change matters because it moves the assistant from answering a recommendation query to carrying out an action with a real-world outcome, and it is a shipped capability rather than a roadmap item ^[2].

The scope is specific and worth reading closely before you build against it. Gemini can check availability, make new bookings, look up existing bookings and cancel reservations ^[3]. It cannot directly modify an existing reservation inside its own interface; Google says it can instead offer a link that sends the user to the OpenTable app to make the change ^[4]. Within this flow it also cannot process payments, show menus or display reviews ^[5]. The documented pattern is intent to booking, not a replacement for OpenTable's browsing and management surfaces ^[6].

The mechanics are a handoff. A user connects OpenTable to Gemini Apps, states the constraints in ordinary language, and allows Gemini to use Reserve with Google to check availability and book the table with OpenTable ^[7]. Restaurant, party size, date, time and seating preference can all sit in one request ^[8]. The stated aim is to cut the number of steps between intent and a confirmed reservation ^[9]. It runs on both the Gemini mobile app and the web app at gemini.google.com ^[10].

The eligibility fences are equally documented. Google restricts the integration to US residents aged 18 or older, requires a signed-in personal Google account, requires the Activity setting to stay on, and supports English ^[11]. A work-managed Google account is not the documented account type for this flow ^[12]. Google's documentation sets out the supported flow, and OpenTable has separately described its work to surface bookings through AI-driven conversational and voice experiences ^[13].

For builders, the useful lesson is the design shape rather than the restaurant angle. The integration works by defining clear, task-specific handoffs between the assistant and the service that owns the transaction, instead of pulling every capability into the assistant itself ^[14]. The requirement that Activity stay on also puts account settings and data handling inside the user experience, which matters when prompts carry personal preferences and future plans ^[15].

Two cautions. This is a consumer-facing integration with defined eligibility and product limits, not a newly announced enterprise booking API or a change to Gemini pricing ^[16]. And the shorter path from request to reservation only holds if the availability data flowing through OpenTable and Reserve with Google is accurate enough to support it ^[17].

Watch whether Google widens eligibility beyond US personal accounts and English, and whether the payments and modification gaps close inside Gemini or stay as handoffs to OpenTable ^[4][16].