A no-show on a Tuesday afternoon costs you close to nothing. A no-show on four lanes at 7pm Saturday costs you the whole evening on those lanes, plus the food and drinks that group would have ordered, because by the time you know they are not coming nobody else can take the slot.
This is why blanket policies are usually the wrong shape. The cost of a no-show varies enormously by when it lands, and your policy should vary with it.
Three different problems, one word
Cancellations are people telling you in advance. These are fine. A cancellation 48 hours out is a customer doing you a favour. Make cancelling easy, because every barrier you put in front of it converts a cancellation into a no-show.
Late cancellations are people telling you at 5pm for a 7pm booking. Partly recoverable, worth a policy.
No-shows are people who never tell you. Total loss.
If your reporting combines these, you cannot tell whether a change helped. A policy that converts no-shows into late cancellations is a genuine win and will look like nothing happened if you track one number.
The tools, ordered by friction
Reminders. Lowest friction, real effect. A booking made eleven days out is half forgotten. A reminder 24 hours ahead with a one-tap cancel converts a chunk of would-be no-shows into recoverable slots.
The detail that decides whether this works: cancelling has to be genuinely easy. If your reminder says "reply to cancel" and nobody reads that inbox on a Saturday, you have built a reminder that manufactures no-shows.
Card on file, no charge. You capture the card at booking and never charge it. Most people never get charged. The commitment effect does the work, because a booking attached to a card feels different from a booking attached to a name and a phone number.
For most centers this is the single highest-leverage change, and it requires a booking system that can capture a card without taking payment. Not all can.
Deposits. A partial payment held against the booking. Right for parties and corporate events, overkill for two lanes of open play. The reason to prefer a deposit over full prepayment on parties: full prepayment makes people shop around, and a deposit gets commitment without making the decision feel irreversible. Lucky Strike requires deposits on most event bookings with details varying by venue and size, which is a reasonable model to copy.
Full prepayment. Works, and costs you bookings. Defensible on peak weekend slots at a busy house. If you are struggling to fill lanes, this is the wrong tool, because you are adding friction to a business that needs less of it.
No-show fees. Effective, and the most likely thing on this list to produce a one-star review. If you charge them, the policy has to be visible at booking, restated in the confirmation, and applied consistently. A fee that gets waived whenever someone complains loudly is worse than no fee, because it teaches people that complaining works and it makes your staff dread the phone.
Match the tool to the slot
This is where the real gains are and it is the step most centers skip.
Saturday 7pm and Tuesday 2pm should not share a policy. Saturday 7pm is scarce, so requiring a card is justified because you will fill it regardless. Tuesday 2pm is not scarce, and every requirement you add costs you a booking you actually needed.
A shape that works for most houses:
- Peak weekend evenings: card on file, 24 hour cancellation window
- Parties and any booking of four or more lanes: deposit, regardless of timing
- Corporate events: deposit plus an invoice, because the buyer is a company with a procurement process
- Off-peak: reminders only, take the booking, do not make someone enter a card to bowl on a Wednesday afternoon
If your platform can only express one policy for the entire center, that is a real limitation worth raising with your vendor.
Head count drift costs more than no-shows
Here is the bowling-specific problem that gets less attention and often costs more.
A party books for twelve kids. Nine show up. You have staffed for twelve, ordered pizza for twelve, and set up two lanes and a party room for twelve. If your package is priced per head, you just lost a quarter of the revenue on a booking you did everything right on.
Nobody no-showed. Everyone was happy. You still lost money.
Lucky Strike puts this question directly on its party FAQ, which tells you how universal it is. The fixes are boring and they work:
Confirm head count three days out, not on the day. One message. This recovers more margin at most centers than any no-show policy.
Set a package minimum. Price the party for a minimum number of guests and let the count go up from there. If the party is sold as "eight guests included, additional guests $X," a drop from twelve to nine costs you far less.
Take the deposit against the minimum. Now the floor is already paid.
Order food against the confirmed number, not the booked number. Sounds obvious. Plenty of kitchens still work off the original booking.
Some of your no-shows are your own doing
Before adding friction for customers, check your own funnel.
If someone books online and gets no confirmation, they are not sure it worked. If the confirmation lands in spam, same outcome. If your booking form collects a phone number but reminders go by email, you picked the weaker channel. If someone tries to cancel and cannot work out how, they will simply not turn up, and you will record that as a customer problem when it was an interface problem.
Book a lane on your own site, from your phone, on a Sunday, logged out. Then try to cancel it. Most operators have never done the second part.
Pick a realistic target
Zero is not achievable and should not be the goal. People get sick, groups fall apart, plans change. Some no-show rate is the cost of taking advance bookings, and the alternative, which is walk-in only, is worse for a business where most of the money now comes from planned group visits.
Track the three categories separately, change one thing at a time, and give it a month. If you add reminders, a card requirement, and a fee in the same week and bookings drop, you will have no idea what to undo.
Written by Mathieu Morin, CRO at Bowl O'Clock. If anything here is inaccurate, contact us and we will update it.
Written by Mathieu Morin, CRO at Bowl O'Clock.