A technician who is 20 minutes late is not always the problem. The problem is when nobody knows they are 20 minutes late until the customer calls, the next job is already waiting, and the office starts dialing every truck. Text message job updates fix that gap when they are tied to a real dispatch process, not tossed into a group chat and forgotten.
For a 2-10 truck plumbing or HVAC shop, the goal is not to turn every field movement into data entry. It is to make the few updates that matter visible to the people scheduling work. Techs already know how to text. Use that.
Why text message job updates work in small shops
Small shops run on fast decisions. A no-cool call becomes urgent at 1:30. A water heater job takes longer than expected. One technician needs a part, while another finishes early across town. The office needs a clear answer without chasing people down.
A short text works because it happens where the technician already is: their phone. No app to install. No password reset. No "did you see the notification?" routine.
But texting alone is not a system. A group thread can tell everyone that Mike is on the way, but it cannot reliably show which customer Mike is headed to, what was promised, whether the job is complete, or where the notes belong. By Friday, that useful message is buried under photos, jokes, and six conversations about parts.
The useful version is simple: send a job card, receive a standard reply, update the dispatch board. The text stays easy for the technician. The office gets a shared record instead of relying on memory.
The three job updates that do most of the work
You do not need 14 status codes. More codes create hesitation, and hesitation means no update. Most service shops can keep the day moving with three clear replies: OTW, HERE, and DONE.
OTW means the truck is committed
OTW should mean the technician is actually leaving for that specific job, not that they noticed the assignment. That distinction matters when a dispatcher is deciding whether to promise the customer a tighter arrival window or send a different truck.
A job text might read: “Johnson residence, 214 Oak St. No AC. Customer home after 1 PM. Reply OTW when leaving.” The technician replies OTW. The office sees the job move from assigned to en route.
That is enough to trigger the next action: notify the customer if needed, stop calling other techs, and start planning the technician’s next stop.
HERE confirms the customer-facing handoff
HERE is useful for more than a timestamp. It tells the office the technician made it to the address and the job is underway. If a customer calls asking where the truck is, the dispatcher has an answer without interrupting the technician.
It also exposes exceptions early. If a tech has been OTW for 45 minutes on a job that is normally 15 minutes away, the office can check in before the schedule starts sliding. Traffic, a wrong address, a tire issue, or a customer who is not home are all easier to handle when they are visible early.
DONE closes the loop before the details disappear
DONE should be sent when the technician is finished at the job, not when they remember to update the office at the end of the day. The dispatcher can then fill an opening, send the next assignment, or tell a waiting customer that a truck is available sooner.
For jobs that need follow-up, the technician can add one plain-language note: “DONE - needs blower motor ordered” or “DONE - customer declined repair.” Keep the update short. The office can capture the full notes, parts needs, and return visit details in the job record.
That division of labor matters. Techs should not have to write a novel from a driveway. The office should not have to reconstruct a job from a half-remembered phone call.
Make the job text specific enough to act on
A text that says “Go to Smith” is an invitation to confusion. Which Smith? Where? What is wrong? Is the customer expecting a morning arrival or an afternoon one?
Every dispatched job should include the customer name, address, problem, timing notes, and anything that changes how the technician approaches the call. For example:
> Perez, 88 Willow Lane. Water heater leaking at top connection. Customer says garage is unlocked. ETA window 2-4 PM. Reply OTW when leaving.
That is not complicated. It is the information the technician would ask for over the phone anyway, delivered in a format they can search later.
If there is a gate code, a dog on site, a warranty note, or a customer who requires a call before arrival, put it on the job card. Do not trust the dispatcher to remember it while handling five other calls.
Standard replies beat clever wording
The office should never have to interpret whether “heading there,” “on my way,” “leaving now,” and “be there soon” all mean the same thing. Pick the replies, explain what they mean, and stick with them.
The point is not to police technicians. It is to remove ambiguity from a busy day. When every tech uses OTW, HERE, and DONE, the dispatch board tells the truth at a glance.
This is also why one-off wording can cause trouble. “Wrapped up” might mean the repair is complete, the customer paid, the technician is still writing notes, or they are simply done trying. A standard status means one thing.
If a technician needs help, give them a separate, obvious way to ask for it. A text such as “HELP - need second tech” or “PART - need 3/4-inch gas valve” gets attention without falsely closing the job. The dispatcher can respond by phone when the situation needs a conversation.
Set the rules before the schedule gets busy
Text-based dispatch works best when the team knows the expectations before Monday morning. A five-minute conversation is usually enough: reply OTW when wheels are turning, HERE when you arrive, and DONE before you leave the final job. If something changes, say so early.
Do not demand an update for every bathroom break, supply-house stop, or traffic light. That is how a useful routine becomes another administrative chore. Ask for updates at the moments that affect customers, assignments, and the next truck decision.
There is a trade-off. A more detailed workflow can produce more reporting, but it also asks more from technicians. For a small service shop, compliance is usually worth more than a perfect dataset. Three reliable updates beat ten statuses nobody uses.
Keep customer history out of personal phones
A technician’s phone is a communication tool, not your company database. If job addresses, repair notes, and customer details live only in texts, you have a problem when someone is off, changes numbers, loses a phone, or leaves the company.
The office needs a searchable home for the job card and its status history. That way, when Mrs. Perez calls six months later about the same water heater, the person answering can see what happened instead of texting three people who may not remember.
This is where a lightweight dispatch board earns its keep. CopyThat, for example, turns simple text replies into visible job statuses while keeping the customer record and notes in the office. The technician still just texts. Like it says on the tin.
Watch for the failure points
The most common failure is treating text updates as optional. If the office keeps calling for every status anyway, technicians learn that the system does not matter. If managers do not look at the board, nobody else will either.
The other failure is sending vague or duplicate assignments. Before dispatching a job, confirm that it has one owner. If a technician is reassigned, close the loop with the first technician rather than assuming they saw a new message in a noisy thread.
Carrier registration and business texting rules can also affect delivery. Use a platform that handles business messaging properly, and make sure technicians know which number will send assignments. A missed update is one thing. A job text blocked or filtered as spam is another.
Finally, know where texting stops being the right tool. If you need route optimization, GPS tracking, complex estimates, inventory controls, payroll, or a full customer marketing system, an app-heavy field-service platform may fit better. Small shops should not buy bloat, but they should not pretend a dispatch tool is something it is not.
The best text message job updates are almost boring. OTW. HERE. DONE. When those three replies are consistent and connected to the right job, the office stops guessing, customers get better answers, and your trucks spend less time waiting for the next call.