The Running-Late Customer Call Script

Why this matters

Running late is unavoidable in service work; the job before always has the right to run long. What separates a respected company from a resented one is not whether you run late but whether you call. A customer told you are behind feels managed and usually waits without complaint. A customer left sitting past their window with no word feels abandoned and remembers it. This call is one of the cheapest, highest-return things the office does all day, and there is a right way to make it.

Step 1: Call before the window closes, not after

Timing is the whole game. The moment you know the tech will miss the window, the customer should hear from you, ideally while there is still time left in their window, not after they have already started wondering and stewing.

Calling early says "we respect your time." Calling after they have called you, or worse, after the tech simply shows up late, says the opposite. Set a habit: when a job runs long enough to push the next stop, the office calls the next customer right then, not at the end of the run.

Step 2: Lead with the apology and the new time

Open plainly and own it. Do not bury the point or pad it with excuses.

A clean opener: "Hi, this is the office calling about your appointment today. I want to let you know the tech is running behind. We're now looking at closer to three o'clock instead of one. I'm sorry for the change in timing."

That is the core: who you are, the honest new estimate, and an apology. Give a specific new time, not a vague "later this afternoon." A real number lets the customer plan; a vague one leaves them stuck waiting all over again.

Step 3: Offer a genuine choice

After the new time, hand the customer control: "Does that still work for you, or would you rather I find you a different day?"

This matters because the customer's situation may have changed, or the new time may not fit. Offering the reschedule openly, instead of forcing the wait, signals that you value their time more than your route. Most customers, given the respect of a choice, choose to wait. The ones who cannot are better rescheduled now than missed entirely.

Step 4: Confirm and set the next checkpoint

Once they agree to a path, lock it down and tell them what happens next: "Great, so we're set for around three. The tech will text you when he's about thirty minutes out so you're not just sitting and waiting."

That "thirty minutes out" promise is gold. It frees the customer to live their life until the tech is genuinely close, instead of staring at the driveway. Then make sure the tech actually sends it. A promised heads-up that never comes undoes all the goodwill the call just built.

Step 5: Handle the upset customer without escalating

Some customers will be annoyed, and that is fair; they may have taken time off. Do not argue, do not get defensive, and do not over-explain the chain of delays that led here. Acknowledge it and move forward:

• Validate: "I completely understand, and I'm sorry, your time matters."
• Do not over-apologize into groveling. One sincere apology lands; ten sound insincere.
• Pivot to the solution: the firm new time, the heads-up promise, the reschedule option.
• Offer a make-good if the delay is large or the customer is loyal. A small gesture often turns the moment around.

The customer is reacting to the inconvenience, not attacking you personally. Stay calm, stay solution-focused, and most of the heat passes.

What not to do

• Do not go silent and hope they do not notice. They always notice.
• Do not give a fake-tight new time to soften the blow; missing it twice doubles the damage.
• Do not blame the prior customer or the tech. The customer does not care whose fault it is; they care that you communicated.
• Do not promise the thirty-minute heads-up and then skip it. Broken small promises erase the trust the call built.

References

• Trade-standard customer-communication and service-recovery practice for field-service operations.
• See related: Setting the Arrival Window Expectation.
• See related: The Double-Booked Schedule Decision Tree.