One contact person and one deadline solves the most common group booking problem
A practical model for group bookings built on fixed routines instead of ongoing messages: how the restaurant appoints one contact person at the time of booking, considers a confirmation deadline suited to the group size, gathers menu choices within one window, and clarifies how changes should be handled before the visit.
Why group bookings often drag on
A group booking rarely involves just one guest. Several people submit requests about numbers, allergies and menu choices at different times, often through different channels. Without a clear structure, the restaurant ends up answering the same questions multiple times, while information gets spread across phone calls, emails and notes that don't always reach the kitchen.
The result is that staff must chase answers right up until the day of the visit. Guest numbers change without the kitchen knowing, menu choices come in piecemeal, and no one is certain who actually has the final say for the group. What should have been a simple confirmation turns into an ongoing thread of questions that takes time away from other guests.
One contact person who owns the entire dialogue
When a group booking comes in, the restaurant should ask for the name and phone number of one contact person in the notes field right away. In TableBooking, the restaurant creates a booking link that guests use without setting up an account, and the contact person remains the fixed point of contact for the whole group, no matter how many others later reach out separately.
The advantage is that all information is gathered with one person instead of being spread across several members of the group. This way, the restaurant always knows who to contact with questions about numbers, allergies or table placement, and the contact person can relay messages internally within the group without the restaurant having to deal with multiple senders at once.
A confirmation deadline that follows the group size
A single fixed deadline for all group bookings rarely fits reality, since a group of eight requires less preparation than a group of twenty-five. The restaurant should therefore consider how many days before the visit it needs a final guest count, and whether the deadline should vary with group size or be set the same for everyone.
The deadline should be stated in the first confirmation sent to the contact person, so it doesn't come as a surprise later on. A specific date is easier to work with than a phrase like "a few days before," and makes it easier for the contact person to plan internally within their own group and respond within the deadline the restaurant has set.
Menu choices and changes gathered in fixed windows
Menu choices should be gathered in one round instead of coming in person by person over several weeks. The restaurant can ask the contact person to send a combined overview of preferences and any allergies for the entire group at once, and enter this directly into the notes field on the booking so the kitchen sees everything in one place.
After the deadline, the restaurant should clarify internally how changes are to be handled: whether numbers and menu choices are considered locked for the kitchen's planning, or whether minor adjustments can still be noted and passed on to the kitchen. Whatever practice the restaurant chooses, it should be made clear to the contact person so that expectations match on both sides before the day of the visit.
Want to see how it works in practice?
Start with a free restaurant account and build your tables, opening hours and booking link at your own pace.
Start free