In a business with technicians and a booked schedule, absence is not an exception — it is a weekly event. Treating it as a surprise every time is what turns one sick technician into six unhappy customers and an afternoon lost to phone calls.
In this article
Someone will call out today
In a business with technicians and a booked schedule, absence is not an exception — it is a weekly event. Treating it as a surprise every time is what turns one sick technician into six unhappy customers and an afternoon lost to phone calls.
The first fifteen minutes
Before anything else, look at the day and sort the jobs into three groups: the ones that must happen today, the ones that can move without consequence, and the one or two that are already at risk for other reasons. You cannot make good decisions about coverage until you know which is which.
Emergency and access-dependent jobs go first. A customer who took a day off work is not a job you reschedule casually.
Keep reading — free
The rest of this article is worth the 20 seconds
Tell us where to send it and the full piece unlocks right here, along with everything else on this blog.
Rather just talk? Message us on WhatsApp.
Call before they call you
The difference between an annoyed customer and an angry one is almost entirely who called first. A call at seven-thirty offering a specific alternative time lands completely differently than a call at eleven explaining why nobody arrived.
Offer two concrete options rather than asking what works. People rebook faster when given a choice than when handed a blank calendar.
Spreading the work
Resist the urge to hand the whole route to one person. An overloaded technician does three jobs badly and finishes at eight. Split the day, cut the jobs that can wait, and accept that the schedule is smaller today.
If you routinely need overtime to cover one absence, the schedule was too tight before anyone got sick.
Build the slack on purpose
The businesses that handle this well are not luckier. They hold a small amount of unbooked capacity every week, usually late in the day, specifically so a bad morning has somewhere to go. It looks like wasted capacity until the week you need it.
A policy beats a negotiation
Write down how call-outs are reported, by when, and to whom. A technician texting a coworker at seven is not a notification. A clear rule removes both the ambiguity and the argument, and it makes the pattern visible if someone is abusing it.
Read the pattern
One absence is life. A repeating one is information — about scheduling, about workload, or about a person who has already left mentally. Keep the record, look at it quarterly, and deal with the cause rather than the symptom.
Where to start
Triage the day before touching the phone, call customers before they call you with two specific options, split rather than dump the route, hold a little slack every week, and put the notification rule in writing.
The businesses that handle bad mornings well are not luckier. They planned for them.
We help service businesses build the scheduling slack, the communication rules and the dispatch process that keep one absence from costing you six customers.
Frequently asked questions
What should I do first when a technician calls out?
Triage the day before touching the phone. Sort the jobs into three groups: the ones that must happen today, the ones that can move without consequence, and the one or two already at risk for other reasons. Emergency and access-dependent work goes first — a customer who took a day off work is not a job you reschedule casually. Then call the affected customers before they call you, offering two concrete alternative times rather than asking what works, because people rebook faster when given a choice than when handed a blank calendar.
How do I stop one absence from wrecking the week?
Hold a small amount of unbooked capacity every week, usually late in the day, specifically so a bad morning has somewhere to go. It looks like wasted capacity until the week you need it. Avoid handing the entire route to one technician — an overloaded person does three jobs badly and finishes at eight. If covering one absence routinely requires overtime, the schedule was too tight before anyone got sick. Finally, write down how call-outs are reported, by when and to whom, which removes the argument and makes the pattern visible if someone is abusing it.