The En-Route Text: Killing "Where's My Tech?" Calls Forever

One text, sent when the tech starts driving, eliminates the most annoying call in contracting. The 15-minute rule, the exact wording, and why proactive beats reactive every time.

System 8 from the Leveraged Owner Starter Pack

"Where's my tech?" It's 10:40. The window was 9–11. The customer has called twice. Your tech is 12 minutes away, stuck behind a school bus, and now he's also fielding an annoyed customer while driving. The job hasn't even started and the review is already at risk. All of it — the calls, the stress, the bad review risk — prevented by one text sent at 10:15.

The en-route text is the fourth touch of the confirmation cadence in the pillar guide, Appointment Confirmation Texts That Cut No-Shows in Half. This post is the deep dive: why it's the highest-ROI text you'll ever send, the exact mechanics, and the upgrades (live tracking, tech photo) that turn it into a review machine.

Why this one text matters so much

"Where's my tech?" calls are pure waste: they interrupt the tech (who's driving), interrupt the office (who has to track the tech down), and annoy the customer (who feels ignored). But the deeper cost is psychological — a customer who's been wondering and worrying for 40 minutes greets the tech with tension instead of warmth. The whole job starts downhill. The en-route text flips it: the customer knows who's coming and when, so they greet the tech relaxed. Same tech, same job, completely different review outcome.

The 15-minute rule

Send the en-route text when the tech is 15–30 minutes out — not when they leave the shop (too early, the ETA is fiction), not when they're pulling into the driveway (too late, the wondering already happened). Fifteen minutes is the sweet spot: close enough that the ETA is real, far enough that the customer can wrap up what they're doing.

Who sends it: ideally the tech, from the tech's phone or the dispatch app — it should read like it's from the human who's driving there. If the tech can't (driving, no signal), dispatch sends it in the tech's name. The automation version: your field-service software (field-service software = field service management software — Jobber, Housecall Pro, and similar) can fire it when the tech taps "en route" on the job.

The exact wording

Hi [First Name], it's [Tech Name] from [Business Name] — I'm on my way and should be there around [ETA]. See you soon!

That's it. Twenty words. The components: the tech's name (a person is coming, not a company), a real ETA (not "soon"), and warmth ("see you soon"). What it doesn't need: the work order number, the service description, a link. This text has one job — answer "where's my tech?" before it's asked.

The two upgrades

Upgrade 1: The tech photo text

Add the tech's name, photo, and a one-line bio to the en-route text:

Hi [First Name]! Your tech today is [Tech Name] [photo] — he's been with [Business Name] for [X] years and should be there around [ETA]. See you soon!

The trust effect is outsized: the customer opens the door to a face they've already seen, not a stranger. It also protects the tech — identified, expected, welcome. The review-lift mechanism is straightforward: customers review people, and now they know the person's name before he arrives.

Upgrade 2: Live tracking link

Some field-service software and dispatch tools generate a live map link — "watch your tech arrive." The text becomes:

Hi [First Name], [Tech Name] is on the way — track his arrival here: [Tracking Link]. ETA around [ETA]. See you soon!

Live tracking kills the last 10% of "where's my tech?" calls — the ones from customers who got the text but still worry. It's also a quiet competitive weapon: the big national chains do this, and now you do too. (The full live-tracking setup is its own post in this series.)

When you're running late (the companion text)

The en-route text assumes you're roughly on time. When you're not — previous job ran long, traffic — send the late text before the window expires, not after. Thirty minutes of warning beats any apology:

Hi [First Name], it's [Tech Name] — running about [25] minutes behind (last job ran long). New ETA around [Time]. Really sorry about the wait — still good for today? Just reply here.

"Still good for today?" gives them an out instead of a grievance. Honesty before the deadline protects the 5-star; silence past the deadline destroys it. The late-tech text is its own post in this series — it's that important.

Making it stick (the operational part)

Measuring the effect (prove it to yourself)

The en-route text is cheap to test. For one month, track three numbers and compare against the prior month:

The dispatch-board integration (for multi-tech shops)

With 3+ techs, the en-route text needs dispatch visibility — otherwise two techs text from the truck while dispatch has no idea who told the customer what. The setup: the field-service software dispatch board shows each job's communication status (confirmed → en route text sent → arrived), updated by the tech's status taps. Dispatch glances at the board and knows every customer's state without calling anyone. The rule: the board is the source of truth, not the group chat. Texts in the group chat get buried; status on the board persists. Fifteen seconds of tech discipline per job saves dispatch hours of "did anyone tell the customer?" per week.

Compliance note

En-route texts are transactional — the customer booked the visit. Baseline rules still apply: 10DLC business-texting registration on your business number (1–7 day approval, ~$15–$20 one-time), opt-out language in the first automated text, and observe TCPA (federal telemarketing law) quiet hours (no marketing texts before 8am or after 9pm in the recipient's local time). This is general information, not legal advice.

Related guides in this series

The cadence: the appointment-confirmation pillar. The upgrades: En-Route Texts With Live Tech Tracking: The Setup Guide and The "On My Way" Photo Text. The late version: Running Behind? The Late-Tech Text That Saves the Review. Browse the full blog for everything published.

The done-for-you version

This post is System 8 from the Leveraged Owner Starter Pack — the done-for-you version with the full en-route setup guide (standard operating procedure), every script variant (photo, tracking, late), the field-service software tap-to-send setup, and screen-by-screen setup instructions for all 8 systems.

Stats sourced as labeled: no third-party stats in this post — built from dispatch best practices.

Keep building your systems

Related guides from the Leveraged Owner blog: