Restaurant Waiting Lists: Four Decision Rules for Capacity and Contact
A look at when a waiting list should be used: which capacity signals should actually trigger it, how language keeps expectations realistic, why the timing of the inquiry should govern contact order, and why the restaurant itself should set a short response deadline.
When Capacity Is the Actual Signal
A waiting list shouldn't be a default setting the restaurant switches on every evening. It makes most sense when a specific time slot is full while demand clearly continues - for example, when several guests in a row ask for the same time on a Friday evening. In that case the signal is capacity, not atmosphere, and the decision can be made without guessing.
A useful checkpoint is to look at how many tables are actually free in the relevant time window, not just whether the restaurant "feels" full. If two four-seat tables are still open, a waiting list is premature - the guest should instead be given a concrete suggestion. A waiting list works best when the real room to manoeuvre is gone, not simply when the front desk is busy.
Managing Expectations: What a Waiting List Actually Promises
The language used when a guest is placed on the waiting list should never suggest that a table is guaranteed. Phrases like "we'll note you down" or "we'll get in touch if something opens up" are more precise than "we'll try to sort something out," because the latter creates an expectation the restaurant can't necessarily meet. A precise standard response makes it easier for the guest to know exactly what being on the waiting list involves.
Internally, the team should share the same understanding of what the waiting list actually means: a possibility, not a commitment. If a server verbally promises a table while the guest waits at the bar, a gap opens up between what was said and what is actually booked. A shared, written-down response - ideally a single standard phrase - ensures everyone at the front says the same thing.
A Contact Order That's Easy to Defend
The simplest order to explain, both internally and to guests, is the time of the inquiry. Whoever asked for a table at 5:02 pm is contacted before whoever asked at 5:15 pm, regardless of party size or who the guest knows on staff. This rule is easy to enforce because it rests on a timestamp, not a judgment call that can be disputed afterward.
The exception worth accepting is when a table actually suits one group better than another - for instance, when a table for six becomes available and the first person on the list wants seats for two. In that case it's fine to skip ahead to the next guest who matches the table type, as long as the person who was passed over is told why.
Expiry Time: Why the Response Needs to Come Quickly
An inquiry without an expiry time is hard to manage, because the restaurant doesn't know whether the guest is still waiting or has found somewhere else to eat. How long a reasonable deadline should be - a few minutes or somewhat longer - should be judged by the restaurant based on how quickly staff can follow up and how fast the table could otherwise be filled.
When the deadline passes without a response, the table should be offered onward without exception - even if the guest gets in touch right afterward. The dashboard in TableBooking shows bookings, guests and the table map, making it easier to keep track of who is waiting and which tables are in play before the next guest is contacted.
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