It's 3:50 and your two-o'clock customer has been home since noon. They took a half-day off work for this, and the window was 2 to 4. The truck's not in the driveway. They're standing near the front window with the phone in their hand, deciding whether to call.
You already know why the tech's late. The morning job ran long, a condensate pump had to come from the supply house clear across town, and I-610 did what I-610 does on a hot afternoon. None of that is the customer's problem, and none of it is in front of them. All they see is an empty driveway and a window that's about to close.
So they call. And that call lands on your desk in the exact stretch of the day when you've got the least room to take it. One late tech can spin up three or four of these, and now your front desk is reading the schedule board out loud instead of booking tomorrow's work.
Why that one call ties up your whole afternoon
Here's the part that stings. The "where's my tech" call doesn't move a single truck one foot closer. The tech's still stuck on the Loop whether the customer phones in or not. All the call does is pull your desk off the work that actually pays, right when the afternoon rush is stacking up.
And it rarely stays one call. A tech running ninety minutes behind might have three more stops waiting on him, which is three more people watching an empty driveway. Each one phones in, your desk reads the board, apologizes, hangs up, then does it again twenty minutes later when the next one calls.
Worse, the customer who had to call to find out is the one who leaves the one-star review. Not because the tech was late (people get that jobs run long) but because nobody told them. Late plus silence reads as "they forgot about me." Late plus a heads-up reads as "they're on top of it."
Send the new window the moment the schedule moves
The fix is a text that goes out automatically the second the appointment moves, not whenever someone at the desk finds a free minute to send it. If your dispatch or scheduling software lets you change a job's time window or arrival estimate (most do), that change itself can be the trigger, meaning the event that kicks off the text with no one pushing a button.
It works like this. When a dispatcher drags the 2-to-4 job into a 4-to-6 slot, or the tech marks the current job as still running, the system fires a text to the customer on file: new window, who's coming, and a way to reply. Nobody has to remember to do it. The schedule change is the thing that sends it.
That last point matters more than it sounds. If sending the text is a separate manual step, it won't happen on the afternoons you need it most, because those are the afternoons nobody has a spare hand. Tie the message to the schedule move itself and it goes out at 1:55, before the customer has even started wondering.
What the text should actually say
Keep it short and keep it useful. A customer glancing at their phone between things needs three facts: when now, who's coming, and what to do if that doesn't work. Everything else is noise.
- The new window, stated plainly. "Your tech is now arriving between 4 and 6." Not "we're experiencing delays." Give them a number they can plan the rest of the afternoon around.
- Who's coming. "Marcus is headed your way." A name turns a stranger at the door into an expected guest, and it's a small comfort for anyone home alone.
- A confirmation it's still happening today. The quiet fear is that they've been bumped to tomorrow. Say "still today" so they can stop worrying about it.
- A way to reply. Let them text back if 4-to-6 no longer works. Better to learn that now than to roll the truck to an empty house.
If you can add a live tracking link once the tech is actually en route, good, but don't let that hold up the first text. The window and the name do most of the work on their own.
Where this breaks, and what to watch
Be honest with yourself about the limits. Automation can send the new window the instant you change it, but it can't know the window changed until somebody changes it. If the tech runs long and nobody moves the job in the system, no text goes out and you're right back where you started. The habit you're building is "move the job the moment you know," not "remember to send a text."
Don't over-text, either. One clear update when the window moves is reassuring. A text every fifteen minutes is annoying, and people start ignoring them, which defeats the whole point. Set it to fire on a real change, not on a timer.
One more thing. The message is only as good as the phone number on the ticket. If your intake is grabbing a landline, or a cell number with a typo in it, the text lands nowhere and the customer calls anyway. Clean numbers at booking are what make the back end work.
Worth doing this week
You don't need to automate the whole schedule to get this win. Start small and build on what works.
- Pull last week's inbound calls and count the "where's my tech" ones. That number is what you're trying to shrink, and it tells you how big the problem really is.
- Check whether your scheduling software can send a text when a job's time window changes. If you're not sure, call the vendor and ask that exact question.
- Write the one text. Fill in the new window, the tech's name, "still today," and a reply-to number. Keep it to three short lines.
- Decide the single trigger that fires it: a dispatcher moving the job, or the tech tapping "running late" from the truck. Pick one so it's clear who owns it.
- Run it on your afternoon routes for a week, then ask the desk whether the calls dropped. Adjust the wording from there.
Getting the right text out before the customer reaches for the phone is the kind of small, dull system that quietly saves your afternoons and your reviews. If you'd like a hand wiring it into the software you already run, that's the sort of setup we do for Houston shops. Either way, it's worth an afternoon of your own time to get right.