Why people don't show up
Surveys of no-show guests say the same thing: they forgot, plans changed and cancelling felt awkward, or they booked two places and picked one. All three are fixed by a reminder that makes cancelling a one-tap, no-guilt action. Restaurants that send reminders with cancel links typically report no-shows falling from around 20% to under 5%.
The three messages that work
- Confirmation, instantly. "You're booked: Friday 14 Nov, 7:30pm, table for 4. Need to change it? Tap here." Sent the moment the booking lands.
- Reminder, 24 hours before. "See you tomorrow at 7:30. Still coming? [I'll be there] [I need to cancel]". The two buttons are the whole trick.
- Thank-you, the morning after. "Thanks for coming. If you have 30 seconds, a Google review helps us a lot." This is also how you turn a full room into a better map ranking.
Email, SMS or WhatsApp?
Email is free and fine for confirmations. SMS gets opened within minutes and is the best reminder channel; it costs a few cents per message through Twilio. WhatsApp works well in the UK and Europe but needs Meta's business API and approved templates. Start with email plus SMS for the 24-hour reminder.
Deposits and card holds
For groups of six or more, or Friday and Saturday nights, a small card hold (£10 per head, charged only for no-shows) is now normal and guests expect it. Say it clearly at booking. For weekday tables of two, reminders alone are enough and feel friendlier.
Build it yourself with n8n
If you take bookings through your own website form rather than OpenTable or ResDiary, you can run the whole system in n8n for free:
- A webhook receives the booking form and writes a row to a Google Sheet
- A workflow sends the confirmation email with a signed cancel link
- An hourly workflow finds bookings 24 hours away and sends the reminder once
- A tiny webhook handles "I'll be there" and "cancel" taps and updates the sheet
- A morning workflow emails the team today's list
- A workflow the day after sends the review request
The hard parts are the one-time links (so nobody can cancel someone else's table) and making sure nobody gets a reminder twice. Both are solved in the Restaurant Booking & Review Automations pack: five tested n8n workflows, a bookings sheet and a website form, set up in about 45 minutes.
Wording that keeps it human
Use the guest's first name, the restaurant's voice and short sentences. Never threaten ("no-shows will be charged") in a reminder; put policy at booking, warmth in reminders. Sign off with a real name.
Questions people ask
What percentage of restaurant bookings are no-shows?
Industry surveys put it between 10% and 20% without reminders, and under 5% with a reminder that includes a one-tap cancel link.
When should I send a booking reminder?
24 hours before works best for dinner. For same-day bookings, send it 3 hours before. Once is enough.
Should restaurants take deposits?
For large groups and peak nights, a small card hold is reasonable and expected. For small weekday tables, reminders are usually enough.
Can I automate booking reminders for free?
Yes, with n8n (self-hosted or cloud trial), Google Sheets and email. SMS adds a small per-message cost through Twilio.
Does this work with OpenTable or ResDiary?
Those systems send their own reminders. The n8n workflows are for restaurants taking bookings through their own website, phone or WhatsApp.