Almost everything written about no-shows is some arrangement of four ideas: take money up front, send reminders, make cancelling easy, refill the gap. That is the map, and we have already drawn it — the-no-show-playbook sets out the four layers and how they stack on each other.
This is the other half. Nine specific changes, in the order they pay off, each with the thing it cannot do. It is the version to work through on a Tuesday morning with the settings screen open, rather than the version to nod along to.
One distinction has to come first, though, because most articles on this subject skip it — and they skip it because the software behind them works the opposite way from ours.
Two remedies, and they fail at opposite ends
There are two ways to make an empty chair cost something to the person who emptied it.
A deposit is money taken at the moment of booking. It exists before the appointment does. Nobody has to decide later whether to charge it; the only decision is whether to give it back, and that decision is governed by a notice window agreed in advance.
A card on file is a card stored at booking and charged after the appointment is missed. No money changes hands up front, so nothing deters the booking — and then a fee is levied against a stranger's card for a service they did not receive.
We should be plain about which of the two we do, because it shapes every recommendation below. VoltsBook takes deposits. It has no card-on-file mechanism — no stored card, no charge-after-the-fact, no automated no-show fee. That is a real difference from most of this market: GlossGenius, Phorest, Boulevard, Mangomint, Zenoti, Mindbody, MoeGo and Gingr are all built around a card held on file with a fee charged against it, and when their content marketing says "charge a no-show fee" it means something we do not do.
So this guide is written for the deposit shape. Where the card-on-file shape is genuinely better, it says so.
The failure modes are the useful part. A deposit fails at the front: some people reach the payment screen and leave, and a share of those were people you actually wanted. A card on file fails at the back: the customer disputes the charge, and between the chargeback fee and the review they write, the remedy costs more than the gap did. An invoice sent after the fact fails simply by not being paid, and it puts you in debt collection against someone you would like to see again.
There is a constraint worth knowing before you design around either, and it comes from two competitors' own documentation rather than from us: both Zenoti's and Timely's help centres record that on their platforms deposits and no-show fees are mutually exclusive — a business configures one or the other, not both layered together. Two independent vendors documenting the same limitation suggests it is a real product constraint rather than an oversight, and it is worth checking against whatever you use before you plan on stacking the two.
The nine changes
1. Take money at booking, on the services where a gap hurts
This is the only change on the list that alters the psychology of the appointment rather than managing it. A person who has paid something has made a decision. A person who has only picked a time has expressed a preference, and preferences move.
Everything else here manages memory, logistics and recovery around a decision that has or has not been made. That is why it is first, and why the other eight are worth less on their own.
The mistake is applying it everywhere. A fifteen-minute appointment that goes unfilled costs fifteen minutes; a four-hour one costs the afternoon. Put deposits on the second kind and leave the first frictionless — the extra screen is a real cost, paid by every honest customer, and it should only be charged where the gap it prevents is expensive. In VoltsBook a deposit is set per service for exactly this reason.
What it cannot do: it does nothing about forgetting. A customer who paid a deposit and then genuinely lost track of the date still leaves you with an empty chair; you just get to keep twenty pounds of it.
2. Size it to the slot, not to your instinct
The instinct is to ask for half. The number that works is nearly always lower.
The deposit's job is psychological, not financial. No realistic deposit compensates you for a lost afternoon, so stop trying to make it compensation and start treating it as the thing that converts a possibility into a plan. That conversion is bought cheaply. Past the point where people hesitate at the payment screen, raising the amount buys you nothing extra and quietly costs you bookings from the honest majority.
For a £40 service, £10 does most of the work. The reasoning is worked through properly in deposits-and-no-shows.
It is worth reading a competitor's advice next to that, because it points the other way and the disagreement is instructive. According to Acuity Scheduling's own guidance on setting up payment policies, read on 18 August 2026, that vendor recommends requesting 20 to 50% of the total appointment cost as a deposit. On a £40 haircut the bottom of that range lands near where we would put it; the top of it does not, and on a £400 job the top of that range is a serious sum to ask a new customer for on a first booking. Both positions are defensible. Ours is that the amount should be set by what the empty slot costs you, not by a share of the price.
The scale does run further than most people push it, though. On genuinely large work — a full-day detail, a multi-hour colour correction — the deposit stops being a token and becomes a real share of the price, in the hundreds where the job is in the thousands. At that end you are not nudging the forgetful; you are filtering the uncommitted before they cost you a whole day. The worked arithmetic for the biggest version of this is in ceramic-coating-pricing.
What it cannot do: a well-sized deposit will not survive a badly-worded booking screen. Which is the next one.
3. Say what happens to the money in the same sentence as the button
The largest cause of abandoned bookings at the payment step is not the amount. It is not knowing whether the deposit comes off the final bill.
A customer who cannot tell assumes the worst — that this is a booking fee on top of the price — and a booking fee is priced very differently in the head from a prepayment. One sentence beside the button fixes it: this comes off your bill on the day.
The same sentence has to cover the other half: what happens if they cancel. A deposit that is kept whatever the customer does is a surcharge, and customers shop it as one. The shape that reads as fair is the one that is fair — cancel or move outside your notice window and the deposit follows the booking or comes back; inside the window, it is kept.
What it cannot do: wording will not rescue a policy that is genuinely unfair. If your window is 72 hours for a haircut, no phrasing makes that read well.
4. Confirm immediately, and make the confirmation findable
The booking screen is not proof. It is a page the customer closed.
A confirmation message sent the moment the booking is made does two jobs at once: it catches the mistyped date while the customer still remembers what they meant, and it puts a searchable record in their inbox or their texts, which is where they will look at 8am on the day. It is the cheapest message you will ever send and the one most often left switched off because it feels redundant.
What it cannot do: it will not be read on the day. That is a different message.
5. Send one reminder, and make sure it can act
Simple forgetting is the second-largest cause of no-shows and the cheapest to address. One reminder the day before covers most trades.
The design rule that matters more than the timing: a reminder must let the person do something. A message that says "you have an appointment tomorrow" to somebody whose plans have changed produces a no-show you knew about in advance and could do nothing with. The same message carrying a reschedule link produces a freed Tuesday slot by dinnertime, which is a slot you can still sell.
One reminder is right for most work. A second on the morning is defensible for long or expensive appointments where the loss is large. Beyond that you are training people to ignore your messages, and the training works.
Which messages an appointment actually needs, and what each is for, is set out in the-four-messages-an-appointment-needs.
What it cannot do: reminders do not create commitment. Sending three to someone who never intended to come produces three ignored messages.
6. Make cancelling easier than not cancelling
This is the counterintuitive one, and it is the change most businesses resist hardest.
Every barrier in front of rescheduling — call us during opening hours, no changes online, speak to reception — does not prevent the change of plans. It prevents you hearing about it. The customer whose Thursday fell apart either moves the appointment in ten seconds from their phone, or does nothing at all and becomes a no-show. There is no third option where the barrier makes them turn up.
Self-service rescheduling up to your notice window is not softness. It is the mechanism by which a cancellation happens early enough to be worth money to you.
What it cannot do: it will not stop the person who cancels an hour before. That is what the notice window and the waiting list are for.
7. Put the notice window in the booking, not in the argument
A policy that lives in your head is not a policy; it is a mood, and it is applied inconsistently by definition, which is how a fair rule comes to feel unfair to the person it lands on.
The version that works is agreed at booking, priced in money you already hold, and applied by a system rather than argued by a person. Three decisions: how much notice you need, what crossing that line costs, and what the customer sees at the moment they book.
Trades diverge here more than anywhere else on this list. A salon's version is three decisions and four sentences: salon-no-show-policy. A personal trainer's version has to survive 6am sessions and prepaid blocks, which is a genuinely different problem: personal-trainer-cancellation-policy. Consultants have their own shape again, where the fee is often credited rather than kept: charge-for-discovery-calls.
What it cannot do: a written policy does not enforce itself, which is why the enforcement should be automatic and the grace should be human — see the closing rule below.
8. Refill the gap with a waiting list that holds nothing
Some no-shows and late cancellations happen anyway. The recovery layer decides what they cost.
A waiting list turns a cancellation into a booking. When a slot frees up, the people who wanted that day are told, and the first to respond takes it. The design point that matters: nothing is held while everyone is asked. A held slot is just the original no-show moved sideways — you have re-created the problem you were solving, with a different person's name on it. VoltsBook's waiting list works exactly this way: joining costs nothing, an opening is an invitation, and claiming it is booking it.
Small books benefit most from this, which is the opposite of what people assume. Each recovered slot is a larger share of a small week.
What it cannot do: a waiting list only helps where demand exceeds supply on some days. If every day has openings, this change is worth nothing and you should skip it rather than configure it.
9. Change the terms on the third no-show, not the first
One no-show is life. Three is a pattern, and the pattern deserves a different contract rather than a ban.
The proportionate response is to move that specific customer to payment in full at booking, said once and without drama. It filters precisely the people who cost you mornings, it converts them into either a reliable customer or somebody else's problem, and it reads as fair because it is — you are not punishing them, you are pricing them.
What it cannot do: it does nothing for first-time customers, who are the ones most likely to vanish. That is why change number one is number one.
Then measure your own number
Count your no-shows per hundred bookings for a month. Change one thing from the list. Count again.
This is also why there are no statistics in this guide. Every figure you will read on this subject comes from somebody else's book — a different trade, a different price point, a different town, a different set of customers — and the only number that tells you whether a change worked is yours, measured before and after. We would rather give you the mechanism than a percentage you cannot apply.
That division is what lets a policy be strict without the relationship going cold. It is also the honest answer to the objection that all of this is unfriendly. Nothing here is unfriendly. Charging a deposit that comes off the bill, sending a reminder someone can act on, and letting people rearrange from their phone are all things a good customer likes. The only person inconvenienced is the one who was never going to turn up.
If you are choosing software to run any of this, the deposit question belongs on the checklist well before the feature tour — we put it at number three in how-to-choose-booking-software. The state of the field on that one feature is worse than most buyers expect: of the eight scheduling-link tools we checked on 18 August 2026, not one had a confirmed, generally-available deposit mechanic. That survey, vendor by vendor and plan by plan, is in booking-software-with-deposits.
What single change reduces no-shows most?
Money at booking. Nothing else changes the psychology of the commitment itself — everything else on the list manages memory and logistics around a decision the customer has already made or failed to make.
Should I charge a no-show fee after the appointment?
Charging after the fact means chasing money while annoyed, which is the worst version of anybody doing collections, and it invites a payment dispute that usually costs more than the fee. Hold the money from the start instead: a kept deposit is a policy, an invoice for absence is an argument.
How much should a deposit be?
Enough that forgetting is inconvenient, low enough that nobody hesitates at the last screen — for a £40 service that is usually around £10. Size it by what the empty slot costs you rather than as a share of the price, and raise it steeply only where a gap costs you a whole day.
Do deposits reduce bookings?
They filter them. The bookings a small, clearly-credited deposit costs you are heavily weighted toward the ones that were not going to arrive. Keep the amount below the hesitation point, and say in writing that it comes off the bill.
Is a waiting list worth it for a small business?
It costs nothing to keep and it converts your worst moments into your most grateful bookings — but only if some of your days are genuinely full. If every day has openings, skip it.
Does VoltsBook charge no-show fees to a saved card?
No. There is no card-on-file mechanism in the product at all. Deposits taken at booking, credited against the bill, and kept or returned according to your notice window are how the same problem is solved here.