Group Reservations That Shrink: A Practical Fix

A full no-show hurts. But a table of four where eight were expected? That might be worse.

With a full no-show, you know what happened. The table sat empty, you lost revenue, and maybe you filled it with a walk-in. With a partial no-show, the table is technically occupied. You staffed for eight, prepped for eight, possibly turned away a six-top to hold the space. And now half the chairs are empty, the per-head spend is lower, and the kitchen overproduced.

This is one of the most common frustrations in independent restaurants. One operator on r/restaurantowners put it plainly: "people book for 6-8 and just don't show up. no call, no text, nothing. we're turning away walk-ins for these tables and then they just sit empty all night."

The standard no-show playbook (card-on-file, confirmation texts, cancellation fees) was built for the binary scenario: they come or they don't. Partial no-shows need a different approach.

Why partial no-shows cost more than you think

The math on a full no-show is straightforward. An empty table generates zero. But a half-empty table generates the illusion of revenue while hiding real losses underneath.

Here's what a shrinking eight-top actually costs a 40-seat restaurant on a Saturday night:

Cost Factor	Full 8-top	Shrinking to 4	The Gap
Revenue (at $65/head avg)	$520	$260	-$260
Turned-away covers	0 (table would've been empty)	4 seats you held but didn't fill	Lost opportunity
Kitchen prep	8 portions prepped	4 wasted	Food cost on 4 unused preps
Staff allocation	Appropriate	Overstaffed for actual covers	Labour cost absorbed
Per-head alcohol/beverage	$25 x 8 = $200	$25 x 4 = $100	-$100

That's $360 or more in direct losses on a single reservation, before you count the six-top you turned away to hold the space. Multiply that by two or three shrinking group bookings per week, and you're looking at $1,500-2,000 per month in invisible revenue loss.

The average restaurant no-show rate sits around 20%, and large-party no-shows make the biggest dents in profits. But partial no-shows don't show up in that statistic at all. They're a quieter problem, and most reservation systems don't even have a field for "showed up with fewer people than booked."

The reconfirmation sequence (your best tool)

Before deposits, before card-on-file, before any policy with dollar signs attached: reconfirmation. It's the single most effective move for shrinking group reservations, and it costs nothing.

SMS confirmations have a 98% open rate and are typically read within three minutes. Automated confirmation sequences reduce no-shows by 27-32%. But the standard confirmation text ("Your reservation for 8 on Saturday at 7pm is confirmed") misses the point for groups. It confirms the booking. It doesn't confirm the headcount.

Here's a three-touch reconfirmation sequence designed specifically for group bookings of six or more:

Touch 1: Booking confirmation (immediate)

Thanks for booking at [Restaurant], [Name]! We've got you down for 8 guests on Saturday, July 5 at 7:00 PM. If your party size changes, just reply to this text. See you soon.

The key: putting the party size in bold. It plants the seed that the number matters.

Touch 2: Headcount check (48 hours before)

Hi [Name], quick check-in for your reservation this Saturday at 7 PM. Still expecting 8 guests? If the number has changed, reply with your updated count so we can set the right table. Thanks!

This is the move that catches shrinking parties. You're not asking if they're coming. You're asking how many are coming. That's a fundamentally different question, and it gives guests an easy, guilt-free way to update you before it becomes a problem.

Touch 3: Day-of confirmation (3-4 hours before)

Looking forward to seeing your group tonight at 7 PM, [Name]. We're set up for [confirmed number] guests. If anything changes, give us a call at [number].

By this point, you've already adjusted the table if needed. This is a courtesy confirmation, not a headcount check. It reinforces the final number and gives a phone line for last-minute changes.

What to do when the number drops

When a guest replies "Actually, it's 6 now" to your 48-hour text, you've just recovered two covers. You can:

• Adjust the table configuration and open the freed space for walk-ins or smaller bookings
• Rearrange the floor plan to seat a two-top or four-top where the larger table was
• Reduce kitchen prep for that reservation

That 48-hour window is worth more than a $50 deposit, because you still have time to fill the gap.

Per-person deposits for groups of 6+

Reconfirmation catches the honest shrinkage: the birthday party where two friends bailed, the work dinner where schedules shifted. But it won't stop the guest who books for 10 "just in case" and always planned to bring 6.

For that, you need financial commitment. And the cleanest version is a per-person deposit.

How to structure it

Element	Recommendation
Threshold	6+ guests (smaller parties don't warrant the friction)
Amount	$20-35 per person (covers your opportunity cost without feeling punitive)
Applied to bill	Yes, always. The deposit becomes a credit toward the meal.
Refund window	48 hours before: full refund. 24 hours: 50%. Same-day: forfeited.
Partial attendance	Charge for confirmed headcount, refund the difference if they let you know 24h+ ahead

The $20-35 range is the sweet spot for Canadian independents. Most restaurants charge between $20 and $40 per person for deposits. Below $20 doesn't create enough commitment. Above $40 starts to feel like a barrier, especially for casual dining.

The 80% minimum guarantee

Some restaurants use a minimum guarantee instead of (or alongside) per-person deposits. The rule is simple: if you book for 10, you're charged for at least 8, even if only 6 show up.

This works well for semi-private and private dining, event bookings, and prix fixe or set-menu situations. It's less natural for regular table service, where charging for empty chairs feels heavier.

Making the deposit feel right

The framing matters. "We charge a deposit" sounds transactional. "Your deposit goes straight toward dinner" sounds like you're just getting started early.

Policy language that works:

For groups of 6 or more, we ask for a $25 per person deposit to hold your table. This is applied to your bill when you arrive. If your plans change, just let us know 48 hours ahead for a full refund.

Notice what's not in there: the word "fee," any punitive language, or complicated tier structures. Simple, warm, clear.

Card-on-file: the low-friction alternative

If per-person deposits feel too heavy for your restaurant's style, card-on-file is the lighter version. No money moves at booking. The card is there as a safety net, not a toll booth.

One operator described the results: "No-shows went from a weekly headache to basically never." Another noted that "every single person who drops off because of it would have been a no-show anyway. The commitment-phobes self-select out."

How card-on-file works for groups

1. Guest books for 8. Your system collects a card via a secure setup intent (the card is tokenized, not charged).
2. Your reconfirmation sequence runs as described above.
3. If the guest updates to 6 before the 48-hour window, you adjust. No charge.
4. If 4 show up without notice, you have the option to charge for the missing seats, or simply clear the card and note it in their guest profile.

The key insight: having the card on file isn't about the charge. It's about the commitment signal. OpenTable data shows deposits reduce no-shows by 57% and make guests 72% less likely to cancel last minute. Card-on-file creates the same psychological effect without moving any money.

When to actually charge

This is where Trudy's philosophy matters. A shrinking party isn't the same as a no-show. Someone showed up. They're eating at your restaurant. Charging them for the friends who bailed can turn a decent evening into a bitter one.

Our recommendation:

Scenario	Action
Guest updates 48h+ ahead	Adjust, no charge. This is exactly what you want.
Guest updates 24h ahead	Adjust, no charge. Still recoverable.
Guest updates same-day, 3h+ before	Your call. Consider partial charge or grace.
8 booked, 4 show up, no notice	Charge for 2-4 missing seats at your per-person rate.
Complete no-show	Full no-show fee per your standard policy.

The goal is protecting the table without burning the guest. If someone gave you notice (even late notice), that's a guest who cared enough to call. Reserve the charge for the ones who didn't.

Protecting against chargebacks

Once you start collecting deposits or charging no-show fees on group bookings, chargebacks become a real concern. So-called "friendly fraud" (legitimate customers disputing valid charges) accounts for up to 70% of all credit card fraud cases. And every dollar lost to a chargeback actually costs the merchant about $3.60 when you factor in fees and penalties.

Here's how to make your group booking charges chargeback-proof:

Documentation checklist

• Written policy displayed during booking (not buried in fine print)
• Guest explicitly agrees to policy at booking (checkbox, signature, or text confirmation)
• Confirmation SMS includes party size and policy reference
• Reconfirmation texts are logged with timestamps
• Any party-size changes are documented (text thread, email, call log)
• Charge matches the disclosed fee structure exactly (no surprises)

What wins a dispute

Credit card companies look for three things when a restaurant disputes a chargeback: clear disclosure of the policy before the transaction, evidence the customer agreed to it, and proof that the charge matches what was disclosed.

If your booking flow includes a clear policy statement, the guest confirms via text or checkbox, and you charge exactly what your policy says, you have a strong case. If any of those three are missing, the card company sides with the guest almost every time.

Keep it in writing

Your reservation system should log every confirmation and reconfirmation text. If a guest disputes a no-show charge six weeks later, you need to produce the text thread showing the booking, the confirmation, the headcount check, and the silence when they didn't reply or show up.

This isn't paranoia. It's just good record-keeping, and the same system that catches shrinking parties also builds your chargeback defence.

Putting it together: the group booking playbook

Here's the complete system, from booking to service:

At booking (groups of 6+):

• Collect card-on-file or per-person deposit
• Display clear policy language
• Send immediate confirmation with party size highlighted

48 hours before:

• Send headcount reconfirmation text
• If number drops, adjust the table and open freed space
• If no reply, flag for follow-up

24 hours before:

• If no reply to 48h text, send a second touch or call directly
• Update kitchen prep counts

3-4 hours before:

• Send day-of confirmation with final headcount
• Provide phone number for last-minute changes

At service:

• If fewer guests arrive than confirmed, note the discrepancy
• Decide whether to charge based on timing and communication (see the table above)
• Log everything for your records

After service:

• Update guest profile with attendance history
• Use the pattern to calibrate future policies (regular guests who consistently downsize might need a conversation, not a fee)

What not to do

A few moves that backfire:

Don't set the deposit so high it scares off bookings. A $100/head deposit on a casual dinner isn't protecting revenue. It's killing it. Match the deposit to your average per-person spend, and you'll land in the right range.

Don't charge without warning. If someone booked for 8 and 6 showed up, and you never sent a reconfirmation asking about the headcount, charging for two missing seats looks aggressive. The reconfirmation sequence is what earns the right to charge.

Don't treat every shrinking party the same. A regular who books for 6 and brings 5 is different from a first-timer who books for 12 and brings 4. Your guest CRM should track this. Patterns matter more than incidents.

Don't hide behind automation. Automated texts handle 90% of this. But when a guest calls to explain that two people in their group tested positive for COVID that morning, a human should be the one saying "no problem, we'll adjust." The system handles the routine so you can bring the warmth when it counts.

The bottom line: partial no-shows are a commitment problem, and commitment is built through communication, not just fees. A reconfirmation text that asks "still 8?" does more work than a $50 deposit. Layer them together, and you've got a system that protects your revenue without turning booking into a transaction.

See how much no-shows are costing your restaurant with our No-Show Cost Calculator.

Sources: TouchBistro, OpenTable Canada, Tableo, Hostie AI, Maitre'D POS.

---