Restaurant no-shows: the ladder that cuts them

Why a ladder works better than a fee on everything

Most no-shows are not rude guests. They are plans made weeks ahead and forgotten, a group whose organizer booked two places and picked one at the last minute, or a guest who meant to cancel and never found a quick way to do it. Each of those has its own fix, and none of the fixes needs to land on every booking.

That is the logic of a ladder. The free rungs, a confirmation and a reminder, fix the forgotten plan and give the guest who meant to cancel an easy way out. The paid rungs, a card on file and a fee that steps up, fix the double booker, because dropping one of two tables now costs something. The last rung, tables held for walk-ins, fixes whatever gets through. Climb a booking only as high as its risk, and the rest of your guests never feel the ladder at all.

What two empty tables a week really cost

The cost of a no-show is easy to underestimate, because each one feels small on the night. Take a simple case: two tables of four that do not show up each week, at a $60 average check per guest. That is $480 a week, about $1,920 over four weeks, and $24,960 over a year. Those are sample numbers; put in your own.

The real cost is higher than the empty chairs. On a full night, each no-show table is also a table you told someone else you did not have. The couple turned away at 7:30 went somewhere else and may not come back. That is why the rungs that cost a guest nothing, confirming and reminding, pay for themselves before any fee is charged.

Writing a reminder guests actually answer

A reminder works when answering it takes one second and no courage. Put the restaurant's name, the day and the time in the first line, then make letting the table go sound as normal as keeping it. Something like: see you tomorrow at 7:30 for four; reply 1 to confirm, or 9 if your plans changed and we will free the table. Short, warm and with no hint of a penalty in the wording.

On Tableify the reply step applies only where two-way texting is set up for your restaurant's number, so check that before you print the instruction anywhere. Either way, the reminder goes once, at 9am the day before or at noon on the day for later bookings, and only to guests who have not already confirmed.

Deposits: the rung for private rooms and big groups

A deposit takes money at booking, which makes it the strongest rung and the one to use most sparingly. It suits the nights you could fill twice over and the bookings that tie up a room: holiday dinners, tasting menus, event nights and large parties. A common choice is a per-person amount that is a modest share of the average check, credited toward the bill, so a guest who shows up pays nothing extra.

On Tableify a deposit can depend on party size, day, date, room, shift or experience, and it is paid straight to your own account with no cut taken. For private events, agree the headcount, the minimum and the deposit in writing and send an invoice or payment link the guest can pay from a phone; the private event software handles that part, the record sits in the restaurant CRM, and Nora answers the inquiry before it becomes a booking.

A cancellation policy a host can say in one breath

Long policies get skipped, and a skipped policy makes every fee feel like an ambush. Write yours as two or three short sentences, read it out loud, and cut anything a host could not say on the phone. Show it on the booking page and repeat it in the confirmation. A simple pattern to start from:

• Cancel or change your booking up to a set number of hours before, at no charge.
• After that, a fee per guest is charged to the card you saved, rising as the time gets closer.
• If your party gets smaller, let us know and we will adjust the booking at no charge.

The morning after a no-show

Decide before the night what happens next, so nobody improvises at the host stand. A short, friendly text the next day asking whether everything is all right brings some guests back and explains a lot of no-shows. Charge only what the policy says, only when the guest agreed to it, and note the outcome so the next booking from that guest can be handled with care.

Waive with a reason, never at random: a medical emergency, a storm, a regular with a long record. Random waivers teach guests that the policy is a bluff. Keep the record of the guest ticking the policy, because it is your answer if a charge is ever disputed. If a card fails, the payment link keeps the conversation polite and off the phone.

Counting before and after each rung

Your no-show rate is the bookings that never arrived divided by all bookings, for the same nights and the same party sizes. Count it for four weeks before you change anything, then for four weeks after each new rung, one rung at a time, because a single bad Saturday can swing a small count. Tableify's reports show the rate, so the before and after sit side by side.

Watch covers seated as well. A rung that cuts no-shows but also cuts bookings may not be a win, which is why the paid rungs belong only where your count points. The reservation system page shows where each setting lives, the reservation system checklist lists what to ask of any booking system, and the walk-in tracking page shows how to count the walk-ins that fill your held tables. The booking link most guests tap first sits on your listing, covered in the Google Maps guide.