Where each booking channel works — restaurant table

Four routes to a reservation, and the one thing each of them will not do. Hover any row for what it means in practice.

Works today Partial / depends on venue Not supported
Channel Coverage Books table Waitlist Change / cancel
OpenTableGlobal recommendations Worldwide inventory Yes Venue On OpenTable
ResyAmerican Express US restaurants Yes No On Resy
YelpReservations + Waitlist US & Canada Yes Yes On Yelp
MCP serversSelf-hosted Venue-dependent Listed only Rare On the venue's platform

What each channel still hands back to you

Share of the reservation flow the channel completes end-to-end, from request to confirmed table.

Book → confirm
88%
Deposit venues
30%
Hot tables
12%
Phone-only venues
5%
Read it this way: the agent is excellent at the routine booking and still useless at the ones that need a human relationship. Say book, name the party size, keep your details in memory, and always collect the confirmation.

Sources: OpenTable “Filling seats with smarter tech” (first restaurant-tech partner on OpenAI's agent work); Yelp and Resy in-chat reservation launches, 10 August 2026, as analysed by explainx.ai; community MCP servers for OpenTable on GitHub and Apify. Coverage reflects published partner material as of 26 September 2026.