Academy › Build › Bookings and orders
The second no-show changes the rule
By the end, you'll know the point at which a client has to start paying in full upfront, and how to tell them without it feeling like a punishment.
By Yodai · Published on September 6, 2026 · Updated on October 12, 2026
A slot that someone cancels last minute, you can still try to fill. The real problem is the one left by someone who doesn't even give a heads-up. A client is a no-show. It's the first time, so you apply the policy you already have: you charge the deposit, or you let it slide with a warning because it had never happened before. Two weeks later, it happens again. Same client, same lost slot.
The question isn't whether you forgive that second no-show. It's a different one: from here on, does she keep booking under the same terms as anyone else, or does she move into another category? The one where she pays in full upfront before you hold her a slot.
Counting no-shows, not cancellations
Canceling ahead of time, rescheduling, and not showing up are three different things, and each one carries its own consequence. Here, only the last one counts: the slot that stays empty because no one gave enough notice to fill it. That's a no-show.
Count by client, not by a one-off appointment. If Marta no-shows in January and again in June, there are five months in between: probably a coincidence. If she no-shows twice in three weeks, it's not a coincidence anymore. It's how she treats your calendar.
The counter doesn't reset just because a good month has gone by. It resets when you decide the client has proven otherwise, not before.
Why the second no-show, not the first or the third
Punishing the first no-show means charging someone for a bad day: a flat tire, a sick kid, they simply forgot. If you demand payment upfront from the very first time, you treat someone who's been coming for two years the same as a stranger booking for the first time. You lose more trust than you protect.
Waiting for the third strike means letting two full slots cost you before you act. If your schedule has six appointments a day at $40 each, two empty slots in a month add up to $80 nobody pays you, money you also couldn't collect from another client because the slot was booked on paper.
The second no-show is the point where it stops being a fluke and starts being a pattern. That's when you change the rule. Not before, not after.
- Easy to explain: one policy for everyone
- No need to track who no-showed and when
- A regular going through a rough patch feels treated with distrust for no reason
- It doesn't stop repeat offenders: for them, the policy never changes
- The first slip is treated as what it usually is: a one-time thing
- The second triggers full payment upfront before accepting another booking
- Protects the slot of clients who do show up, without penalizing anyone who's never no-showed
- Requires keeping a simple log: who's no-showed and how many times
Which one to pick: Choose the policy that changes on the second no-show, unless your schedule is so slow that an empty slot doesn't cost you anything. If you live off of being booked, the second no-show is the signal, not the third.
How to apply it without it feeling like a punishment
- 1Log the no-show in the client's file
A column, a note, whatever you already use for history. You just need the date and whether they gave notice or not. - 2On the first no-show, apply your normal policy
The deposit you already charge, or nothing if that wasn't your habit. Don't change anything yet. - 3On the second, communicate the change before the next booking
Don't apply it silently. Tell her what's changed and why, before she tries to book again. - 4From then on, don't confirm a slot without payment done
The payment link comes before the slot on the calendar, not after.
When she says she did give notice
It's going to happen: someone will tell you they did text, that the message didn't go through, that they called and you didn't pick up. Don't argue the specific incident, check the log. If you have the notice saved, it doesn't count as a no-show, and you tell her so. If you don't have it, it counts, and you say so just as calmly: here I only log what comes through the channel we always use.
That's why it helps to have a single channel for notices, the same one you use to confirm the appointment. If a client gives notice through a different channel than usual, the next time you talk to them, ask them to always use that one, and it's settled going forward.
One question remains open: if that client doesn't no-show again for months, does she keep paying upfront forever, or is there a point where you give her back your trust? That gets decided in the next lesson.
- You know how to tell a one-off no-show from a pattern: the second one is the signal, not the first or the third
- You keep a simple log of no-shows per client, with the date and whether they gave notice
- You know what to say, and when to say it, when you change the booking terms
- From the second no-show on, payment comes before the slot on the calendar
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. A client no-shows in March without notice, and you apply your normal policy. In October, seven months later, they no-show again. Do you activate payment upfront now?
Not automatically. Seven months without incident points to coincidence, not a pattern. Treat that no-show as if it were the first and keep watching; the second-no-show rule protects against repetition close in time, not against any second no-show separated by months in the history.
2. A client gives timely notice that they're rescheduling, and three weeks later they don't show up without notice. Is that no-show their second one?
It's the first. Rescheduling with timely notice isn't a no-show, it's exactly the behavior you want repeated: they gave notice in time. Only the time they didn't give notice counts as a no-show. Apply your normal policy for that single no-show and start counting from there.
3. You send the upfront-payment notice after a client's second no-show, but two days later someone else on your team confirms a slot for her over the phone without charging her, because they didn't see the notice.
The failure isn't the client's, it's the record-keeping: the new condition never reached whoever answers the phone. The fix is adding the note to the client's file, where anyone confirming a booking will see it, not just sending a WhatsApp message; the rule has to be written right where bookings get confirmed, so no one confirms without payment in hand, instead of relying on someone remembering a conversation.
With the rule written in the file, it no longer depends on anyone's memory. But someone will call with a real reason, asking you to make an exception just this once: that's where you decide whether to let it go or charge anyway.
In Yodai your clients request a time on your site and you confirm it from your dashboard. See how online booking for your business works.
NextWhen you waive the charge (and when you don't, no matter how much they push)