Customer Comms Script - Running Late Message
Why this matters
The single largest driver of negative service reviews is not the missed window. It is the silent missed window. Customers who get a proactive heads-up that the tech is running 45 minutes late, with a reason and a revised ETA, leave neutral or positive reviews at rates several times higher than customers who hear nothing until the tech walks up the driveway. The script in this reference is the wording dispatchers and techs should use, the timing they should hit, and the channel choices that work. Adopt it verbatim or adapt it to your voice; either way, send the message.
When to send
Three timing rules cover almost every case.
- Inside the original window: do nothing extra. The window is the promise; you are still keeping it.
- Window slipping by under 30 minutes: send a short heads-up message at the moment you know, not at the end of the window. The customer is calibrating the rest of their day off your ETA.
- Window slipping by 30 minutes or more: send the message, offer to reschedule, give a revised window (not a single time), and confirm the customer wants you to continue.
The trigger is awareness, not severity. The moment the dispatcher or tech knows the original window will not be met, the message goes out. Waiting "to see if we can still make it" is how customers lose trust in the brand.
Channel choice
Pick the channel that the customer has used to communicate with the company so far. Three rules.
- SMS is the default for residential service work. Read rates exceed 95 percent within five minutes. Use SMS unless the customer has explicitly opted out or unless the message contains content that should not be in writing (rare).
- Voice call is the default for commercial customers with a dispatcher or facilities manager on the other end. They expect to talk through schedule changes.
- Email is the default only for previously scheduled multi-day jobs or when the customer initially contacted by email. Email read rates are too low for same-day notice.
If the original communication thread was SMS, the late message goes SMS. If the customer texted you a question two hours ago, do not call them about being late; text them.
Script - under 30 minutes late
Short, accurate, no apology spiral. The customer wants information, not contrition.
Hi [Customer first name], this is [Tech name] from [Company]. Quick update: the job before yours ran long. I am still on track for your window but on the back half of it - now estimating arrival between [revised time] and [original end of window]. I will text again when I am 15 minutes out. Reply STOP to opt out of texts.
Variations by reason - swap one line.
- Traffic: "Hit a closed-road detour heading your way."
- Parts run: "Had to grab an additional part for your job."
- Previous job ran long: "The job before yours ran long."
- Weather: "Slow going in the rain - keeping it safe."
Do not invent reasons. If you do not know why dispatch is behind, omit the reason line. "Running on the back half of your window" is fine on its own.
Script - 30 minutes or more late
Three things the message must do: tell them how late, give them a choice, and give them a revised window.
Hi [Customer first name], this is [Tech name] from [Company]. I am running about [X minutes] behind the window we gave you, and I want to give you the choice. Option 1: I head your way now and arrive between [new start] and [new end]. Option 2: we reschedule to [first available alternative]. Reply 1 or 2 and I will lock it in. Sorry for the delay.
Why this works. It names the delay (no surprise on arrival). It gives the customer agency (they decide, not you). It offers a concrete alternative (not "let me know when works"). It closes with a brief apology (not a paragraph).
Script - over 90 minutes late or end-of-day risk
When the slip is large enough that the customer's day is affected, the call replaces the text. Pick up the phone.
Hi [Customer first name], this is [Tech name] from [Company]. I am calling because I am running significantly behind today and I want to be straight with you. Best case, I would be at your place around [time]. I do not want to rush the job before yours, and I do not want to rush yours. Would you rather I come tonight at [late time], or move you to first-call tomorrow at [time]?
If you hit a voicemail, leave the message and follow with a text containing the same options. Do not just text - the call demonstrates that the company knows the slip is large.
What not to say
Six phrases to delete from every late-notice script.
- "We are doing the best we can." This is about you, not the customer.
- "There is nothing we can do." This is also about you.
- "It should not be much longer." Vague is worse than a specific late window.
- "The tech got held up." Use a real reason or no reason; this phrase signals avoidance.
- "We will be there as soon as possible." ASAP is not an ETA.
- "Sorry for any inconvenience." Generic apologies read as canned.
Replace each with a concrete time, a concrete reason, or a concrete choice.
Follow-up after arrival
Late arrivals deserve a brief in-person acknowledgment. One sentence is enough.
Thanks for working with us on the timing today. I appreciate it.
Do not over-apologize on the doorstep. Get to work, do the job well, and let the work close the gap. A 25-minute late job done correctly is a satisfied customer; the same job with five minutes of apology at the door before starting reads as defensive.
Compliance notes
Two regulatory items affect how the message is sent.
- TCPA (Telephone Consumer Protection Act, 47 USC 227): automated and bulk SMS to a mobile number requires consent. A service customer who provided a phone number for service communications and confirmed at intake is generally covered for transactional service messages. Document the consent at intake. Include a STOP keyword in any automated message.
- CAN-SPAM Act (15 USC 7701): applies to commercial email. Service email under an established business relationship is generally permitted but include sender identification and an unsubscribe path for marketing content.
Late-arrival messages are transactional, not marketing, and are the safest category of customer messaging. Keep them brief and they stay transactional.
References
- 47 USC 227, Telephone Consumer Protection Act
- 47 CFR 64.1200, FCC implementing regulations for TCPA
- 15 USC 7701 et seq., CAN-SPAM Act
- 16 CFR Part 316, FTC implementing regulations for CAN-SPAM
- Federal Trade Commission guidance, Mobile Marketing Best Practices
- CTIA Short Code Monitoring Handbook, current edition, transactional message definitions