A waitlist should be routine, not a last resort
A look at which capacity signals make a waitlist the right tool, how the restaurant sets clear expectations from the first contact, which contact order is easiest to defend, and why an agreed expiry time protects both guest and staff.
Capacity signals that trigger a waitlist
A waitlist works best when the restaurant is fully booked, but experience shows that some bookings still fall away before service - cancellations or no-shows that free up tables. How large this share is varies from night to night and from restaurant to restaurant, and should be assessed from the venue's own experience rather than a fixed rule of thumb.
The waitlist, on the other hand, is the wrong tool when the capacity constraint isn't about tables but about staffing. If the restaurant has enough tables but too few hands in service or the kitchen, a waitlist won't relieve the pressure - it just creates more guests waiting for something that isn't coming. In that case, the restaurant should reduce the number of seatings rather than promise space later.
Setting clear expectations from the first contact
A guest placed on the waitlist should be given a concrete time window, not a vague "we'll call you." Say instead: "We'll get in touch before 8:30pm if a table opens up, but we can't guarantee it tonight." This phrasing is honest about the uncertainty while still giving the guest something to plan around.
It's also useful to ask about party size and any special needs right away, so staff don't have to call back later to clarify details. A guest who says they're a party of four but actually arrives with two highchairs changes which table actually fits - this information should be on hand before anyone calls to offer a spot.
A contact order that causes the least confusion
The simplest and most predictable order is first-come, first-served, adjusted for table size. If a table for two becomes available, the first party of two on the list is called - not whoever has waited longest regardless of size. Mixing in criteria like drinking habits, familiarity with the guest, or other informal judgments makes the order hard to defend if a guest asks why they were passed over.
In practice, one person should be responsible for calling down the list, and each entry should be marked with a status immediately - calling, answered, declined, or no answer. Without this marking, several staff members end up calling the same guest, or no one calls because everyone assumes someone else already has.
An expiry time that protects guest and staff alike
Set a fixed expiry time per entry, and agree internally on how long it should be - a few minutes after the guest is called, or longer if contact is hard to establish. If the guest doesn't answer or confirm within the deadline, the table moves on to the next person on the list. This prevents a table from sitting empty while staff wait for an answer from a guest who may have already booked elsewhere.
Without a clear expiry time, both guest and staff experience unnecessary uncertainty: the guest doesn't know if they're still in the running, and staff don't know when they can move on. In TableBooking's dashboard, bookings, guests and the table map are all displayed together, giving staff a unified overview to rely on throughout this process.
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