A technician en route text update is a small thing that prevents a lot of avoidable noise: customers calling the office for an ETA, dispatchers calling a tech who is driving, and a technician arriving at a locked house. For a 2-to-10-truck shop, that noise adds up fast. The right message sets a clear expectation without turning dispatch into a full-time status-reporting job.
The goal is not to send more texts. It is to send one useful text at the moment it matters.
What a technician en route text update should do
A good en route message answers the question the customer actually has: “When should I expect someone?” It confirms that the appointment is real, identifies the company or technician when appropriate, and gives a reasonable arrival window.
Keep it plain. A customer does not need a paragraph about traffic, prior jobs, or your routing process. They need enough notice to put the dog away, get home from school pickup, or make sure someone can open the door.
Here is a solid baseline:
> Hi, this is Mike with Acme Plumbing. I’m on the way and expect to arrive in about 25-35 minutes. Reply here if anything has changed.
That message is specific without overpromising. “About 25-35 minutes” is better than “I’ll be there at 2:00” when a technician is coming from a previous call and real life is still happening.
For commercial work, the wording may need to change. A property manager may care less about a precise window and more about knowing which tech is arriving and whether they need access. In that case, send the technician’s name and an approximate arrival time: “Jordan is en route to Suite 204 and should arrive around 1:30 PM.”
The timing matters more than the wording
The best copy in the world does not help if it goes out at the wrong time. Send the customer update when the technician has actually left for that job, not when the office hopes they will leave.
That sounds obvious. Plenty of shops still send automatic notifications when a job is assigned or moved on a calendar. Then the prior repair runs long, the tech detours for a part, and the customer gets a message that was technically sent but operationally useless.
A reliable workflow has three distinct moments:
1. The office assigns the job
Dispatch sends the job details to the technician: customer name, address, issue, contact information, access notes, and any useful history. At this point, the customer does not need an “on the way” text because nobody is on the way yet.
2. The technician confirms they are moving
The technician replies with a simple status such as “OTW.” No app. No login. No tapping through five screens while sitting in a truck. That reply tells the office the job is active and gives dispatch a real trigger for the customer message.
3. The customer gets the update
Once the office sees that status, it sends the technician en route text update. Some shops automate this step. Others want a dispatcher to check the message first, especially when the route is long or the schedule is already slipping. Either approach can work. The non-negotiable part is that the message follows an actual technician status.
That discipline is the product. If “en route” can mean “assigned,” “finishing lunch,” or “maybe leaving soon,” the status is not useful to anyone.
Give an ETA window, not false precision
Small shops often hesitate to send ETAs because they have been burned by them. A technician says 20 minutes, gets stuck behind an accident, and now the customer is irritated before the work even starts.
The answer is not silence. It is a window with enough breathing room.
For nearby residential calls, 20-40 minutes is often reasonable. For jobs across town, a 45-60 minute window may be more honest. If the technician is wrapping a diagnosis or heading to a supply house first, do not call them en route. Say what is true: “Your technician is scheduled next and we will text when they are headed your way.”
A wider, accurate window beats a narrow, missed promise. Customers can plan around honest information. They cannot plan around a dispatch office that disappears until the doorbell rings.
Use the same message structure every time
Consistency matters because it removes decisions from a busy day. Your office should not rewrite the same update from scratch between phone calls, reschedules, and vendor deliveries.
A dependable en route text has four pieces: a greeting, the technician or company name, an ETA range, and a simple way to report a problem. You can use the same structure for nearly every residential job.
Try these variations based on the situation:
Standard residential visit
> Hi Sarah, this is Ben with Northside HVAC. I’m on my way and should arrive in 30-45 minutes. Please reply if there are gate codes or access details we should know.
Customer has a narrow availability window
> Hi Sarah, Ben is en route and expects to arrive around 3:15 PM. Please let us know right away if that timing no longer works.
Tech is delayed after a previous call
> Hi Sarah, your technician is running about 30 minutes behind schedule. We expect Ben to be on the way by 3:30 PM and will text again when he leaves.
That third message is not fun to send. Send it anyway. A proactive delay text is cheaper than an angry call, a canceled appointment, or a technician driving to a customer who has already left.
Do not make the technician write customer messages
Technicians need to communicate status. They should not have to compose polished customer updates while driving, carrying equipment, or trying to finish a call cleanly.
Ask for short, standardized status replies instead. “OTW” means en route. “HERE” means arrived. “DONE” means the job is complete. Dispatch can see the change, update the board, and send the appropriate customer communication if needed.
CopyThat is built around that exact behavior. Techs just text status updates, while the office keeps the job card, schedule, notes, and history in one place. It is not trying to turn your technicians into software operators. Honestly, they have enough to do.
There is a trade-off. An app with GPS can generate automatic arrival estimates, route maps, and location alerts. That may make sense for a larger operation with complex routes and a dedicated operations person. For a small shop, it can also mean another rollout, another login, another monthly bill, and another thing technicians ignore. A simple text-driven workflow is usually better when the real problem is basic coordination.
Protect the customer experience after the text
An en route message creates an expectation. Make sure the rest of the process backs it up.
If the customer replies with a gate code, a request to call on arrival, or a note that their spouse will be home instead, that information needs to land on the job record where the technician and office can find it. It should not be buried in one dispatcher’s personal phone thread.
Likewise, if the customer says they cannot make the appointment, do not leave the technician heading into a dead stop. Update the job status, alert the tech, and use that drive time for a nearby call, a parts run, or the next job. This is where a shared dispatch board earns its keep. Not through fancy dashboards. Through fewer wasted truck rolls.
A simple policy your team can follow
Write the rule down: customers receive an en route update only after the technician confirms they are leaving for the job. Use a standard ETA window. If that window changes materially, send a delay message before the customer has to ask.
Then make the system easy enough to follow during a bad Tuesday. If technicians have to install something, remember a password, and navigate an app just to say they are heading out, compliance will fade. If they can text three letters, they will actually do it.
Start with one standard message this week. Watch how many “Where is the tech?” calls disappear. That is time your office can spend keeping the schedule moving instead.