Restaurant No-Shows: Confirmations, Deposits and Waitlists

The most reliable way to cut restaurant no-shows is a clear workflow: confirm every reservation straight away, remind guests at a set time with a one-tap way to cancel, take a deposit or card hold only where the risk justifies it, and offer released tables to a waitlist quickly. Automation runs the timing. People handle exceptions, disputes and every allergy answer.

Most reservation platforms already include pieces of this. The trouble is that the pieces rarely join up. Our broader guide to restaurant automation covers bookings alongside scheduling, ordering and tips. This post goes deeper on one workflow, from the moment a table is booked to the moment the guest sits down or does not arrive.

Key takeaways

Most no-show work is timing: confirm at booking, remind at a set point, and make cancelling as easy as booking so tables come back in time to re-offer.
Online card holds usually last about seven days, and Visa merchant-initiated holds less, so a hold taken at booking may expire before a table weeks away.
Cancellation fees must be proportionate: UK and EU unfair terms rules flag terms that make consumers pay disproportionately high compensation.
Allergy notes are health data in GDPR terms, so collect them for the visit, pass them to a trained person and do not keep them on a profile by default.

Why the no-show workflow breaks today

Restaurant no-shows are rarely malicious. Plans change, people book at two places, or a group organiser forgets to say half the party dropped out. The venue simply finds out too late. The same patterns come up again and again:

Cancelling is harder than booking. Booking takes seconds online; cancelling means finding an email or phoning during service.
Replies go nowhere. A guest replies "we're now four, not six" to a no-reply address, and the floor plan never changes.
Deposits are all or nothing. Charge everyone and casual diners go elsewhere; charge nobody and you absorb empty tables for eight on a Saturday.
Waitlists live in people's heads. When a table frees up, the host has to remember who asked and call them while seating walk-ins.
Allergy notes get lost. They sit in a free-text field nobody reads before service.

The fix is clear rules about timing, money and handovers, applied consistently.

The restaurant no-shows workflow, stage by stage

Each stage has a trigger, an action and a person who reviews or decides.

1. Booking made: confirm and capture the right details

Trigger: a reservation arrives online, by phone or through a third-party platform.

Action: an immediate confirmation with date, time, party size, address, the cancellation policy in plain words and a change or cancel link. The record captures a mobile number, preferred channel and an optional field for allergies or access needs.

Who reviews: a manager, for large parties and exceptions only. Keep the confirmation free of promotions, for the consent reasons covered below.

2. Deposit or card hold: only where the risk justifies it

Trigger: the booking matches a rule you set, such as a party of six or more, a set or tasting menu, or a peak service.

Action: the guest is asked for a deposit or card details at booking, with the policy stated before they pay.

Who decides: the owner or general manager sets the rules and the amounts. Staff can waive or refund within limits you agree.

Know how card holds behave. Stripe's documentation on placing a hold on a payment method says an online card authorisation is usually valid for seven days, and about five for Visa merchant-initiated transactions. A hold taken three weeks ahead expires long before the date, so many systems save the card instead and charge it only under the published policy. Check what your providers support.

3. Reminder: ask for a reply, not just attention

Trigger: a time you choose, for example the day before, plus a same-day message for large parties.

Action: a reminder with three options: confirm, change, or cancel. Each reply updates the booking.

Who reviews: a host sees bookings that have not replied, largest first, and decides who gets a call.

4. Cancellation or change: release the table fast

Trigger: the guest cancels or reduces their party size.

Action: the seats go back into availability straight away. If the guest is inside the fee window, the record is flagged rather than charged automatically.

Who decides: a manager reviews any fee before it is taken, especially where the guest gives a good reason.

5. Waitlist offer: first come, first served, with a short timer

Trigger: a table frees up that matches someone on the waitlist.

Action: the next guest in line gets an offer with a short time to accept, say fifteen or thirty minutes. If they do not reply, it moves to the next person. Accepted offers become normal bookings.

Who reviews: the host can override the order, but the default stays transparent.

6. Allergy and access notes: route to a person, then to service

Trigger: the booking contains an allergy, dietary or access note.

Action: the note goes to a trained member of staff, never answered automatically. Once confirmed, it appears on the service sheet and kitchen ticket.

Who decides: the chef or duty manager, and staff check again with the guest at the table.

7. On the day: the no-show itself

Trigger: the guest has not arrived after your grace period.

Action: the host marks a no-show. A polite message is drafted and any fee is flagged for approval.

Who decides: the manager. Automation never charges a fee or bans a guest on its own.

Who does what: the workflow at a glance

Stage	What is automated	Who checks or decides	Typical systems
Booking	Confirmation with policy and change or cancel link	Manager for large parties and exceptions	Reservation platform, website booking widget
Deposit or card hold	Asking for payment or card details under set rules	Owner sets rules; staff waive within limits	Reservation platform, payment provider
Reminder	Message with confirm, change or cancel options	Host calls large or silent bookings	Reservation messaging, SMS or email
Cancellation	Releasing the table, flagging fees	Manager approves any fee	Reservation platform, payment provider
Waitlist	Timed offers in order	Host can override order	Waitlist feature or simple form plus messaging
Allergy notes	Routing to staff and onto service sheets	Chef or duty manager confirms every answer	Reservation notes, kitchen display or printed tickets
No-show	Marking and drafting a follow-up message	Manager decides on fees and future bookings	Reservation platform

What stays human

The rules in this workflow are yours, and so are the exceptions. In line with how we approach automation for restaurants and hospitality, these decisions always stay with people:

Every allergen and dietary answer. Automation never tells a guest a dish is safe.
Complaints, refunds and disputes. A guest who missed a booking because of a family emergency deserves a person.
Fees and blocks. Charging a fee, keeping a deposit or refusing future bookings is a manager's call each time.
Waitlist overrides. Judgement about regulars, accessibility and the shape of the room.

Fair deposits and cancellation policies

A deposit or no-show fee is a contract term, so consumer law applies. The detail differs by country, so check the rules where you operate. Some examples:

UK: under the Consumer Rights Act 2015, Schedule 2 lists terms that may be unfair, including letting a trader keep sums paid when a consumer cancels, and making a consumer pay a disproportionately high sum. The CMA's unfair contract terms guidance explains how this works in practice.
EU: the Unfair Contract Terms Directive contains a similar indicative list, applied through each member state's national law.
US, Canada and Australia: consumer and fee disclosure rules are set at state, provincial or national level. Take local advice.

A fair policy is one a guest understands before paying: the amount, when it applies, a reasonable free cancellation window, and a charge in line with what an empty table actually costs. Work out your current no-show rate from a few weeks of bookings with the free percentage calculator before deciding whether deposits are worth the friction.

Data protection and messaging rules

Allergy notes are sensitive data

Under the GDPR, data concerning health means personal data related to someone's physical or mental health. The ICO's guidance on special category data explains that processing it needs an Article 9 condition. A named guest's recorded allergy is very likely to qualify. In Canada, the Office of the Privacy Commissioner says organisations generally need express consent for sensitive information.

So ask for allergy details for this visit, explain why, limit who can see the note, and do not copy it onto a long-term guest profile unless the guest clearly agrees. The food rules still apply too. In the EU, Regulation 1169/2011 requires allergen information for non-prepacked food, and in the US the FDA lists nine major food allergens, with allergen notification provisions in the FDA Food Code where states adopt it.

Confirmations versus marketing

Confirmations and reminders are service messages. Add promotions and different rules can apply:

US: the FCC's enforcement advisory on robotexts explains that the TCPA bars autodialed texts to mobiles without prior express consent, which the sender must prove. Marketing texts need prior express written consent.
Canada: CASL exempts purely transactional messages, such as confirming a booking the guest asked for, from the consent requirement, but sender identification still applies. The CRTC's CASL pages are the starting point.
Australia: factual messages can be sent without consent, but adding promotional links can make the whole message commercial, as Clayton Utz explains in its summary of the Spam Act and the Ticketek case.
UK and EU: marketing emails and texts generally need consent under PECR and national ePrivacy rules. The ICO's guide to PECR covers the UK.

Keep "your table is confirmed" and "try our new tasting menu" in separate workflows. And check confirmations arrive: run the free email deliverability checker, because a reminder in spam is no reminder. See why emails go to spam for fixes.

How to start small and measure

You do not need to switch everything on at once. A sensible order:

Turn on what your platform already does, with a working change and cancel link.
Route replies to a monitored inbox, not a no-reply address.
Add the waitlist. A QR code at the host stand lets walk-ins join without queuing at the desk.
Introduce deposits for one segment, such as large parties, and review complaints after a few weeks.
Connect allergy notes to service sheets, testing during quiet services first.

Measure with your own data: no-show rate by service and party size, tables re-booked from the waitlist, reminder replies and fee complaints. Tag promotional booking links with the UTM builder to see which channels bring guests who actually turn up.

Make It Flow maps how bookings move through your venue today and checks what your systems genuinely support before suggesting anything new. If you would like a second pair of eyes on your workflow, talk to us.

FAQ

How do restaurants reduce no-shows without deposits?

Send a confirmation at booking and a reminder before the visit, each with a one-tap way to confirm, change or cancel. Follow up by phone with large parties that do not reply. Making cancellation as easy as booking means you hear about changes in time to re-offer the table, which helps even without any charge.

Is it legal for a restaurant to charge a no-show fee?

In many places, yes, if the policy was clear before booking and the amount is proportionate. UK and EU unfair terms rules flag terms requiring consumers to pay disproportionately high compensation, and US, Canadian and Australian rules vary by state, province or country. Check the rules where you operate and take advice before setting fees.

What is the difference between a deposit and a card hold?

A deposit is money taken at booking, usually deducted from the final bill. A card hold reserves an amount without charging it. Online card holds typically expire after about seven days, so for bookings further ahead, many systems save the card instead and charge only under the published no-show policy, with a manager approving it.

How should a restaurant waitlist work?

Guests join with their party size and preferred times. When a matching table frees up, the next person gets a message with a short time to accept, then the offer moves on. Hosts should still be able to override the order. Accepted offers become normal bookings with their own confirmation and reminder.

Can automation handle allergy notes in reservations?

It can collect allergy notes, route them to a trained member of staff and put the confirmed requirement on the service sheet and kitchen ticket. It should never tell a guest a dish is safe. Under GDPR, allergy information about a named guest is likely to be health data, so collect it for the visit and limit who can see it.

Do booking reminder texts need consent?

It depends where you operate. Purely transactional reminders are treated differently from marketing in most countries, but the rules differ. In the US, the TCPA requires prior express consent for autodialed texts. In Canada and Australia, transactional or factual messages have exemptions, but any promotional content changes that. Keep reminders free of marketing.