Why do booked jobs cancel, and how do you stop the leak?
The dominant cause is time. The longer the gap between booking and appointment, the more chances the customer has to solve the problem another way or find someone sooner. Wide arrival windows, no confirmation contact and unclear expectations add to it. Track cancellations against days-to-appointment and the relationship usually appears immediately.
Booked is not the same as ran
Most companies measure booking rate and stop there. But a booked job that cancels consumed a call, a slot on the board, and produced nothing. The number that ties to revenue is net booked: jobs that were booked and actually ran.
Track both, and track the gap between them. That gap is schedule leakage, and it belongs to operations rather than to whoever answered the phone.
The time relationship is the main finding
Plot cancellation rate against the number of days between booking and appointment. In most service businesses the curve rises steeply. A customer scheduled for tomorrow rarely cancels. A customer scheduled for next week has had days to call three competitors, watch a video, or have the problem intermittently resolve itself.
This reframes the fix. Cancellation is often not a customer-communication problem at all; it is a capacity problem showing up several days downstream. That link is another reason days-to-first-available deserves daily attention rather than monthly review.
The controllable causes
- Wide arrival windows. A window that requires the customer to give up a day invites them to keep shopping for someone who can be specific.
- No confirmation. A reminder the day before with the technician's name and a real window prevents the quiet no-show as well as the cancellation.
- Unclear expectations. Customers who do not know what the visit includes, or what happens if the repair is larger than expected, cancel when they get nervous.
- Rescheduling by you. A job pushed once by dispatch is far more likely to be cancelled by the customer. Track your own reschedules as a separate cause.
Capture the reason at the moment it happens
Cancellation reasons are usually recorded as a free-text note or not at all, which makes the pattern impossible to see. A short required reason list on cancellation, plus a link back to the original booking, is enough to make this analyzable.
Where cancellations arrive by phone, the reason is already in the conversation. Call analysis can classify it without adding a step for the person taking the call, which is the difference between a field that gets filled in honestly and one that gets set to other. Reported against days-to-appointment and technician reschedules in a revenue view, it becomes clear how much of the leak you actually control.
Topics: cancellations · scheduling · booking rate · retention
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.