A 70-seat restaurant we worked with in Santiago ran a 12% no-show rate on Friday and Saturday covers. On an average check of 28,000 CLP and roughly 180 weekend reservations, that is about 21 empty seats per weekend that were booked, blocked from walk-ins, and never sat. Annualized, it came to just over 30 million CLP in vanished revenue — more than the restaurant paid in rent.
No-Shows Are a Timing Problem, Not a Character Problem
Owners tend to describe no-shows as a customer-respect issue. The data reads differently. When we plot cancellation timing against booking lead time, the pattern is consistent: reservations made more than nine days out no-show at roughly three times the rate of those made within 48 hours. The guest did not decide to skip. They forgot, plans shifted, and nothing in the intervening nine days asked them to reconfirm.
That reframes the fix. You are not trying to punish people. You are trying to give a long-lead booking one clean moment to either confirm or release the table while you can still refill it.
The Two-Touch Confirmation Window
We use two touches and no more. The first goes out 48 hours ahead and asks a single binary question with one-tap confirm or release. The second goes out four hours before service, confirm-only, purely as a memory aid. Adding a third touch does not reduce no-shows further in anything we have measured; it just increases opt-outs and makes the restaurant feel needy.
- 48 hours out: one-tap confirm or release, sent on the channel the guest booked from
- 4 hours out: short reminder with address and arrival note, no question attached
- Release any unconfirmed party of six or more at the 24-hour mark and open it to the waitlist
- Never send both a message and an email for the same touch — pick the channel the guest used
The restaurant above cut no-shows from 12% to 5.4% within a month of running exactly this. Nothing else changed on the floor. The recovered covers were worth roughly 1.4 million CLP per month.
A Waitlist Only Works If It Is Warm
Releasing a table at 24 hours is worthless if you have nobody to call. The waitlist has to be built before you need it. We capture parties turned away during peak service with a simple message opt-in — name, party size, preferred nights — and hold them in a list segmented by night and party size. When a Saturday four-top releases, the message goes to people who already told you Saturday was what they wanted.
A released table you cannot refill is still an empty table. The waitlist is the half of the system most restaurants skip.
Match on party size, not just availability. Offering a released two-top to a party of six wastes the guest's time and burns the list. We keep separate queues for two, four, and six-plus, and the fill rate on released tables runs near 60% when the queues are clean.
Deposits: Use Them Narrowly
Card-hold deposits work, but they suppress bookings if applied across the board. We limit them to the reservations that actually hurt: parties of six or more, holiday services, and tasting menus. On those, a modest hold cut no-shows to near zero at every property we have tried it. On standard two- and four-tops, a deposit requirement measurably reduced total bookings, which is a worse outcome than the no-shows it prevented.
Track One Number Weekly
Seated-cover rate — seated covers divided by booked covers — is the only metric worth reviewing every week. It captures no-shows, late cancellations, and waitlist recovery in one figure. Healthy full-service restaurants running this system land between 94% and 97%. If yours sits below 90%, the confirmation window is where the money is, and it is a two-week build.
Want us to look at your reservation data and size the recoverable covers? Message us at https://netwebmedia.com/whatsapp.html.
Want this working inside your own stack?
NetWebMedia builds AI marketing systems for US brands — from autonomous agents to full AEO-ready content engines. Book a free 30-minute strategy call and we'll map out the highest-ROI next step for your team.
Book a Free Strategy Call →Share this article
Comments
Leave a comment