When should a restaurant actually use a waitlist?
A look at which concrete signals should determine whether the waitlist is opened, how the restaurant keeps expectations realistic both internally and externally, which contact order is easiest to defend, and why a fixed expiry time makes the decision predictable from the very first phone call.
The signals that should trigger a waitlist
A waitlist shouldn't be opened just because the calendar looks full on screen. It becomes more accurate when the restaurant can point to concrete signals: several inquiries about the same evening, a cancellation that leaves a table no one else fits exactly, or a date the restaurant already knows draws unusually many guests. That last point should be assessed season by season, not taken for granted.
It's useful to distinguish between general interest and an actual capacity shortage. A handful of inquiries about a Friday evening isn't automatically a reason for a waitlist. When several guests ask for the same table type and the same party size at the same time, the restaurant has a real capacity problem, which is exactly what the waitlist is designed to solve, and opening it should be considered.
Managing expectations before a name goes on the list
Before a guest is placed on the waitlist, staff should know what the restaurant can realistically promise. This requires an honest assessment of the likelihood that a table will free up that evening, not a general feeling that “it usually works out.” Where this assessment is made, and how often it's updated through the evening, is something the restaurant should decide for itself.
Externally, the language should reflect this uncertainty. A phrasing like “we'll put you on the waitlist, but we can't guarantee a table” is more honest than promising someone will call the moment something opens up. Internally, everyone who answers the phone should use the same wording, so the guest isn't given different promises depending on who takes the call.
A contact order that's easy to defend afterwards
When a table actually frees up, the order should be predictable, not based on judgment calls. The simplest and most defensible model is first-in, first-contacted, where the time of the inquiry determines the order, adjusted for whether the party size actually fits the table that's available. Judgment should only come into play when two inquiries are practically identical.
This order should also be visible somewhere all staff can see, not just in the memory of whoever took the call. In TableBooking, the dashboard shows bookings, guests and the floor plan together, so whoever is calling out can see who's first in line without digging through notepads or messages across shifts.
An expiry time makes the waitlist predictable for everyone
Without a fixed expiry time, the waitlist becomes an open-ended obligation that follows the restaurant for the rest of the evening. How long a reasonable deadline should be is up to the restaurant to decide, ideally based on how quickly tables actually turn over again. The point is that the deadline is set before the phone rings, so staff can move on to the next name without waiting for a reply that never comes.
The deadline should be the same for everyone, regardless of party size or how long they've been on the list. Whether it should be short or somewhat longer is a decision the restaurant should base on its own experience, not an industry standard. What matters is that the guest knows exactly how much time they have to respond, and that staff don't have to improvise a new deadline every evening.
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