Most of the leaks we write about happen before a job is booked: the missed call, the voicemail, the estimate nobody chased. Once a job is on the board, it feels safe. The customer said yes. There is a name, an address and a time window. The hard part is done.
It is not quite done. Between the booking and the tech ringing the doorbell there are days, sometimes weeks, and plenty can happen. The customer forgets. A neighbor’s brother-in-law offers to take a look. Another company calls back first with an earlier slot. The job is still on the board, and it will stay there until the tech arrives at a locked door.
Four ways a booked job leaks
No-shows. The tech arrives and nobody is home, or the customer answers the door surprised. The truck has driven across town for nothing, and the slot that could have gone to someone else is gone.
Reschedules that never land. The customer calls to move the appointment. Whoever answers says “we’ll call you back with a new time”, and nobody does. The job leaves the board and does not come back. Nobody recorded it as a cancellation, because it was not one.
Quiet cancellations. The customer cancels, often by text or voicemail, and the job is deleted rather than marked canceled with a reason. There is now no trace that it existed, and no way to ask later whether they got the work done elsewhere.
Unconfirmed appointments. A job booked two weeks ago for a Thursday morning, with no contact since. It might happen. It might not. The dispatcher does not know until Thursday.
These are the same leak viewed from different angles: a job that was won and then allowed to drift.
Why they are hard to see
Dispatch boards are built to show what is coming, not what disappeared. A job that is rescheduled into limbo simply is not there next week. A deleted booking does not show up in any report. The board always looks full enough, because the gaps get filled by the next call.
Field software usually can show cancellations and no-shows, but only if people use the statuses. In a busy office the fastest way to clear a job off the board is to delete it, and that erases the evidence.
So the first step is not a fix. It is agreeing on what gets recorded.
Counting them
Pick one recent month and gather, from the scheduling system and the office’s memory:
| What to count | Why it matters |
|---|---|
| Jobs booked | The baseline |
| Jobs completed as booked | The ones that went right |
| Jobs rescheduled, and whether a new time was set | Reschedules without a new time are the hidden cancellations |
| Jobs canceled, with a reason if one exists | “Found someone else” and “fixed it myself” mean different things |
| No-shows at the door | Wasted truck time as well as an empty slot |
| Jobs deleted with no status | If you cannot count these, that is itself a finding |
Here is an illustrative example with invented numbers. Say a plumbing shop books 300 jobs in a month. It completes 255. Of the 45 that did not happen, 15 were proper cancellations with reasons, 12 were no-shows, 10 were rescheduled with no new date, and 8 simply vanished from the board. Those last 18 are the ones worth chasing. Some of those customers went elsewhere. Some are still waiting for a call back. At the shop’s average ticket, the revenue at stake is easy to work out, and none of it needed a single new lead.
The revenue leak calculator can help put your own counts into a figure, using only numbers you give it.
Confirmations that actually confirm
Many no-shows and silent cancellations can be caught by one habit: confirming the appointment close to the day.
A confirmation that works does three things:
- It arrives at a sensible time. The day before, for next-day appointments. A few days before, then again the day before, for jobs booked far out.
- It asks for a reply. “Reply YES to confirm or call us to change” gets a signal back. A message that only informs gets none.
- Someone acts on the silence. An appointment with no reply gets a phone call from the office, not another automated text. The ones who do not answer that are the ones to watch on the day.
Automated reminders from field software handle the first two well. The third is where shops fall down, because it needs a person, a list and a time of day to work through it.
Add one more habit: a call when the tech is on the way. “Your technician is about 30 minutes away.” It cuts down on locked doors, and it is the kind of courtesy customers notice.
Reschedules and cancellations
Two rules close most of the rest.
No reschedule without a new time. When a customer calls to move an appointment, the call does not end until there is a new date on the board, even a tentative one. “Let’s pencil in Tuesday and I’ll confirm Monday” is fine. “We’ll call you back” is how jobs disappear.
No deletion without a reason. A canceled job is marked canceled, with a short reason: found another company, fixed it themselves, price, timing, no longer needed. The reasons are useful on their own. If “found another company” keeps coming up for jobs booked more than a week out, the problem is your lead time, not the customer.
Once a month, someone looks at the canceled and rescheduled list and calls the ones that could still be won back. Not all of them. The ones where the reason was timing, or where there was no reason at all.
What changes
None of this generates a lead. That is the point. Every job recovered from the dispatch board is one the business already paid to win. It is the cheapest work you will ever book, because the marketing, the call and the booking have all been done.
It also makes the rest of your numbers honest. A missed call, like the ones we added up in what a missed call actually costs, is easy to see once you look. A booked job that quietly drifted is harder, because it looks like a win in every report until the day it does not happen.
If you want a second pair of eyes on it, the dispatch board is one of the first places we look in revenue leak remediation. But the month’s count is something any office manager can do in an afternoon.