A cancellation feels like a lost cover, but it only is one if you have no way to fill it. With a sensible waitlist, a cancellation or even a no-show becomes a table you quietly hand to someone who wanted it, turning a gap back into revenue. The difference between a venue that loses cancelled covers and one that recovers them is not luck, it is having a waitlist that works, run in a way that fills tables without annoying the guests it touches.
This is how to do it well. For the wider booking picture, start with the booking systems guide.
Why cancellations do not have to cost you
On a fully booked night, a cancellation is, on the face of it, a hole in your covers and your takings. But on that same fully booked night, there are usually people who wanted a table and could not get one. The waitlist is simply the bridge between those two facts: the guest who cancelled and the guest who wanted in. Connect them quickly and cleanly and the cancellation costs you nothing, because the table is filled by someone glad to have it.
The whole value of a waitlist is in that recovery. A venue without one eats every cancellation as a lost cover. A venue with a good one recovers a meaningful share of them, which over a busy season is real money that would otherwise have sat as empty chairs on nights you were turning people away. The covers were there. The waitlist is what lets you capture them.
The mistake: blasting everyone at once
Here is where waitlists go wrong, and it is a common and avoidable error. A table frees up, and the system, or the host, alerts everyone on the list at once: a table's available, first come first served. It feels efficient and it creates a small disaster. Several guests are told the table is free, they get excited, maybe they reply or set off, and then all but one are disappointed, because there was only ever one table. You have turned a nice gesture into a letdown for most of the people you contacted, and you have taught them that your messages lead to disappointment.
Worse, it is chaotic to manage. Multiple people responding to one table is a mess for your host, who now has to sort out who got there first and let the others down. The blast approach trades a clean process for a scramble and a string of small bad experiences.
The right way: one at a time, in turn
A waitlist done right offers the freed table to one guest at a time, in order, with a short window to accept. The next suitable guest on the list is offered the table and given a little time to say yes. If they take it, done, the table is filled and nobody else was bothered. If they decline or do not respond in the window, the offer moves to the next guest, automatically. The process is orderly, fair, and it only ever contacts the people it needs to, in turn.
This is better on every count. The guest who gets the table has a clean, pleasant experience: they wanted a table, one came free, they were offered it, they took it. The guests further down the list are not disappointed, because they were never told about a table they could not have. Your host is not refereeing a scramble. And you still fill the table fast, because the offer moves down the line quickly if someone passes. You get the recovery without the chaos or the bruised goodwill.
Match the table to the guest
A small but important refinement: the offer should go to a guest the table actually suits. A freed table for two is no use to a party of six, and offering it to them just wastes a step and a little goodwill. A good waitlist matches the freed table to the next guest whose party and timing fit, so the offer is relevant when it lands. This makes the whole process faster too, because you are not working through people the table cannot serve to reach the one it can.
Keep it gentle
The guiding principle through all of this is that a waitlist should feel like a kindness, not a pestering. The guest joined because they wanted a table, so an offer is welcome, as long as it is for a table that suits them, comes cleanly, and does not arrive alongside the news that several other people got the same message. Run gently and in turn, a waitlist is a service your guests appreciate. Run as a free-for-all blast, it becomes another reason people mute your messages. The mechanics decide which it is.
Where Grace fits
In Grace, the waitlist offers a freed table to the next suitable guest in turn, with a window to accept, rather than blasting everyone at once. The offer is matched to a guest whose party and timing fit, it moves down the line automatically if someone passes, and because it runs on the same platform as your bookings and guest record, it is part of one orderly flow rather than a separate scramble at the host stand. You recover the cancellation without disappointing the people who miss out. You can see how it works on the Reservations module.
It is built this way because a cancellation should not be a lost cover, and filling it should not come at the cost of annoying the very guests who wanted to come.
FAQ
How does a restaurant waitlist work?
Guests who want a table that is fully booked join a list. When a cancellation or no-show frees a table, it is offered to the next suitable guest on the list. Done well, it offers the table to one guest at a time with a short window to accept, rather than alerting everyone at once. - q: "How do I fill last-minute cancellations?" a: >- A waitlist is the cleanest way. When a table frees up, the system offers it to the next matching guest in line, turning a gap that would have sat empty back into a booked, paying cover. The faster and more orderly the offer, the more cancellations you recover. - q: "Why is offering a freed table to everyone at once a problem?" a: >- Because it creates a scramble and a bad experience: several guests are told a table is free, only one can take it, and the rest are disappointed by a venue that just messaged them. Offering to one guest at a time, in turn, fills the table without annoying the people who miss out.