Tech Running Late: Call Ahead vs Reschedule vs Send Another Decision Tree
Why this matters
A tech is going to miss the appointment window. The job before ran long, traffic stacked up, or a part run took longer than planned. The lateness itself is recoverable; what destroys the customer relationship is the silence around it. A customer who gets a call thirty minutes before the window slips is mildly inconvenienced. A customer who sits home all afternoon and watches the window pass with no contact feels disrespected and tells everyone. Dispatchers and techs need a fast rule for what to do when the clock slips, because the decision is time-sensitive by definition.
The governing principle: communicate before the window is missed, not after, and offer the customer a real choice rather than presenting the delay as a done deal.
The situation
Running late breaks down by how late and how flexible the customer is:
- Minor slip (still arriving same day, modest delay) - a proactive call usually holds the appointment.
- Major slip (hours late, or into the evening) - the customer may prefer to reschedule.
- Cannot make it at all today - reschedule or, if the work is urgent, send another tech.
- Urgent/obligated job (emergency, SLA, no-heat) where the current tech is stuck - sending a different tech may be the only way to keep the promise.
The dispatcher reads how late, how urgent, and how flexible, then picks the path.
What is at stake
Trust: The single biggest driver of customer satisfaction on a late job is whether they were told early. Early notice converts anger into understanding; late notice or no notice converts a minor delay into a lost customer and a bad review.
Productivity: A customer who reschedules cleanly because you called early is a far smaller loss than a customer who waited, got nothing, and now distrusts the whole company. Protecting the relationship protects future revenue.
Obligations: For SLA-covered, membership, or emergency work, "we are running late" is not enough - you may owe a substitute tech to keep the commitment.
The decision tree
Will the tech still arrive today within a tolerable delay? -> CALL AHEAD immediately, before the original window closes. Give a specific revised arrival time and let the customer confirm it still works. Do not wait to see if you can make up the time; call now and update again if it changes.
Is the job urgent or under an obligation (emergency, SLA, no-heat in cold, membership guarantee) and the assigned tech is stuck? -> SEND ANOTHER tech if one is available and can do the work. Keeping the promise matters more than keeping the same name on the ticket.
Will the tech be hours late, pushing into evening, and the work is not urgent? -> CALL AND OFFER THE CHOICE: "We can still come this evening around [time], or I can get you the first slot tomorrow - which works better?" Let the customer decide. Many prefer a clean reschedule to a late, rushed visit.
Can the tech not make it at all today and the work can wait? -> RESCHEDULE proactively. Call before the window, apologize plainly, offer the next concrete slot (ideally a priority one), and consider a goodwill gesture if the customer rearranged their day.
Is the customer unreachable as the window approaches? -> Leave a clear voicemail and a text with the revised time and a callback number, then keep trying. Document every attempt. Do not let a missed window happen in total silence - the record of your attempts protects the company.
What to document
- The time you first knew the appointment was at risk and the time you contacted the customer (the gap between these two is what matters).
- What you offered (revised time, reschedule, substitute tech) and what the customer chose.
- Any goodwill gesture authorized.
- For unreachable customers: every call/text attempt with timestamps.
The most valuable note is proof you reached out before the window closed, not after.
The communication that saves the job
How you make the call matters as much as making it. Lead with the apology and the specific new time, not excuses. "I want to give you a heads up - we are running behind and I will be there at [time] instead of [time]. Does that still work for you?" respects the customer's time and hands them control. Vague messages ("we are running a little late, see you soon") erode trust because the customer cannot plan around them. Specific, early, and honest is the formula.
For repeat or high-value customers and anyone who blocked out their day, a small goodwill gesture (a discount, a priority next slot, a waived trip fee) turns a service failure into a loyalty moment. The cost is trivial against the lifetime value of a customer who tells people you handled a problem well.
Who makes the call
Decide in advance whether the tech or the dispatcher owns the late-notice call, because in the moment both tend to assume the other is handling it and neither does. The cleanest rule is that the dispatcher owns customer communication and the tech's only job is to flag the delay to dispatch the instant they know about it. A tech wrist-deep in a job cannot reliably stop to manage another customer's expectations, and a customer who gets the heads-up from the office sooner is better served than one who waits for the tech to free up. Whichever way you assign it, assign it explicitly so the notification never falls through the gap between two people each thinking it was the other's job.
Reducing chronic lateness
If a tech is late often, the cause is usually upstream of the tech: slots booked too tight, no travel time built between jobs, or jobs routinely scoped smaller than they really are. Chasing the symptom with apology calls treats the rash and ignores the allergy. Track which job types overrun their slots and pad those slots; build realistic drive time into the route rather than assuming teleportation between stops. A schedule built on honest durations produces far fewer late calls than one built on best-case math, and every avoided late call is a customer who never had a reason to doubt you.
References
- State contractor-licensing standards of practice on timely communication and honoring scheduled appointments (varies by state).
- Service-level-agreement and membership-guarantee terms in your own contracts - the source of substitution obligations.
- Consumer-protection guidance on appointment windows and notice (FTC Act, 15 U.S.C. 45) - avoiding deceptive scheduling practices.
- ConsensusDocs service-agreement conventions on response and notice expectations.