Restaurant Reservation Confirmations and No-Show Reminders

A restaurant no-show reminder service sends each guest a confirmation when a booking is made, then sends timed reminders that let the guest confirm, change or cancel by simple reply. An AI worker takes requests from the web booking form, WhatsApp messages and phone-call notes, checks each one against the reservation book, and writes every outcome back to that book. Anything outside the rules goes to the host team. Deposit and card-hold decisions stay with the manager. Published figures on reminders are mixed. The Resos No-Show Index 2026 links a delivered SMS reminder with a 16% lower recorded no-show rate, but that is an observed association, not a controlled test. The useful step is to measure your own rate before and after, and the free audit does that with your figures.
In short
- A confirmation and timed reminders with a reply option address forgotten and unnecessary no-shows together.
- The Resos No-Show Index 2026 links delivered SMS reminders with a 16% lower recorded no-show rate, as an association only.
- WhatsApp reminders must use Meta-approved templates and an opt-in from the guest.
- Deposits, card holds and refunds stay with the restaurant manager.
- Measure your own no-show rate first; the free audit uses your figures, not averages.
What the service does
Most lost tables come from two situations. A guest forgets the booking, or a guest's plans change and cancelling feels like too much effort, so the table sits empty. A confirmation and reminder service addresses both. Each booking is confirmed when it arrives, reminders are sent at set points before service, and the guest is given an easy way to answer. The worker records the answer in the reservation book so the host stand is working from the same information as the guest.
Who it is for
The service suits any restaurant, bar or café that takes table bookings, whether one site or several. It is most useful where requests arrive through more than one channel. A web form, a WhatsApp number and a phone line that one person answers between tasks is the usual pattern where bookings drift. A group with several sites benefits when each site uses different habits for confirming bookings. The same rules can be applied to every site from one setup.
What is included
- One intake queue that collects booking requests from the web form, WhatsApp Business messages, and notes taken from phone calls.
- A check of each request against the reservation book for date, service period and party size, using the rules the restaurant sets.
- An immediate confirmation that repeats the date, time, party size and restaurant name.
- A reminder sequence timed around each service period, with a reply option on every message.
- Reply handling for confirm, change within your rules, and cancel, with the reservation book updated after each reply.
- A log of every message sent and every outcome, so a host can see why a booking changed.
- A hand-off to the host team, with the guest's request attached, for anything the rules do not cover.
- A decision queue for deposits and card holds. The worker presents the request to the manager. It does not take, hold or refund any payment.
- A weekly summary of confirmed, changed, cancelled and unconfirmed bookings.
How the service runs
The work follows five stages. Each stage ends with a decision the restaurant signs off before the next one starts.
- Audit. The free automation audit reads your current booking flow, the channels you use, how many requests arrive in a typical week, and where no-shows and late cancellations happen. You receive a short written view of what is worth automating.
- Process map. The steps are written down in plain language. Who confirms, who changes, who decides on deposits, what happens to an unanswered reminder. You check the map line by line.
- Build. The intake channels are connected, the reminder wording and timing are set, the reply options are configured, and the reservation book connection is tested with dummy bookings before any guest sees a message.
- Run. The service goes live for one service period first. The host team checks the log each day for the first weeks, and the rules are adjusted where the log shows a gap.
- Support. Changes to opening hours, menus, service periods or message wording are handled as updates. The weekly summary is reviewed by the manager.
Why reminder timing matters
The Resos No-Show Index 2026 covers 3,768,761 reservations across 2,417 restaurants between August 2025 and July 2026, and puts the average recorded no-show rate at 2.33%. The same index found that reservations with a delivered SMS reminder had a 16% lower recorded no-show rate than the same restaurants' bookings without one. The index describes this as an association rather than a proven effect. Higher reductions of 30 to 50 percent circulate in vendor marketing, but the published method behind them is not clear, so this page does not use them. Your own rate is the only reliable baseline.
Timing needs testing too. Resos reports that its platform sends reminders the night before, on the morning of service, and two hours out, each with a one-tap confirm or cancel link. Resy's help centre describes a confirmation text sent at fixed times by service period, with a follow-up if the guest does not reply. Both show that the schedule is a setting, not a fixed rule, and it should match your own service pattern.
WhatsApp and text rules
WhatsApp is not a free-for-all channel. Meta's WhatsApp Business documentation states that a message template must be approved before it is sent, that a template is required to message a user outside the customer service window, and that the recipient must have opted in. Appointment reminders are one of the template categories Meta lists. The reminder wording therefore has to be drafted as a template and approved before go-live. Text message consent rules differ by country, so the restaurant should confirm the rule with its own regulator and record how each guest agreed to be contacted.
What the restaurant provides
The service depends on a few inputs that only the restaurant can give. Without them, the worker cannot make a sound decision.
- Access to the reservation book, either a login with the right permissions or a regular export that the team agrees to supply.
- Opening hours, service periods, table layout limits and the party sizes that need manager approval.
- A WhatsApp Business account and the phone numbers used for bookings.
- Approved reminder and confirmation wording, and the guest consent wording used on the web form.
- Named contacts in the host team and the manager who decides on deposits and card holds.
- Your current no-show and late cancellation records for at least one recent period, so the results can be compared.
Timeline
No public source sets a standard number of weeks for a booking automation project of this kind, so this page does not quote one. The length is set in the audit, once the number of channels and the state of the reservation book are known. The table shows the order of work and what each stage delivers.
| Stage | What it delivers | Length |
|---|---|---|
| Audit | Written view of channels, volumes and no-show points | Set at the audit |
| Process map | Agreed rules for confirm, change, cancel and hand-off | Set at the audit |
| Build | Connected channels, approved templates, tested reservation book link | Set by the number of channels |
| Run | Live service period with daily log review | Starts after sign-off |
| Support | Updates to rules, wording and weekly summary | Ongoing |
What this does not cover
- Deposits, card holds, refunds and no-show fees. The worker flags them for the manager and does not act on payment.
- Walk-in guests, waiting lists and table allocation on the floor.
- Judgement calls on sensitive requests, such as a complaint, an allergy emergency or a guest who is upset. These go straight to a person.
- Accurate handling of every phone call. Phone requests depend on the call being captured and transcribed, and the host team checks any unclear booking.
- Bookings made without a mobile number. Reminders can only reach guests whose number was captured at booking, so those bookings need a manual check.
- Results. The outcome depends on your current booking pattern, your guests and your own figures, which the free audit measures before anything is built.
Sources
- How to reduce restaurant no-shows (13 strategies)
- Do AI Reservation Assistants Really Reduce No-Shows? A Data-Driven Look at SMS Reminder Impact
- How to Reduce No-Shows in Your Restaurant
- How to Reduce Restaurant No-Shows With Smart Reminders — StackBloom Blog
- How to Reduce Restaurant No-Shows (Without Being Annoying)
How AiStaffo would automate this
AiStaffo would connect the web booking form, the WhatsApp Business number and a log of phone-call requests into one intake queue, then check each request against your reservation book for date, service period and party size. The worker sends the confirmation and the timed reminders, reads each reply, and updates the book for confirm, change or cancel within the rules your team sets. Anything outside those rules, and every deposit or card-hold question, is passed to the host team or the manager with the guest's details attached. You still approve the reminder wording, the rules and the weekly summary, and you decide what happens to each flagged booking. Book a free automation audit.
Questions people ask
How much can reminders reduce no-shows?
Can guests change a booking by WhatsApp?
Do I need approval from Meta before reminders go out on WhatsApp?
Does the worker take deposits or card holds?
Can the service handle phone bookings?
What does the restaurant need to provide?
Book a free automation audit
Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.
































