Communicating a Delay Before the Customer Calls You
Why this matters
Almost every customer will forgive a late tech. Very few forgive finding out by watching the clock and calling you first. The delay itself is rarely what damages the relationship, it is the silence around it, the sense that the shop knew and did not bother to say anything. Getting ahead of a delay with a proactive message is one of the cheapest trust-building moves available to a dispatcher, and it costs almost nothing except the discipline to do it every single time, not just when it feels important.
The rule: whoever notices first, speaks first
The moment anyone, dispatch or the tech, realizes an appointment is going to run late, that is the moment the customer should be contacted, not after the appointment time has already passed. A message sent five minutes before the promised window closes lands completely differently than the same message sent twenty minutes after. Waiting to see if things "might still work out" before saying anything is the single most common way this goes wrong.
What the message needs to contain
A good delay message is short and covers exactly three things:
- A brief, honest reason, without over-explaining or making excuses. "The job before yours ran longer than expected" is enough. You do not need to justify the delay at length, you need to acknowledge it happened.
- A real, specific new window, not a vague "soon" or "shortly." If you genuinely do not know yet, say that plainly and commit to a time you will follow up with an actual window, then keep that commitment.
- What the customer should do, whether that is simply waiting, or a way to reach you if the new window does not work for them.
Avoid over-apologizing. One sincere acknowledgment lands better than three repeated sorries, which starts to read as anxious rather than professional.
Match the channel to the situation
- A text or app notification works well for a routine delay of a manageable amount of time, it is fast, low-pressure, and gives the customer a written record of what was promised.
- A phone call is the better choice for a longer delay, a customer who has already had one bad experience, or anything where tone matters, such as needing to reschedule to a different day entirely.
- Never rely on the tech alone remembering to call while they are still mid-job on the appointment running long. Dispatch should send the first heads-up, since the tech is busy and often has worse visibility into how the rest of the day looks.
Timing: the earlier, the better, even with imperfect information
A dispatcher's instinct is often to wait until the new time is fully certain before saying anything. Resist that. An early, slightly rough estimate ("running about an hour behind, will confirm a tighter window shortly") sent well before the original appointment time beats a perfectly precise message sent after the customer was already left wondering. Customers judge you on when they heard from you, not on how exact the first estimate was.
When the delay keeps changing
If a job's overrun keeps sliding (an hour becomes two, becomes three), send a follow-up each time the estimate meaningfully changes, do not let the customer work off a stale promise. A second honest update ("still tied up, now looking at closer to 4 instead of 3") is far better received than silence followed by a third missed window.
What to do if the customer is already upset by the time you reach them
Sometimes the customer beats you to it and calls first, annoyed. Do not get defensive. Acknowledge that they should have heard from you sooner if that is true, give the real update, and move forward. A customer who is annoyed about a delay but treated respectfully in the moment usually stays a customer. One who is made to feel like an afterthought on top of being delayed often does not.
The mental model to keep
Every delay is really two separate events: the schedule slipping, and the customer finding out about it. You cannot always control the first one. You can always control the second, and it is the one that actually determines how the customer remembers the day.
References
- Trade-standard practice for field-service customer communication
- See related: A Job Runs Long and Blows Up the Rest of the Day (decision tree)
- See related: Squeeze In a Same-Day Emergency (decision tree)
- See related: A Customer No-Shows for a Scheduled Appointment (decision tree)