Explainer2026-09-15T07:26:20.857Z

Restaurants, pubs and the booking that isn't just a table.

A table booking for twelve people celebrating a 40th birthday is not the same transaction as a table for two, and treating it that way is where the booking usually goes wrong.

4 min read

The Selfe team
Agentic commerce infrastructure
A table for twelve isn't a bigger table for two. Past a certain size the booking itself changes shape: a private area, a set menu, dietary needs collected once instead of discovered guest by guest.

Group size changes what's being booked

Twelve people and a birthday cake change what needs confirming: a private or semi-private area, a set menu the kitchen can run for that many covers, and dietary requirements collected once across the whole group rather than discovered one guest at a time on the night.

A pub takes a booking for twelve people celebrating a 40th birthday. This site's own piece on what a booking request needs, the date, the party size, a dietary need, the occasion, still applies here. What changes for a group is where the threshold sits: past a certain size, a table booking becomes a different kind of transaction, with its own extra conditions layered on top.

Below a certain number, usually six to eight depending on the venue, a booking is genuinely just a table. Above it, most venues switch to a private or semi-private area, a set or limited menu the kitchen can run at volume, and sometimes a deposit or minimum spend. An agent that treats twelve the same as two, checking only whether a table for twelve exists, misses every one of these conditions that decide whether the booking works.

A deposit or minimum spend, when it applies, changes what the host is agreeing to at the point of booking, separate from how the bill gets settled at the end of the night. An agent that confirms a group booking without surfacing a £200 minimum spend has confirmed something the host hasn't agreed to yet, and the venue is the one left explaining it on the night, at exactly the moment nobody wants an awkward conversation about money.

Dietary requirements need collecting once, for everyone

A table for two can handle a dietary question at the table. A party of twelve with three different dietary requirements needs those collected before the day, so the kitchen can plan a set menu that works for everyone, rather than the group discovering on the night that half the set menu is off-limits to a third of the table. An agent handling this well asks for dietary needs across the whole group up front, not just from whoever's making the booking.

The occasion itself is a fact worth capturing

A birthday means a cake might be brought in, or the venue might offer to provide one, and either way it's a detail that changes the booking rather than sitting alongside it as decoration. An agent that captures "fortieth birthday" as context, not just as a nice-to-know, lets the venue plan for it, a reserved spot for the cake, a card on the table, rather than finding out when a guest walks in carrying one.

A full booking lets the pub's team prepare in advance.

Selfe connects an AI agent to a pub's real private-area availability, set menus and deposit terms directly, rather than a booking form built only for a table for two.

A booking that arrives as "table for twelve, 8pm" forces the venue to have the entire group-booking conversation, area, menu, dietary needs, the occasion, from scratch when the host arrives or calls to confirm. A booking that arrives with all of that already attached lets the team prepare properly instead of improvising on the night.

At what group size does this start to matter?

It varies by venue, but most switch to a different process somewhere around six to eight guests. Below that, a simple table booking usually still works.

What if the host doesn't know everyone's dietary requirements yet?

A good agent can still flag that the group booking needs this information before the set menu is finalised, rather than skipping the question entirely.