How to Communicate a Delay Before the Customer Calls You

Why this matters

Getting ahead of a delay is not really a message skill, it is a system. The shops that always seem to call first are not blessed with more thoughtful techs. They built a routine that catches a slipping schedule before the customer feels it. Writing the actual message is the easy half, and it is covered elsewhere. This is the machine behind it: how the office spots the slip early, decides who to call, and fires the warning before the window closes, every day, not just when someone happens to glance at the board.

Step 1: Sweep the board on a schedule, not on complaints

The default failure is a dispatcher who only learns a job is late when the customer calls to ask where the tech is. By then you have already lost. Replace that with a fixed habit:

• Check the day's real status against the promised windows every hour or two, not just when a phone rings.
• Compare where each tech actually is against where they need to be to hit the next window. The gap is your early warning.
• Make it a named task that someone owns, not a thing everyone assumes someone else is watching.

A schedule you check on a rhythm surfaces the slip while there is still time to get ahead of it.

Step 2: Set the trigger that means "notify now"

Do not leave "is this late enough to call" to a judgment call in the moment. Set a plain threshold so the warning fires consistently.

• A useful default: if a window is likely to miss by more than about 15 minutes, notify now, even if the new time is still fuzzy. Tune the threshold to your trade, but set an actual number so the trigger fires the same way for everyone.
• Waiting until the new time is certain is the most common way this goes wrong. Early and rough beats precise and late.
• The threshold matters more than its exact setting. A consistent trigger the whole office follows beats a perfect one nobody applies the same way twice.

Step 3: Put the call on the office, not the buried tech

The tech running long is the worst-placed person to send the warning. They are elbow-deep in the job that is causing the delay and have the least visibility into how the rest of the day looks. Ownership should default to dispatch or the office.

• The office sends the first heads-up, because they can see the whole board and are not mid-repair.
• The tech's only job is to feed status back so the office knows a slip is coming. A quick "this one is running long, next window is at risk" is all dispatch needs.

Step 4: Fire the warning before the window's edge, even rough

The whole point of the system is to reach the customer while they still have flexibility. Send the message before the promised window closes, not after.

• A rough early estimate ("running about an hour behind, will confirm a tighter time shortly") sent ahead of the window beats a precise one sent after the customer was already left wondering.
• Give a real reason in a line, a real new window or a promise to confirm one by a specific time, and a way to reach you if the new time does not work.
• If the estimate keeps sliding, update each time it meaningfully changes. Do not let the customer work off a stale promise.

Step 5: Manage the cascade

One job blowing up rarely stays contained. When a morning overrun threatens the afternoon, the whole downstream chain is now at risk, and the system has to handle all of them, not just the one in front of you.

• Walk the rest of the day the moment a job blows its window. Which later customers are now exposed?
• Notify them proactively, in order, before their windows arrive. A customer warned at ten that their three o'clock is now four is mildly inconvenienced. The same customer discovering it at four is furious.
• Decide early what gives. If the day cannot hold, better to reschedule one customer cleanly and early than to keep everyone on a promise the day cannot keep.

Step 6: Log every contact so the thread survives

A proactive-delay system falls apart if the next person to touch the account does not know what the customer was already told. Note what you told them and when, in the job record, so anyone in the shop can pick up the thread and nobody contradicts the last update.

Build it in so it does not lean on memory

The reason delays get communicated late is almost never that nobody cared. It is that catching them depended on someone remembering to look. Bake the board sweep into the day as a standing task, set the trigger threshold once, and default the ownership to the office, and the early warning stops being an act of heroism and becomes just how the day runs.

References

• Trade-standard practice for field-service customer communication and dispatch
• See related: The Proactive Call That Prevents a Bad Review
• See related: How to Set an Arrival Window You Can Actually Hit