Restaurant no-shows: the levers that actually work, and the one nobody looks at

What is the average restaurant no-show rate, and what does it cost you?

The figures quoted in France hover around 10 % of bookings not honoured, up to 15 % of revenue. They come from booking-software vendors observing their own customer base, not from a public statistics office. Your real rate depends on your neighbourhood, your sittings and above all your booking channels.

Worth knowing where those numbers actually come from, since every article repeats them without saying. In a March 2025 news agency report, Thomas Jeanjean, CEO of the booking system Zenchef, estimates that « 70 % of restaurateurs face no-shows and 10 % of bookings on average are not honoured, which represents up to 15 % of revenue ». The same report credits email and text reminders with roughly a 30 % reduction. Useful orders of magnitude, attributed and dated. Not a measurement of your restaurant.

Your own number takes ten minutes to produce, and it is the only one that will tell you whether anything you change is working.

The figure to keep is not the €2,690, it is the 8 %. Redo it every month and the curve tells you what a market average never will. One caveat on the last line: a lost cover is not a lost margin. If you want a defensible number, apply your gross margin rather than the full spend, and the result will still be uncomfortable.

Then split the rate by channel: online on one side, phone on the other. If your system cannot tell them apart, you have just found the subject of the next section.

The gap nobody looks at: the booking taken by phone

An automated reminder is sent from a record. A booking taken by phone during a rush and written in a paper diary has no record: no verified number, no email, no cancellation policy spoken out loud. That channel stacks every no-show factor at once, and it escapes measurement entirely.

Three conditions have to hold for a reminder to exist: a booking inside the software, a correct number attached to it, and an easy way for the guest to cancel. Taking the call by hand at 8:15pm on a Saturday breaks at least one of them, usually the second. What ends up on the page is a first name, a time and a party size. Nobody sends a reminder to a first name.

The second effect is the one restaurateurs underestimate most. A guest who wants to cancel calls at 7pm on a Friday. It rings out, because everyone is in the room. They do not try again. You count a no-show, when what happened was a cancellation that could not get through. Unlike no-shows, that one is measurable right now: count your unanswered calls between 6pm and 8pm. Our guide on what missed calls cost a restaurant gives the method, and the two numbers belong on the same page.

So the honest test of your setup is a single question to your booking system: what is my no-show rate on phone bookings? Getting an answer means calls end up in the book with a usable record. Not getting one is the answer. Our guide to connecting a voice agent to your booking software details what « the booking ends up in the book » really requires.

The six levers, ranked by the friction they put on the guest

These six levers run from the most painless to the most demanding. The first three cost the guest nothing and remove most plain forgetting. The card hold comes last: it does solve the problem, and it filters out part of your bookings along the way. Work from the top.

1. 1Get every booking into the system, phone ones includedA booking that exists only in a diary cannot be reminded, cannot be counted and cannot be cancelled remotely. This lever is worth nothing on its own and makes all the others possible.Effect: unlocks levers 3 to 6Guest friction: none
2. 2Read the booking back before hanging upName, day, time, party size, spelled out loud. It kills entry errors and the false no-shows that go with them: the guest who came yesterday because Thursday was written instead of Friday.Effect: removes booking errorsGuest friction: none
3. 3Automated reminder the day before, with one-click cancellingSent by your booking software 24 hours ahead. The cancellation link matters as much as the reminder itself: it converts hesitation into a freed table instead of an empty one.Effect: around −30 % according to platformsGuest friction: low
4. 4State a simple cancellation policy at every bookingOne sentence, spoken on the call and repeated on the confirmation. Knowing that a table is held for them, and that saying so is easy, is enough to change most behaviour.Effect: gives permission to cancelGuest friction: low
5. 5Keep a waiting list and call back freed slotsThis one does not lower the rate, it lowers the loss. A table released at 7pm can still be sold; the same table released at 8:45pm cannot.Effect: recovers the lost tableGuest friction: none
6. 6Card hold or deposit, targetedLarge parties, high-demand nights, set menus, New Year’s Eve. Announced before booking, handled by your booking system or payment provider, never by a number written on a pad.Effect: near-eliminates no-shows on the bookings concernedGuest friction: high, and it filters

Most restaurants that struggle jumped straight to lever 6 without ever running levers 1 to 3. It is the wrong order and an expensive one: asking for a card while your phone bookings never reach the system means paying a filter to fix a capture problem.

Can a restaurant charge a guest who does not turn up?

Yes, on one condition: it must have been announced before the booking was made. Without clear prior information, nothing can be claimed. Wording matters too. Under French consumer law, any sum paid in advance is presumed to be arrhes unless stated otherwise, which lets the guest walk away by forfeiting it.

The presumption sits in article L214-1 of the French Consumer Code and it cuts both ways: the guest who cancels loses the arrhes, but the professional who cancels owes twice the amount. Restaurateurs rarely know that second half, and it is the reason a deposit taken lightly on a fully booked night can turn against you.

An acompte works differently: it binds both sides, so the guest owes the agreed service even after cancelling. It is the right instrument for private hire and large groups, and it only exists if the word is written down. The consumer authority spells out the difference and recommends stating it in writing. Two lines in your booking conditions settle it.

A card imprint is a third thing again: not a payment, a hold released when the guest arrives. It carries a data obligation on top of the information one. The CNIL, the French data protection authority, forbids keeping the security code after the first transaction and limits retention of the number to what the operation requires. Practical consequence: this belongs to your booking system or payment provider, never to a notebook by the till.

One boundary worth naming. This is the French consumer-law framework, which governs your everyday bookings. A private hire contract or a group agreement is negotiated on its own terms, and deserves a look from someone qualified before you copy anyone’s template.

Writing a cancellation policy that fits in three sentences

A cancellation policy only works if the guest hears it. Three sentences are enough: the notice you expect, what happens if they say nothing, and how to cancel. It has to live where the booking happens, which means on the call, on the confirmation and on your booking page.

• Do let us know if you cannot make it, even an hour before: we will give the table to someone else.
• For parties of eight or more we ask for a card hold; it is only charged if nobody turns up and nobody told us.
• You can cancel by phone, or straight from your confirmation message.

The first sentence does most of the work. It offers a way out with dignity, and a guest who feels awkward about cancelling becomes a no-show instead. The second only applies if you actually run lever 6. The third is the one people forget, and it is the one that turns intention into a freed table.

The weak point is not the wording, it is repetition. These sentences have to be said on every call, including the fortieth one on a Saturday, by whoever happens to pick up. That is exactly where a written script stops holding.

What an AI phone agent changes about no-shows, and what it does not

Plainly: ImaginoVox does not cut no-shows by sending reminders. It is an inbound agent, it makes no outbound calls and sends no texts. Its effect runs through the book. Every call becomes a booking recorded with a reachable number, which is the precondition your reminders were missing.

What changes in practice starts with the record existing. The agent writes the booking into your booking software during the call, phone number included, so the reminder your system was always able to send finally has somewhere to go. The policy gets spoken on every call, without the fortieth-call fatigue. And a guest calling at 7pm on a Friday to cancel reaches someone: the agent takes the cancellation and releases the table in real time, which turns a no-show into a table you can still sell.

What it does not do, said before you ask: no day-before reminder, no text messages, no follow-up calls, no card hold taken over the phone. Those bricks stay with your booking system, and any provider telling you otherwise is selling something else. If you run TheFork, our guide on connecting an AI phone agent to TheFork covers how the booking gets into that particular book.

For the wider picture, start with our complete guide to the AI phone agent for restaurants, and put numbers on it with our pricing and ROI guide.

See our pricing or get started.