How to Reduce No-Shows at Your Restaurant
Last updated: May 20, 2026
You built the reservation book, staffed up accordingly, prepped the mise en place, and by 7:45pm you've got three empty four-tops that were supposed to be full an hour ago. The guests didn't call. They didn't cancel through the app. They just didn't come. That's a no-show — and if it happens more than once or twice a week, it's not bad luck. It's a systems problem.
The no-show rate at most full-service restaurants runs between 10% and 20% of reservations. The National Restaurant Association has documented this pattern across concept types for years. At 15% on a 60-cover Saturday night, that's 9 guests who never walked in. At a $55 average check, that's $495 in evaporated revenue — on a single service. Multiply that by 50 weekends a year and you're looking at $24,750 in missed sales that you also had labor and food prep sunk into.
Four things actually fix this problem: automated text reminders, credit card holds on large parties, a written cancellation policy that guests see at booking, and an active waitlist that can fill gaps in real time. Done right, you can get your no-show rate from 15% down to 5% or lower within 60 days. None of these require expensive software. Most of your existing reservation system already supports them.
What this post covers: how to diagnose whether you actually have a no-show problem (vs. a data-tracking problem), the four fixes in order of impact and implementation ease, the overbooking math that some operators use as a backup strategy, and a real example from a 55-seat casual concept in Portland that cut their no-show rate by 68% in six weeks. I'll also walk through what not to do — because some "solutions" create new problems worse than the original.
How do you reduce no-shows at a restaurant?
The four highest-impact fixes: send automated SMS reminders 24 hours before the reservation (text open rates exceed 95%, cutting no-shows by 30–50%), require credit card holds for large parties, publish a clear cancellation policy at booking, and maintain an active waitlist to fill gaps. Most modern reservation systems support all of these natively.
First: Make Sure You're Actually Tracking the Problem
Before you can fix a no-show rate, you need to know what yours actually is. Most operators have a vague sense that "no-shows happen a lot," but they're not tracking the rate by day of week, party size, booking source, or time of reservation. That data tells you where the actual problem lives — and it's rarely uniform.
You have a no-show problem — but only on certain days
If your Saturday dinner service is spotless and your Tuesday lunch has a 25% no-show rate, the fix is different. Tues/Wed lunches are often booked more casually — the perceived cost of not showing is lower. Credit card holds for off-peak reservations can be a targeted fix without annoying your weekend regulars.
Large parties disappear more often than small ones
A party of 2 that no-shows costs you one table for one turn. A party of 10 that no-shows costs you your entire private dining room, a two-server section, and the prep you did for 10 covers. Large-party no-shows deserve a separate policy — specifically, a deposit or credit card hold that small parties don't need.
Third-party booking app guests no-show more often than direct-book guests
Guests who book through your website or call in have a higher commitment level than guests who tapped "Book" on Yelp between appointments. If your no-show problem is concentrated in one booking source, you know where to add friction — require email confirmation or a phone call for certain sources.
Peak-time no-shows are costing you more than you think
An empty table at 8pm on Saturday is not the same as an empty table at 11am Tuesday. If your no-shows are concentrated in your highest-demand time slots, the revenue loss and guest experience impact multiply. That's when a credit card hold for all reservations during those windows is worth the friction it creates.
The Four Fixes, in Order of Impact
Text message open rates are above 95%. Email open rates are around 20%. When you send a guest a text 24 hours before their reservation that says "Your table for 4 at Rosewood Grill is confirmed for tomorrow at 7pm. Reply YES to confirm or NO to cancel" — you are giving them the easiest possible way to let you know they're not coming. Most cancellations happen within that window. Restaurants that implement this see no-show rates drop 30–50% almost immediately. Set up a second reminder 2 hours before the reservation for the best results. Toast, OpenTable, Resy, and most major platforms support automated SMS — if yours doesn't, look at add-ons like Wisely or Yelp Guest Manager.
The average large-party no-show rate runs 20–25% without a hold, and drops below 5% with one. The card rarely gets charged — the threat of the charge is the deterrent. Set the hold amount at $15–$25 per person, applied against the final bill if they show. For cancellations with less than 24 hours notice, charge the full deposit. Communicate this clearly at the time of booking, in the confirmation email, and in the reminder text. Guests who have skin in the game cancel instead of disappearing.
Your cancellation policy needs three things: a specific deadline (24 hours is industry standard, 48 hours for large parties or special events), a clear consequence for missing that deadline (deposit forfeiture or a no-show fee), and placement at every guest touchpoint — booking confirmation, website FAQ, reminder texts, and your host stand. A policy buried in the fine print of a confirmation email doesn't count. If guests don't know they'll be charged, the charge becomes a dispute and you've got a chargeback.
Your waitlist is your insurance policy against no-shows. When a no-show or last-minute cancellation opens a table at 7:45pm, you need a warm body seated within 10 minutes or the turn is gone. A digital waitlist (Yelp Guest Manager, Nowait, or your reservation platform's built-in tool) lets you send an automatic "A table just opened — want it?" text to everyone on the list. The first to respond gets the table. No phone tag, no delay, no empty table sitting dark for 45 minutes.
The Overbooking Question: When It Makes Sense and When It Backfires
Some operators, particularly high-volume ones, overbook strategically. If your historical no-show rate on Saturday night is consistently 15%, you might book 115% of capacity, knowing the math will work out. On a 60-cover floor, that means booking 69 reservations. Most of the time, you'll end up at or near full. Occasionally, everyone shows up and you have a problem.
A safer middle-ground: release held tables to walk-ins 15 minutes after the reservation time if the party hasn't checked in and hasn't responded to your reminder. Post this policy clearly — "Reserved tables held for 15 minutes" — so it's visible at the host stand and in your confirmation messages. Most no-shows aren't going to show up 20 minutes late. Releasing the table at 15 minutes lets you seat walk-ins and capture at least some of the lost revenue.
Real Kitchen Example: Portland Casual, No-Show Rate Slashed in 6 Weeks
The operator pulled three months of reservation data. On average Saturday nights, they were losing 14–16 covers to no-shows — 7–8 per turn. At their $62 average check, that was $868–$992 per Saturday in evaporated revenue. Over 50 Saturdays a year: roughly $43,000–$49,000. They had been thinking of this as "annoying but minor." The math said otherwise.
What they did:
- Enabled automated SMS reminders through Resy (24 hours out, then 2 hours out)
- Added a credit card hold requirement for parties of 6+ with a $20/person deposit, applied to the bill on arrival
- Published a 24-hour cancellation policy prominently on their website and in all confirmation communications
- Set up a digital waitlist through Yelp Guest Manager to fill gaps from cancellations
Result after 6 weeks: No-show rate dropped from ~15% to 4.8%. Saturday cover count increased by an average of 10 covers per night from waitlist fills. Monthly revenue increase: approximately $2,400–$2,900 in recovered sales. The credit card hold was challenged by two guests in six weeks — both were resolved without chargebacks because the policy was in writing at booking.
Your No-Show Action Checklist
- Pull your actual no-show rate by day and party size — if you've never tracked it, start this week with a simple spreadsheet
- Enable automated SMS confirmations in your reservation system — 24 hours before and 2 hours before
- Require credit card holds for all parties of 6+ with a clear, written deposit policy
- Publish your cancellation policy at every booking touchpoint, not buried in confirmation fine print
- Set a 15-minute table-hold rule and post it at the host stand
- Build or activate a digital waitlist and train your host team to work it proactively
- Track your no-show rate weekly for 60 days after implementing — you need the data to know what's working
The Bigger Revenue Picture
No-shows are one revenue leak. But if you're doing this kind of diagnostic work on your dining room, it's worth running the same exercise on your kitchen. Most full-service operators with a fry station are losing $600–$1,200/month on fryer oil they're changing unnecessarily or burning through too fast. The frying oil cost calculator can show you what you're actually spending versus what a managed fryer operation should cost. And if your equipment is part of the problem, the fryer maintenance guide covers the steps most kitchens skip — steps that directly affect how long your oil lasts per fill.
Can a restaurant legally charge a no-show fee?
Yes — with conditions. You must disclose the fee clearly at the time of booking, include it in the confirmation, and send a reminder before the reservation. If a guest completes the booking and receives written notice of the policy, charging a no-show deposit is legally defensible. Ambushing guests with an undisclosed charge after the fact will result in chargebacks and bad reviews. The policy must be clear, written, and acknowledged at booking.
Does requiring a credit card scare off customers?
For large parties, rarely — if it's framed correctly. Most guests understand that a 10-top at a real restaurant requires a deposit; it's standard practice in fine dining and for private events. For smaller parties, requiring a hold can reduce bookings by 10–15% — which is usually offset by the reduction in no-shows. Test it first on your highest-demand Saturday nights before rolling it out across all bookings.
