Group bookings without unnecessary back-and-forth: four fixed steps in the process
A practical process for group bookings: how the restaurant designates one point of contact, sets a confirmation deadline suited to the group size, clarifies guest numbers and menu choices in the same step, and defines exactly what can still be changed before the visit.
One point of contact from the first message
Group bookings become unmanageable when several people in the party send messages independently of one another. The solution is simple: ask for the name and phone number of one point of contact right from the first message, and state clearly that all further communication will go through that person. This way staff know exactly who to deal with, and the group knows who holds responsibility internally.
This point should be written down, not just mentioned verbally in a phone call. If the restaurant uses a booking link where guests fill in the details themselves without creating an account, the contact-person field can be made mandatory. That way the information stays attached to the booking, visible to everyone working on the upcoming evening, without anyone having to dig through a thread of messages.
A confirmation deadline suited to the group
What counts as a reasonable deadline for confirmation depends on the size of the group and how complex the menu selection is. The restaurant should judge for itself whether a party of eight needs a shorter deadline than a group of forty ordering a pre-selected menu, and set the deadline accordingly rather than applying one fixed rule to every group alike.
The deadline should be communicated as a specific date, not as 'a few days before'. Write, for example, 'confirm numbers and menu choices by Tuesday 14 May' rather than 'let us know well in advance'. The restaurant should also decide on a fixed rule for what happens if the deadline passes without a response - either a reminder or a reduction to the last confirmed number.
Guest numbers and menu choices in the same step
Guest numbers and menu choices should be settled at the same time, not in two separate rounds. When the contact person confirms the number of guests, the menu options to choose from should be sent along at the same time, to be decided before the deadline. This prevents the kitchen from receiving a final headcount without knowing which dishes to prepare, and stops menu choices from arriving after the table plan has already been set.
For groups with a pre-selected menu, it is useful to ask for choices per person, compiled into one list by the contact person, rather than having each guest submit separately. A simple table with initials and dish choices is enough. In TableBooking, the restaurant can create a booking link that guests use without setting up an account, and the dashboard shows bookings, guests and the table map together, so numbers can be checked against available capacity before the menu is confirmed.
What can be changed - and what cannot
The most common source of back-and-forth after confirmation is uncertainty about how much can still be adjusted. The restaurant should set a concrete limit, for example how many guests the number can be reduced by without requiring a new discussion, and decide that any increases or menu changes after the deadline are treated as a new request, subject to a fresh assessment of capacity and kitchen workload.
This limit should appear in the confirmation sent to the contact person, not only in the restaurant's internal routines. A short line such as 'changes to numbers or menu after 14 May cannot be guaranteed' makes expectations clear from the outset. That way, both the contact person and staff avoid having to clarify details again in the days before the visit, and any deviations become the exception rather than the rule.
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