Restaurant Operations
How restaurants cut no-shows by 60% without charging deposits
Restaurant no-show rates run 20–30%. The operators who cut that to under 10% don't take deposits — they run a 2-touch confirmation system. Here's the exact playbook.
A 28% no-show rate is the industry default at most independent restaurants without a confirmation system. That number sounds like an inevitability — like weather. It's not. It's an attention failure.
The operators we work with cut their no-show rate from 28% to 11% in the first 30 days. Not by charging deposits. Not by cracking down on cancellations. By running a 2-touch confirmation sequence that takes the diner zero effort and the host zero time.
Here's the exact playbook.
Why deposits are the wrong answer
The first instinct most operators have when they discover the no-show rate is to bolt on a deposit policy. "$25 hold, refunded at the table."
It works. It also costs you 8–12% of the bookings that would have come through. People hate giving credit cards to small restaurants. The diner who's torn between three places picks the two that don't ask for one.
A deposit policy is a tax on the friction of trust. It works as a final fallback for high-value Saturday-night reservations. It is a terrible default for Tuesday-night bookings.
The 2-touch confirmation sequence does the same job at zero friction cost.
The 2-touch sequence
This is the same cadence used by every well-run restaurant group in the country.
Touch 1 — T-24h. Soft confirmation.
"Hi [Name], looking forward to seeing you tomorrow at 7pm at [Restaurant]! We're holding a 4-top under your name. If anything's changed, just reply CANCEL or RESCHEDULE and we'll sort it. — [Host]"
This message does three things:
- Reminds them the booking exists. Most no-shows are forgetting, not deliberate.
- Anchors the commitment by naming them, the time, the party size, and the restaurant.
- Opens an out — counterintuitively, this reduces no-shows. People who can't make it now have a friction-free way to cancel, freeing the slot for a walk-in.
Sent 24 hours out gives you operational lead time. Cancelled tables can be re-released to walk-in or refilled by waitlist.
Touch 2 — T-1h. Final reminder.
"[Restaurant] — see you in an hour! We're at 142 W 17th, between 6th and 7th. Order anything from the bar starting at 6:45 if you're early."
This one is short, warm, and operationally useful. The address detail prevents the "I couldn't find parking" excuse. The bar offer pulls early arrivals into revenue immediately.
Together, these two touches reduce no-show rate from 28% to ~11%.
The math is straightforward: forgetters get reminded, intentional cancellers get released, and the small fraction of true no-shows shrinks to people who genuinely had emergencies.
Reservation rebook (the multiplier)
When a guest does cancel via the T-24h flow, you have a saved 4-top with 24 hours of lead time. That's a re-fillable slot.
The fastest restaurants run a third sequence on top:
Cancellation rebook — fired the moment a cancel comes in.
"Hey [Name], no problem on tonight! Want me to hold your spot for next week? Same time, same table — just reply YES."
This converts about 34% of cancels into rebooks. Out of 100 reservations, you went from 72 to 89 actually-attended dinners. Not by stopping the cancellations — by converting them into the next booking.
Bringing back the regulars
The other half of restaurant revenue automation is the regular who hasn't been in for 60 days.
This is your highest-LTV cohort. Someone who came in twice in 30 days and then disappeared isn't lost — they got busy, switched to delivery, or are testing the new place down the street. They will come back if you ask.
The win-back message that converts at 18–22%:
"Hi [Name], we noticed you haven't been in for a while — wanted to make sure you weren't avoiding us 😅. If you'd like to come back this week, we've got 8pm Friday open and we'll comp dessert. Just reply YES."
Two operational keys:
- The free dessert is a $4 cost item. It's not a discount — it's a host-comped courtesy. Anchors goodwill at almost no margin cost.
- Specific slot offer is what makes them book this time. "Come back anytime" gets ignored. "Friday at 8pm" gets a reply.
Restaurants running this win-back sequence to a 200-regular list typically rebook 25-40 of them per month.
What to suppress
Three rules that separate professional restaurant communication from spam:
- Never message during service hours. A 7pm "we miss you!" text to a regular while their phone is on the table during a meal at a competitor is a catastrophic moment. Window your sends to 9am–5pm only.
- Suppress on recent visit. A guest who came in last Saturday should not receive a "we miss you" message on Monday. Suppress until at least 14 days post-visit.
- Limit frequency. No more than 2 marketing messages per regular per month. Beyond that, you're training them to mute you.
Where Alfred fits
Alfred runs all three sequences — the T-24h and T-1h confirmations, the cancellation rebook, and the regular win-back — automatically. It pulls reservations from Resy, OpenTable, Tock, or whatever you use (any URL-based system works), drafts the messages in your restaurant's voice, and queues them for your one-click approval each morning.
A typical restaurant running Alfred sees their no-show rate drop from 22-28% to 8-12% in the first 30 days, plus 25-40 regulars rebook from win-back per month. At a $65 average ticket, that's $5K-10K/month in recovered revenue per location.
See Alfred for restaurants → — or start a free trial and have your first confirmation sequence running tonight.
