Stop losing tables to no-shows without sounding pushy

A table for four at 7:30 pm sits empty. You held it, turned away walk-ins, prepped the mise en place — and nobody showed. No-shows cost the average restaurant somewhere between 5% and 20% of nightly revenue, and most owners absorb that loss quietly because they're afraid of sounding like a debt collector in their reminder messages.

You don't have to choose between being ignored and being annoying. The right reminder sequence is warm, timely, and gives guests an easy out — so the ones who can't make it cancel instead of ghost you.

1. Send the first reminder 48 hours out, not the day-of

Most restaurants send one reminder the morning of the booking. By then, the guest has already half-forgotten and has no time to cancel gracefully. Forty-eight hours is the sweet spot: they still feel like they have options, so they're far more likely to confirm or cancel rather than simply not show up.

Keep this message short and friendly. Confirm the date, time, party size, and your address. Include a one-tap way to cancel — a reply keyword ("CANCEL"), a link, or a phone number. The goal is to make cancelling feel easy, not shameful.

2. Follow up 4–6 hours before the reservation

This is your soft confirmation nudge. By now the guest knows their day and whether they can make it. A short "We're getting your table ready — see you at 7:30!" message with a quick "Need to change anything? Just reply here" does two things: it builds anticipation and it catches last-minute cancellations before your kitchen is deep in prep.

Tone matters here. Think of it the way you'd text a friend you're meeting for dinner — not a formal notice, just a genuine heads-up. Guests respond to warmth. They ignore formality.

3. Make cancelling genuinely easy

No-shows often happen because guests feel awkward cancelling last-minute. They don't want to disappoint you, so they say nothing. Remove that friction entirely:

• Offer a reply-to-cancel option directly in the message (no login, no form).
• Frame it positively: "Plans change — just let us know and we'll free the table for someone else."
• If you take deposits, be upfront about refund windows at booking time, not in the reminder. Surprises breed resentment.

When cancelling is easy, people actually do it. That cancelled slot is infinitely more valuable than a silent no-show — you can fill it.

4. Use a waiting list to replace cancellations fast

A reminder sequence only pays off if you can turn a cancellation into a cover. Keep a simple waiting list — even a WhatsApp group or a notes app — of guests who wanted a table and couldn't get one. When a slot opens up, message the top of the list immediately.

Speed is everything here. Reaching out to a waitlisted guest within minutes of a cancellation means you can still seat them the same night. Waiting until the next morning means the table was empty for nothing.

5. Track your no-show rate by day and booking source

You can't fix what you can't see. Spend five minutes each week noting how many no-shows happened, which day they were on, and how the booking came in (phone, Instagram DM, Google, walk-in request). Patterns show up fast:

• Friday late-night bookings may no-show more than Sunday lunch.
• Bookings taken via DM with no confirmation step may ghost more than phone bookings.
• Larger party sizes may need a deposit nudge more than tables of two.

Once you see the pattern, you can tighten your reminders — or your deposit policy — in exactly the right places instead of adding friction for everyone.

---

Staying on top of this reminder sequence every single day is genuinely tedious, especially when you're also running a kitchen, managing staff, and handling the hundred other things that come with running a restaurant. That's exactly the kind of operational work you can hand off to a Sidekyk. Just tell your Sidekyk via WhatsApp which bookings need reminders, set your preferred tone and timing, and it handles the messages, tracks replies, and flags cancellations so you can move fast on your waiting list. Try it at sidekyk.ai — your tables are worth protecting.