Key takeaways
- Start with the low-friction fixes: clear confirmations, reminders with a reply option and an easy way to cancel.
- Cornell research tells restaurants to make it easy to cancel or report running late, and to overbook or charge for no-shows where needed[1].
- Diners rate card guarantees among the fairest reservation policies, while short-show penalties rank as least acceptable[2].
- Text reaches almost everyone, with 91% of US adults owning a smartphone[3], but keep reminders separate from promotions[4].
Why guests do not show up
A no-show is rarely malice. Plans change, someone books two restaurants and forgets to cancel one, a group never settled on the date, or the guest tried to cancel and could not get through. That last cause is the one a restaurant controls most directly. In Cornell's survey of 1,230 frequent diners, respondents believed guests should call when plans change, yet often found it difficult to reach the restaurant to do so[5].
So the work splits into two jobs. First, make showing up or cancelling the easy default for every booking. Second, for the tables where a no-show really hurts, add a commitment the guest feels. Do the first job everywhere and the second only where your numbers justify the friction it adds.
The no-show ladder, from least to most friction
| Step | What it is | Guest friction | Use it for |
|---|---|---|---|
| 1. Clear confirmation | Instant message with date, time, party size and how to change | None | Every booking |
| 2. Reminder with a reply option | Message before the visit asking the guest to confirm or cancel | Very low | Every booking |
| 3. Easy cancel and running-late paths | A link, a text reply and a phone that is answered | None | Every booking |
| 4. Confirm or release | Prime tables released if not confirmed by a set time | Low | Friday, Saturday and holiday prime times |
| 5. Card hold | Card details taken; a fee charged only for a no-show or late cancel | Medium | Large parties, prime nights, special menus |
| 6. Deposit | Money taken upfront and applied to the bill | Higher | Holidays, tasting menus, private dining |
| 7. Prepaid ticket | Full price paid at booking | Highest | Ticketed events and fixed-price experiences |
Move up one rung at a time and measure what happens. Many restaurants find that the first four steps solve most of the problem on ordinary nights, and none of them costs anything in guest goodwill. The upper rungs are for the bookings where the cost of an empty table is high and predictable.
Steps 1 to 3: make the right action effortless
Confirmations and reminders work because they put the booking back in front of the guest with an easy way out. Phones make that cheap: 98% of US adults own a cellphone of some kind and 91% own a smartphone[3]. A reminder sent to a mobile number with reply options reaches almost every guest you seat.
Source: Pew Research Center, 2026[3]
Show the data
| Item | Value |
|---|---|
| 2011 | 35% |
| 2026 | 91% |
- Confirmation text: “You’re booked at Marlow’s for 4 on Fri at 7:30 p.m. Need to change? Reply here or tap the link.”
- Reminder text: “See you tomorrow at 7:30 for 4. Reply Y to confirm or C to cancel. Running late? Just reply and tell us.”
- Cancel link: one tap, no login, and an instant message confirming the table has been released.
- Running-late path: a reply in the reminder thread or an answered phone. Guests who can tell you they are 20 minutes late usually still come.
Keep reminders to service messages about the booking the guest made. Federal rules restrict telephone solicitations, for example before 8 a.m. or after 9 p.m. at the recipient's location[4], and the TCPA lets consumers sue for $500 per violation[6]. Adding a promotion to a reminder turns it into a different kind of message, so keep marketing separate and send reminders at sensible hours.
Step 4: confirm or release
For the tables that matter most, ask guests to confirm and release the table if they do not. The rule must be stated at booking and again in the reminder, with a deadline that leaves time to give the table to someone else.
Reminder wording: “Please confirm your table for Saturday at 8 by replying Y before 2 p.m. on Saturday. Unconfirmed tables may be released to our waitlist at 2 p.m. Need more time? Just reply and tell us.”
Call before releasing, rather than releasing silently. A quick call before a regular's table goes back on sale saves an argument at the door. At the deadline, give the host three lists: confirmed, cancelled and no reply. Only the no-reply list needs any work, and most of it is a two-minute call.
Steps 5 to 7: holds, deposits and prepayment
When a no-show costs real money, such as a party of ten on a Saturday or a tasting menu with ingredients bought in, a financial commitment changes behavior. Diners in Cornell research rated credit card guarantees, together with table-holding policies, as the most acceptable and fairest of the reservation policies tested[2]. The same research found that penalizing short-shows, where part of the party fails to appear, was the least acceptable[2].
That distinction should shape the policy. Charge for a whole-party no-show or a late cancellation, not for one missing guest at a table of six. Choose the lightest instrument that works: a card hold before a deposit, and a deposit before full prepayment. The trade-offs are compared in detail in card holds vs deposits.
Overbooking, carefully
Cornell's guidance also lists overbooking as a way to protect revenue against no-shows[1]. In a restaurant it should be gentle and based on your data. If your Saturday no-shows reliably leave a few tables empty, you can accept one or two extra early bookings on the assumption that some parties will not arrive. Do it only with a plan for the night when everyone comes, such as bar seats, a short wait with a drink on the house, or a table held back from walk-ins. Never overbook large parties, and never overbook a night with a deposit policy, because those guests are the most likely to arrive.
Example: a 30-day no-show plan
Week 1: measure
Pull four weeks of bookings and work out the no-show rate by day, party size and channel. The formulas are in normal no-show rates.
Week 2: fix the basics
Turn on confirmations and reminders with reply options, add a one-tap cancel link, and make sure the phone is answered at peak times.
Week 3: add confirm or release
Apply it to Friday and Saturday prime times only, with a deadline of 2 p.m. on the day.
Week 4: review and decide
Compare no-shows with the first week. If prime-night parties of six or more still fail often, add a card hold for those bookings and nothing else.
Example: a fictional 85-seat restaurant finds that most of its no-shows are Saturday parties of six or more booked by phone with no mobile number on file. Capturing a mobile number on every phone booking and adding confirm or release for those parties closes most of the gap without charging anyone a fee.
Make the phone part of the fix
Phone bookings deserve the same follow-up as online ones. Take a mobile number, read back the date, time and party size, and tell the guest how to change or cancel. If calls go unanswered during service, guests who want to cancel give up and the table sits empty. An SI Employee such as Ava can answer those calls, take the cancellation or change request and pass it to the host, so the table goes back on sale while there is still time to fill it.
Track whether it is working
Every rung you add should earn its place in the numbers. Keep a simple weekly sheet with four lines: bookings due, no-shows, late cancellations and tables refilled from the waitlist. Split it by Friday, Saturday and the rest of the week. After each change, give it four weeks before judging it, because a single wet Saturday or a local event can swing one week on its own.
Watch the side effects as well. If bookings fall after you add a card hold, the friction may be costing more than the no-shows did. If the number of guests replying to reminders keeps rising, the basics are working and you may never need the upper rungs. Share the sheet with the hosts who make the calls, so they can see that the two-minute confirmation round has a result.
What not to do
- Do not charge fees that were not shown to and agreed by the guest at booking.
- Do not penalize a party that arrives one or two guests short.
- Do not send reminders at midnight just because that is when the system runs its batch.
- Do not flag or refuse a guest without a record and a polite explanation; see repeat no-show guests.
- Do not make cancelling harder than booking. If booking takes one tap, cancelling should too.
Frequently asked questions
What is the single most effective no-show fix?
For most restaurants it is a reminder with an easy reply to confirm or cancel, combined with a cancel path that works at any hour. It costs nothing and catches the guests whose plans changed.
Should we take card details for every booking?
Usually not. Card holds add friction, and diners accept them best where the stakes are clear, such as large parties, prime nights and special menus. Start there and widen only if your data says so.
How far before the booking should the reminder go out?
Many restaurants send one the day before and a short one on the day for prime tables. Test the timing against your own no-show data and keep messages within sensible hours.
References
Cornell University (Sheryl E. Kimes) (2011). Customer Attitudes towards Restaurant Reservations Policies (Kimes, Journal of Revenue and Pricing Management, 2011) (opens in a new tab) ↑
Cornell University (Sheryl E. Kimes) (2011). Customer Attitudes towards Restaurant Reservations Policies (Kimes, Journal of Revenue and Pricing Management, 2011) (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), eCFR text of FCC rule (2026). 47 CFR § 64.1200 - Delivery restrictions (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 47 U.S. Code § 227 - Restrictions on use of telephone equipment (opens in a new tab) ↑