When a tech is running late: messages that work

Late is forgivable. Silence is not.

Every service company runs late sometimes. A diagnostic turns into a three-hour repair, a part is missing, traffic stops on the interstate. Customers understand that. What they do not accept is waiting at a window, having rearranged a workday, with no word at all. The complaint is rarely "your tech was 40 minutes late." It is "nobody told me."

A good late-arrival process turns a delay into a moment that builds trust. It has three parts: rules that trigger a message early, templates that say the right thing quickly, and a clear policy on what the customer is offered when the delay is long.

Why text beats a phone call

Your phone call may never be answered. Pew Research found that eight in ten Americans say they do not generally answer their cellphone when an unknown number calls, and only 19% say they generally answer^[1]. If your dispatch line is not saved in the customer's contacts, a delay call often goes to voicemail.

Text reaches almost everyone: 98% of U.S. adults own a cellphone and 91% own a smartphone^[2]. Make the first notice a text from the number the customer already received confirmations from, and follow up with a call only if they do not reply to a long delay, or if they asked for calls in their contact preferences.

Set expectations at booking

The easiest delay to handle is one the customer was prepared for. At booking, the CSR should explain the arrival window in one sentence and say how the customer will hear about changes: "Your window is 10 to 12. You will get a text when your technician is on the way, and we will text you right away if anything changes." That one line sets the rule for the day and tells the customer which number to save.

Capture contact preferences at the same time. Ask whether texts are fine, whether someone else will be home, and whether the customer has a hard stop. A note such as "must leave by 12:30 for school pickup" lets the dispatcher protect that customer first when the morning starts to slip, instead of finding out at 12:20.

Trigger rules

Do not leave the decision to whoever happens to notice. Tie messages to minutes behind schedule, measured against the promised arrival window.

The key rule: the delay message goes out before the window closes. A message at 12:05 for a 10-to-12 window feels like an excuse. The same message at 11:15 feels like good service.

What a good delay message contains

1. Who it is from: company name, and the tech's first name if known.
2. The new estimate, as a time or a short window, not "a little late."
3. A brief reason, without blaming another customer.
4. A clear choice with an easy reply.
5. A way to reach a person.

Keep it under 300 characters so it is not split into multiple texts. Avoid jokes and avoid over-apologizing; one sincere "sorry" is enough.

Templates you can copy

• Heads-up (15 to 30 minutes): "Hi Maria, this is [Company]. Jake is finishing a repair that ran long and now expects to reach you around 11:40 instead of 11:15. Sorry for the change. Reply here or call us if that does not work."
• Will miss the window: "Hi Maria, Jake is running behind and now expects to arrive between 12:30 and 1:00, after your 10 to 12 window. Sorry about this. Reply 1 to keep the visit today or 2 and we will book you first thing tomorrow."
• Long delay with gesture: "Hi Maria, we are very sorry. Jake is delayed by an emergency and the earliest arrival today is 2:30. Reply 1 for 2:30 or 2 for tomorrow 8 to 9. Either way, today's diagnostic fee is waived."
• Cannot make it: "Hi Maria, we called a moment ago. We cannot reach you today after an emergency call. We are holding tomorrow 8 to 10 for you. Reply YES to confirm or call us to choose another time."
• After a late visit: "Thanks for your patience today, Maria. If anything about the visit did not meet your expectations, reply here and a manager will call you."

Replace the names and times with merge fields in your field service or texting software. Have one person own the templates, and review them each quarter for tone. Make sure your texting complies with consent rules; see the TCPA texting guide for the basics.

When to offer compensation

Not every delay needs a gesture. Give the dispatcher a short, pre-approved policy so they do not have to ask a manager, and so customers get the same treatment.

Write down who can approve what. A dispatcher might waive a trip fee; a manager approves anything larger. Log every gesture against the job so you can see which techs, job types or days cause the most delays.

Remember who is waiting

Most of your customers rearranged something to be home. In 2025, 81% of employed Americans worked on an average weekday^[3], and 35% did some or all of their work at home on days they worked^[4]. A homeowner working from the kitchen table may tolerate a delay; one who took unpaid time off will not. If your intake records this, use it: customers who took time off get the earliest notice and the first offer of a reschedule.

Who sends the message

• Techs should never text customers while driving. The tech taps a status or calls dispatch hands-free; dispatch or automation sends the message.
• Automated heads-ups work well for small delays if your software projects arrival times from GPS and job status.
• Long delays and cancellations should come from a person, with a call when possible.
• One voice per customer per day: avoid the tech, dispatcher and office all texting the same customer.

When the customer replies angry

Some replies will be sharp, especially after a long wait. Move angry replies from text to a phone call quickly, from a person with authority to fix the problem. Do not argue about the reason for the delay, and do not send a second templated apology.

• Acknowledge the specific cost: "You took the morning off for this, and we let you down."
• Offer the choice again, with the earliest real slot and the gesture your policy allows.
• Confirm the outcome in writing by text, with the new time and any waived fee.
• Flag the account so the next visit gets a confirmation call the day before.

Example: a delay handled well

Example (fictional): at 10:50 a dispatcher sees a tech's repair will run 45 minutes over. The next customer has a 11-to-1 window and noted she is taking a long lunch from work. The dispatcher texts at 10:55 with a 1:15 estimate and a choice. She replies 2. The dispatcher books her at 8 a.m. the next day and adds a note to waive the trip fee. The next morning she gets an on-my-way text with the tech's photo, and the visit ends with a five-star review that mentions the communication.

Measure and prevent

Track three numbers weekly: on-time arrival rate, the share of late arrivals that got a message before the window ended, and complaints that mention timing. If late arrivals are rising, the fix is upstream: better job duration estimates, buffers after diagnostics and smarter skill-based dispatching. Good delay messages protect the relationship, but fewer delays protect it better.