Restaurant no-shows: what to do

A guest didn't turn up for their booking, and the table stood empty all evening. You can't get rid of no-shows entirely, but you can make them rare and manageable: agree on the terms with the guest in advance, record every no-show and make decisions on facts rather than impressions. Below, step by step, is how to set this up in a restaurant of any size.

Why guests don't come

Before introducing rules, it helps to understand what a no-show is actually made of. Usually one of five reasons stands behind it:

• Plans changed, and they forgot to say or felt awkward about it. The most common and the most harmless reason. The person isn't acting in bad faith; it simply didn't occur to them that someone was holding the table.
• Booking several places at once. The guest wrote to three venues and will go to the one that answered first or had the better table free.
• A “just in case” booking. The group hasn't decided where to go yet, but a table for Friday is better grabbed in advance.
• The booking got lost on your side. It was written in a private chat, a notebook or on a sticky note, and never reached the shift. The guest arrives, there's no table, and you still shouldn't record a no-show against them.
• A mix-up over the time or date. The guest is sure you agreed on Saturday; you wrote down Friday.

The last two reasons are yours. They are cured not by strictness towards guests but by order in your records. There's more on this in the article about what to replace the paper reservation book with.

Booking and cancellation rules

Strict rules don't necessarily put guests off. Unclear ones do. For you to be able to refuse or decide calmly, the guest has to learn the terms before the booking is confirmed, not after a no-show.

The minimum set of points:

1. How long you hold the table. For example, 15 or 20 minutes after the booked time. Choose the number to suit your floor.
2. Until when a booking can be cancelled with no consequences. Be precise: “no later than three hours before” or “until 18:00 on the day of the visit”.
3. How to cancel. With one message in the same chat where the booking was made. The simpler it is, the more often guests will cancel rather than silently disappear.
4. What happens after a no-show without cancelling. For example, a note on the guest's card and more caution with their next bookings on peak evenings.
5. Special terms for large groups and holidays, if you have them.

Ready wording, and how to get it across to the guest, is collected in a separate article: booking cancellation policy: how to write one.

One important caveat. A rule works only if you keep to it. If today you hold a table for forty minutes for an acquaintance and tomorrow turn away a stranger at minute seventeen, guests will notice quickly, and the conversation about rules will become a conversation about fairness.

How to record no-shows

The main mistake here is keeping no-shows “in the manager's head”. The manager will change, the shift will end, and the information will disappear with them. It has to be recorded in writing and in one place.

What to record for each no-show:

• the date and time of the booking, the number of guests, the table;
• the guest's name and phone number;
• whether there was a cancellation, even a late one;
• who decided to count the booking as a no-show, and when.

Keep apart three situations that are easy to mix up:

If you lump all three together, your no-show numbers will be meaningless, and you'll be penalising people who warned you.

Don't call a no-show the very second the holding time runs out. Wait until it is over, contact the guest once, and only then make the note. One call or message will spare you most of the disputed cases.

A disputed case

Say a guest arrives forty minutes after the booked time and is indignant that their table was given away. If the rule “we hold a table for 15 minutes” was stated at booking and written on the card, the conversation is short: you apologise, explain the terms and offer the nearest free table or a wait. If nobody mentioned the rule, the fault lies not with the guest but with the process, and it's worth finding a table. That is exactly why the terms should be spelled out at confirmation, not after a problem.

A useful habit: once a month, look through the no-show records as a whole. You'll see which days of the week and which kinds of bookings produce the most misses. For example, bookings for large groups before holidays. Then the rule can be tightened exactly there, rather than for everyone at once.

What to do with repeat offenders

A guest who didn't come once is no reason to put them on a “blacklist”. A sensible ladder of responses looks like this:

1. The first no-show. A note on the card, with no consequences. Perhaps a short message: “We were expecting you, is everything all right?” This keeps the relationship and shows that you noticed.
2. A second no-show. You confirm bookings for peak hours only after checking with the guest. You offer a less sought-after time.
3. Habitual no-shows. You're entitled to refuse bookings for weekend evenings and to take the guest “if there's room” on the day of the visit.

Make sure that decisions rest on records, not on the mood of the shift. “We have two no-shows on record over the last few months” sounds more convincing and calmer than “you keep letting us down”.

Don't forget the other side either: regular guests with a long history of visits deserve leniency. One no-show from someone who has come many times and one no-show from someone you're seeing for the first time are different cases. How to keep such a history is described in the article about regular guests.

What a system can automate

The discipline of record-keeping rests on people, but part of the routine can be handed over to software. In the GuestKeepr virtual front desk it works like this.

• In the dashboard every booking has a “didn't come” mark, and the booking history is kept. So no-shows don't stay in someone's memory.
• The bot takes bookings in Telegram and WhatsApp and always asks the guest for a name, phone number and time. Every booking has a contact.
• The owner enters the cancellation terms, and the deposit terms if you have them, into the venue profile once. The bot tells them to the guest as text. The bot doesn't take payments and doesn't work out the deposit amount: that is your arrangement with the guest.
• If a member of staff cancels or moves a booking, the guest gets a message in their messenger (provided they have written to the bot before; in WhatsApp there is a 24-hour message window).
• The log shows who did what with a booking, so there's no arguing about who marked the no-show.

What the system doesn't do: it doesn't remind the guest of an upcoming booking and doesn't take prepayments. The decision about what to do with an offender stays with you and your team.

Frequently asked questions