The real cost of “Where’s my technician?”

Most trades owners don’t see job-status calls as a serious operational problem. They see them as part of running a service business.

A customer calls at 9:40am because their 8:00am to 10:00am window is nearly over. The office checks the dispatch board. The technician is finishing a previous job, stuck at a supplier, or sitting in traffic. The office calls the technician. The technician doesn’t answer because they’re under a sink, on a roof, or in an electrical panel. The customer calls again 15 minutes later.

That sequence is normal in plumbing, HVAC, electrical, and roofing businesses. It is also expensive.

The call itself might take three minutes. The back-and-forth to find a reliable answer can take another five to ten minutes. If an admin handles 12 to 20 status inquiries in a day, that is easily 1.5 to 3 hours of office time spent relaying information that your dispatch system, technician GPS, and job milestones already hold.

For an owner doing $1 million to $25 million in annual revenue, the impact is wider than payroll.

• Dispatch loses focus while new inbound calls wait.
• Technicians receive interruption calls while doing chargeable work.
• Customers interpret silence as unreliability, even when your team is working hard.
• The owner becomes the escalation point for a simple ETA question.
• A missed inbound call can become a lost service job worth $500 to $3,000.

The objective isn’t to prevent customers from wanting information. It is to provide the information before they need to call.

A well-built update workflow can remove roughly 70% of inbound status inquiries because customers receive clear messages at the moments that create uncertainty. Booking confirmation. Appointment reminder. Technician en route. Technician delayed. Job started. Job complete.

That is a better customer experience, but it is also a capacity decision. Your office gets time back to book work, chase approvals, and manage exceptions that genuinely need a person.

For a broader view of where this fits, see Omni for trades businesses.

Why job-status calls keep happening

The issue is rarely that your team does not care. It is that the information flow is manual.

A typical service workflow has several gaps:

1. A customer gets an appointment window, often by phone.
2. The first technician’s job runs long.
3. Dispatch knows the schedule has changed but does not have time to contact every affected customer.
4. The next customer has no update.
5. They call the office to ask where the technician is.
6. Dispatch interrupts the technician or makes an educated guess.
7. The answer arrives late, if it arrives at all.

Roofing and larger project trades have a version of the same problem. The customer calls because a material delivery has shifted, weather has changed the schedule, permits are pending, or the crew’s start date has moved. They are not always angry. Often, they are trying to plan their own day. But a business that makes customers chase basic information creates unnecessary friction.

Appointment windows make this worse. A four-hour window might be operationally sensible, especially during emergency call volume. It feels vague to a customer who has taken time off work. If the window starts at 8:00am and the technician is now likely to arrive at 11:30am, the customer needs that information at 9:30am, not after their third phone call.

The answer is not to promise unrealistic arrival times. The answer is to communicate a live, honest expectation.

Map the calls before you automate them

Don’t begin by sending more texts. Begin by identifying the questions customers are actually asking.

Pull two weeks of inbound call notes, voicemail transcripts, and dispatch comments. Mark every call that relates to job status. You will normally find a small number of repeat triggers.

The common triggers

For service businesses, these usually include:

• “Is the technician still coming today?”
• “What time will they arrive?”
• “Can you tell me when they are on the way?”
• “The appointment window has passed.”
• “My technician didn’t show up.”
• “Has the part arrived?”
• “When will the work be finished?”
• “Is the crew coming back tomorrow?”

Then look at the operational event behind each question. You are not trying to automate every customer conversation. You are identifying moments where a system can confidently give the right update.

For example:

Customer question	Trigger for an automated update
Is someone still coming today?	Technician is delayed beyond the original arrival window
When will they arrive?	Technician marks en route or GPS shows travel has started
Has the part arrived?	Parts status changes to received
Is work complete?	Technician closes the job in the field app
Are you coming back tomorrow?	A return visit is scheduled or rescheduled

This simple mapping exercise often shows why the calls are occurring. The data exists, but it is trapped in job notes, a dispatcher’s head, technician text threads, or the field service platform.

If your office is manually chasing technicians for answers, the workflow is not scalable. It only works until call volume rises, somebody takes leave, or the owner is pulled into the day-to-day dispatch queue.

What proactive job updates should look like

A useful job-status workflow does not bombard customers. It sends short, specific messages that answer the next likely question.

Here is a practical service-call sequence.

1. Confirmation when the job is booked

As soon as the appointment is scheduled, the customer receives a confirmation by text and email.

It should include the date, the agreed arrival window, the business name, a contact method, and any preparation needed. For HVAC or plumbing work, that might mean clearing access to the unit or ensuring an adult is present.

This first message reduces incorrect bookings and gives customers confidence that the job is on the board.

2. A reminder before the appointment

Send a reminder 24 hours before the job, or the afternoon before for early morning calls. The message confirms the window and gives the customer an easy way to reply if access has changed.

That is not a job-status update yet. It prevents failed visits and protects the technician’s time.

3. An en-route message triggered by the technician

When the technician changes status to en route in your dispatch tool, the customer gets a text such as:

Your technician, Jordan, is now on the way. Current estimated arrival is 25 to 35 minutes. Reply here if there are any access instructions.

The estimated arrival should be based on GPS or the route data available in the field platform. Don’t claim a minute-perfect ETA if your data cannot support it. A realistic range is more useful than a false promise.

4. A delay message before the customer calls

This is the most valuable part of the workflow.

If the technician is still at a prior job, GPS indicates they cannot reach the next appointment inside the window, or dispatch changes the expected arrival time, send an update immediately. Make the message plain:

We are running later than planned due to a prior job. We now expect to arrive between 11:15am and 11:45am. We are sorry for the disruption and will keep you updated.

Customers can tolerate a delay much better than silence. This message alone can take a large share of “where are you?” calls out of the queue.

5. Job-complete follow-up

When the technician closes the job, send the invoice, work summary, payment link if applicable, and a clear next step. If a part is on order or a return visit is needed, say so before the customer has to ask.

The point is not to make every communication feel automated. The point is to make your business dependable at the moments customers are most likely to feel uncertain.

How an AI agent handles the work end to end

An AI workflow should not replace dispatch judgment. It should handle the repeatable communication, detect exceptions, and hand uncertain cases to a person.

At Enterprise DNA, we build this around the systems a trades business already uses. That may include a field service management platform, calendar, GPS feed, phone system, job board, CRM, and SMS provider.

The workflow starts by reading the job status and customer record. It knows the booked window, assigned technician, job type, address, contact preference, and relevant milestones.

When a milestone occurs, the agent selects the approved message for that situation and sends it. Every message is logged against the job. If a customer replies with a simple question, it can provide the latest confirmed information. If the reply signals a problem, such as access issues, an urgent complaint, cancellation, or a request for a different appointment, it routes the conversation to dispatch with context.

That means the office team receives an exception like this:

Job 1842, Smith residence. Customer replied that nobody will be home after 12:00pm. Technician ETA is 11:35am to 12:05pm. Please confirm access or reschedule.

That is far better than making an admin reconstruct the whole situation from three phone calls and a technician text.

The workflow can work alongside the 24/7 Dispatch Voice Agent. The voice agent answers calls that still come in, identifies the caller, checks the live job status, and provides the current ETA when it is reliable. If the customer needs to change access, reschedule, or escalate an issue, the call is handed to the right person with the details already captured.

This matters after hours as well. A homeowner who calls at 7:15pm to check the next morning’s plumbing appointment should not have to leave a voicemail and wait until dispatch opens. A clear automated answer protects confidence before the day even begins.

If the problem is operational rather than informational, the agent should not pretend otherwise. It flags it. For example, if the technician has not checked in, the route data is missing, or there is no valid ETA, the workflow escalates to dispatch instead of sending a vague message.

That guardrail is essential. Good automation reduces uncertainty. It does not manufacture certainty.

The dollar reality behind fewer calls

The revenue leakage from status calls is not usually a line item in your accounts. It shows up as small losses throughout the week.

Consider a business receiving 15 status calls per day. If each one uses an average of six minutes of office time across answering, checking, and calling back, that is 90 minutes a day. Across five days, it is 7.5 hours per week.

At a loaded office cost that is typical for a growing trades business, the direct payroll cost may look manageable. But that is not the main issue. The bigger cost is what those 7.5 hours displace.

It might be:

• Calling back a new customer who needs emergency service
• Confirming a high-value estimate
• Following up a $6,000 HVAC replacement quote
• Rebooking a cancelled job
• Ensuring tomorrow’s route is ready
• Asking a satisfied customer for a review

We usually see the economic case build from three areas: recovered office capacity, fewer missed inbound opportunities, and better customer retention. Across a business of this size, the broader annual leakage from weak call handling, dispatch overhead, and neglected follow-up can land in the $50,000 to $200,000 range.

That does not mean every job-status call costs hundreds of dollars. It means a recurring communication failure creates a chain of lost capacity and missed revenue.

The same operational foundation also supports the Estimate Follow-Up Agent. When an estimate is sent, it can follow up on day 2, day 5, and day 14 using messages matched to the job type and value. Many firms find that a structured follow-up process converts a meaningful share of estimates that would otherwise go cold, often in the 15% to 25% range.

Once job completion data is clean, the Review and Reactivation Agent can ask happy customers for a review the next day and bring past customers back at appropriate service intervals. Your dispatch process should not only reduce calls. It should create a more reliable customer record that supports the rest of your growth process.

Start with one service line and prove it

You do not need to automate every job type in week one.

Pick one service line with steady volume and predictable dispatch milestones. It could be plumbing service calls, preventative HVAC maintenance, electrical fault-finding, or repair work that has clear appointment windows.

Run a four-week pilot with these measures:

• Number of inbound job-status calls
• Office minutes spent per status call
• Percentage of customers receiving booking, en-route, and delay messages
• On-time arrival rate
• Number of escalations requiring a person
• Missed calls during peak dispatch periods
• Customer complaints related to communication

Set a realistic target. If you currently receive 60 status inquiries each week, reducing that by 40 or more is a meaningful operational win. Don’t judge the system only on call volume. Look at whether customers receive honest updates earlier and whether dispatch has more time to handle live operational problems.

You should also involve your technicians early. They need to understand that changing a job status is not admin for admin’s sake. Marking en route or updating a delay triggers the customer communication that keeps their phone from ringing during a job.

For ideas on where else agents can relieve operational bottlenecks, review our guides for business operations and the wider Omni operations approach.

Use the after-hours checklist to close gaps

Job-status calls often overlap with another revenue leak, missed calls outside office hours. If you want a practical way to review your current phone handling, download the After-Hours Call Recovery Plan for Trades. It is a working checklist for call routing, emergency qualification, booking coverage, and customer confirmation.

You can also access the direct worksheet here: After-Hours Call Recovery Plan for Trades.

Find the gaps in your own dispatch process

The question is not whether automation can send a text when a technician is on the way. It can.

The useful question is where your job information breaks down, which messages customers need, what your systems can reliably trigger, and which exceptions should go to a person. That requires looking at actual calls, actual dispatch steps, and the tools your team uses each day.

A 60-minute Omni Audit does exactly that. There is no deck and no vague technology discussion. We map the workflow, identify the leakage points, and give you three practical outputs: the highest-value automation opportunities, the operating design for the agents, and the next steps to implement them.

Book a 60-min Omni Audit if job-status calls are consuming dispatch capacity and you want a clear plan to reduce them.

You can also see the AI audit for trades businesses to understand how we assess dispatch, call handling, follow-up, and customer communication across the full operating model.

The aim is simple. Your customers should know what is happening with their job before they feel the need to call. Your office should spend its time solving exceptions and booking revenue, not repeatedly chasing an ETA.