How to reduce no-shows at your restaurant without picking fights with guests
A practical guide with five proven tactics to cut your no-show rate — from reminders to card pre-authorization — with their trade-offs.
No-shows are one of the most expensive and quietest problems in the restaurant business. A booked table that doesn’t show up isn’t just food prepared for no one: it’s a table you didn’t offer to another guest who would have shown up. And yet, very few places tackle it rigorously.
Let’s walk through the tactics that actually move the needle, in increasing order of friction.
1. Well-calibrated reminders
The cheapest and most underrated weapon. A reminder by email 24 hours before and one by SMS 2 hours before typically cuts the no-show rate by 10–20%. Not because the guest fully forgot, but because receiving a message on the morning of the service gives them the opportunity — and the nudge — to cancel if they already know they can’t come.
Tone matters: the reminder must include an obvious cancellation link so they don’t have to call. Many restaurants only confirm the time, which is worse than not reminding: if a guest can’t cancel without picking up the phone, they won’t cancel, and won’t tell you they’re not coming.
2. A clear, public cancellation policy
The second lever: tell them what happens if they don’t show. A visible line in the widget and the confirmation email — say, “cancellations with less than 3 hours notice will count as a no-show” — reduces no-shows from on-the-fence guests, the ones who already suspected they might not come.
It’s not a threat: it’s information. Guests who see this and still book are implicitly accepting the rules. It’s also the foundation for the card-based tactics.
3. Ask for a card to book (without charging)
Asking for a credit card at booking time — even without charging — reduces no-shows by 30–50%. Not from fear of an actual charge, but from the psychological effect of “this restaurant takes my booking seriously, so should I”.
The trade-off is friction: asking for a card on every booking reduces total bookings. Most restaurants with serious use of this apply it only on risk scenarios: weekend dinners, large parties, days before holidays.
4. Real card pre-authorization
Same as above, but with funds actually held. When the guest books, Stripe holds an amount on their card (say, €20 per person). If they show up, it’s released. If they don’t, it’s captured automatically per your policy.
This works because the guest sees the hold on their account. The message is no longer psychological — it’s material. Restaurants applying pre-auth on risk services get no-shows down to 3–5%, vs 15–25% in the unprotected baseline.
The usual objections:
- “Guests get offended”. The ones who plan to come, don’t. The ones who don’t, do — and they’re exactly who we want to filter.
- “It’s legally complicated”. Not if you use tools that are SCA / 3-D Secure compliant and clearly show the amount before confirming. It’s a payment flow recognised by Visa, Mastercard, and Amex.
- “My PMS doesn’t support it”. Some systems, like Reserver, ship with it built-in via Stripe.
5. Automatic waiting list
Technically not a no-show reduction, but it fixes the same problem: empty tables from failures. When someone cancels, Reserver automatically alerts the first person on the waiting list via email and SMS. If they accept within 15 minutes, the table fills up.
The combined effect of waiting list + pre-auth is powerful: not only do you deter no-shows, but when they happen, you don’t lose the seat because someone else was waiting.
Which tactic when
| Tactic | Implementation effort | Expected no-show reduction | Guest friction |
|---|---|---|---|
| Reminders | Low | 10-20% | None |
| Clear policy | Zero | Another 5-10% | None |
| Ask for card (no charge) | Medium | 30-50% | Medium |
| Real pre-authorization | Medium | 70-85% | Medium-high |
| Waiting list | Low | Indirect | None |
Our recommendation for restaurants starting out: turn on reminders + policy + waiting list from day one, on every service. Add pre-authorization only on the actual risk services (weekend dinners, holidays, large parties) at 4–6 weeks in, once you have comparable data.
If you want to see how this all gets applied concretely in Reserver, we have a dedicated page on no-show prevention.