Running Behind? The Late-Tech Text That Saves the Review

Your tech is running 45 minutes behind — the previous job had a surprise, traffic is bad, it happens. Nobody tells the next customer. At the appointment time, the customer starts watching the clock. At 15 minutes past, they're annoyed. At 30 minutes past, they're calling the office, and the dispatcher — who also wasn't told — has to stall. When the tech finally arrives at 45 past, the customer is already writing the 3-star review in their head: "good work, but they don't respect your time." The work was fine. The silence was the problem.

Here's the truth that makes this post short and valuable: customers forgive lateness they were warned about, and punish lateness they discovered. The late-tech text is System 8 (proactive communication) at its most leveraged — one message that protects the entire appointment's rating. Part of the full-and-calm-calendar framework.

The 30-minute rule

The text goes out at least 30 minutes before the customer would notice — which means as soon as dispatch knows the tech is behind, not when the appointment time passes. The timeline:

• Tech realizes they're behind → immediately notifies dispatch (text, app status, call — whatever's fastest). This is the step that fails most often; techs hope they'll "make up time" and say nothing.
• Dispatch sends the late text within 5 minutes of learning about the delay. Not after the next job, not when there's a free moment — now.
• The text states the new ETA honestly. "Running about 40 minutes behind" — not "a few minutes." Customers calibrate trust on accuracy; a 40-minute warning that arrives in 35 beats a "few minutes" warning that stretches to 50.

The late-tech text (copy-paste)

Anatomy of why this works:

• "I want to be straight with you" — honesty as the opening line. It frames everything after as trustworthy.
• Specific delay, specific new ETA. Vagueness ("running a bit behind") creates more anxiety than the delay itself. Numbers calm people down.
• Brief honest reason. One clause, no excuses, no life story. "A job that ran long" is enough — it also subtly signals you don't rush jobs, which reframes the delay as thoroughness.
• The reschedule offer. "If that doesn't work, we'll reschedule, no charge." This is the power move — it returns control to the customer, and customers who feel in control don't write angry reviews.

The second update (if it gets worse)

Sometimes the delay grows. The rule: update before the new ETA expires, every time. A second text is always better than a missed second ETA:

Two delays with honest updates still beat one delay with silence. The customer is tracking your honesty now, not just your punctuality.

Making it a dispatch habit (the system)

1. Write the policy: "Any delay over 15 minutes gets a customer text within 5 minutes of dispatch learning about it." Post it where dispatch works. setup guide = standard operating procedure — written, visible, non-optional.
2. Give dispatch the template with bracketed fields (the script above) — in the messaging tool, not in someone's head.
3. Fix the tech-to-dispatch link. Techs don't report delays because they think they can make up the time, or they dread the dispatcher's reaction. Make early reporting explicitly safe: "Tell us the moment you're behind — that's the job. We'll handle the customer."
4. Track it: late arrivals with a timely text vs. without. Watch the review mentions. The correlation will convince any skeptic on your team.

What the late text protects (beyond the review)

• The customer's schedule. A warned customer can run an errand, take a call, live their life. An unwarned customer sits by the window, and every minute of that sitting becomes resentment.
• The tech's arrival. Walking into a warned customer's home vs. an ambushed one is a different job. Techs perform better when they're not starting from a deficit.
• The dispatcher's day. Every "where's my tech?" call that never happens is time back. Proactive texts are cheaper than reactive calls by an order of magnitude.

When to add a goodwill gesture (and when not to)

Should the late text include a discount? Usually no — and here's the discipline:

• Under 30 minutes late with a timely warning: the apology in the text is enough. The customer was informed, the ETA was accurate, the job went well. No gesture needed — normalizing compensation for minor delays trains customers to expect it.
• 45–60+ minutes late, or a second delay: add a small, specific gesture in the arrival follow-up — not in the warning text itself. Example: "Thanks for your patience today — I've taken $25 off your invoice for the wait." Small, named, tied to the specific inconvenience.
• Never offer the gesture preemptively in the warning text. "Sorry I'm late, here's 10% off" before you've even arrived reads as a bribe and invites haggling. Apologize first, deliver the job well, then let the gesture be a surprise.
• Never let the tech authorize discounts on the fly. The gesture policy (amount, threshold) is set by you in advance. Techs offering ad-hoc discounts to smooth over lateness creates inconsistency and margin leaks.

What the tech says on arrival (the in-person close)

The text handles the waiting; the arrival handles the relationship. The tech's opening line:

Thirty seconds, sincere, then straight to work. What the tech must not do: complain about the previous job, blame dispatch, or over-apologize for ten minutes — all of which keep the customer focused on the delay instead of the service. Acknowledge once, warmly, and move on. Customers take their emotional cue from the tech: if the tech is upbeat and professional, the delay fades; if the tech is flustered and guilty, the customer stays annoyed.

Compliance note

Delay notifications are transactional service messages to customers with scheduled appointments. Standard texting basics apply: 10DLC business-texting registration for business texting from a 10-digit number (1–7 day approval, ~$15–$20 one-time), opt-out language in the first text of the relationship ("Reply STOP to opt out"), and TCPA (federal telemarketing law) quiet hours for marketing texts — nothing before 8am or after 9pm in the recipient's local time. General information, not legal advice.

Related guides in this series

The late-tech text is System 8 of the full-and-calm-calendar framework — the emergency layer of the confirmation sequence. Pair it with En-Route Texts With Live Tech Tracking for the full arrival experience, and The "On My Way" Photo Text for the trust-building companion.

The done-for-you version

This post is System 8 from the Leveraged Owner Starter Pack — the done-for-you version with the full communication setup guide, every script, the dispatch checklists, and click-by-click setup instructions for all 8 systems.

No third-party research stats cited — all scripts and frameworks are the author's own.

Keep building your systems

Related guides from the Leveraged Owner blog: