Your dispatch board is full. Three crews are running, two more jobs just came in, and your phone rings for the fourth time in an hour. It’s Mrs. Patterson again, asking when the tech will arrive for her water heater replacement. You already told her 1 to 3 PM when she called at noon. Now it’s 1:15 and she wants an update.

You pull up the dispatch screen, text the crew lead, wait for a reply, call her back. Five minutes gone. The phone rings again before you hang up.

This is the hidden tax of growth in trades businesses. The more jobs you run, the more customers call to ask where you are. It’s not their fault. They took the afternoon off work. They’re watching the driveway. And your crews are good, they just don’t have time to send a text every time they leave the supply house or hit traffic on the bridge.

The cost isn’t just the interruption. It’s the jobs you miss while you’re on the phone, the estimates you don’t follow up on, and the slow erosion of trust when a customer has to chase you for information. A typical trades business doing $3M in revenue fields 40 to 80 inbound status calls per week. If half of those calls come in while you’re dispatching or on a job site, you’re losing three to six hours of productive time just playing operator.

AI agents fix this by sending automatic status updates at every milestone. Tech dispatched. En route. Arrived on site. Job started. Completed. The customer gets a text or email at each step without anyone on your team lifting a finger. The calls stop because the information is already in their hands.

What Triggers the Status Call

Customers don’t call because they’re difficult. They call because they don’t know what’s happening. You gave them a four-hour window and it’s hour three. Or you said “this afternoon” and it’s 4 PM. Or the tech said he’d be there in 20 minutes and it’s been 35.

The trigger is uncertainty. They have no visibility into where the truck is, whether the part came in, or if the job is still on the schedule. So they call. And if you don’t answer, they call again. Then they leave a one-star review saying you’re hard to reach.

Most trades businesses try to solve this with better dispatch software. They buy a tool that shows truck locations on a map and assume that fixes it. It doesn’t, because the customer can’t see the map. The information lives in your system and dies there. The gap between what you know and what the customer knows is where the calls come from.

The manual workaround is to have someone send updates. Your dispatcher texts every customer when the crew leaves the shop. Your office admin emails when a job is delayed. It works until you’re running eight jobs a day and the admin is spending two hours just on status updates. Then it stops working because someone forgets or gets busy and the calls come back.

What an AI Agent Does Instead

An AI agent watches your dispatch system and sends updates automatically based on what’s happening in the field. It doesn’t wait for someone to remember. It doesn’t get busy. It triggers on events.

Here’s what that looks like in practice. You book a furnace repair for Thursday morning. The system sends a confirmation text immediately with the four-hour arrival window and a link to reschedule if needed. Wednesday afternoon, it sends a reminder with the tech’s name and a tighter two-hour window. Thursday morning at 8:47 AM, the tech marks the previous job complete and your system dispatches him to the furnace repair. The agent sees the dispatch event and sends a text: “Mike is on his way. Expect him between 9:15 and 9:45 AM.”

At 9:32 AM, Mike pulls into the driveway. He taps “arrived” in the mobile app. The agent sends another message: “Mike has arrived and will be at your door shortly.” At 10:18 AM, Mike closes the work order. The agent sends a completion summary with the invoice link and a request for a review.

The customer never called. They didn’t need to. They had more information than they wanted.

This is what we build with the AI audit for trades businesses. We map every customer touchpoint in your dispatch flow, identify where uncertainty creates calls, and deploy agents that close the gap. It’s not a chatbot. It’s a system that watches your operations and communicates on your behalf.

The Three Milestones That Matter

Not every event needs a message. If you send ten texts for a two-hour job, you’re annoying people. The goal is to send the minimum number of updates that eliminate uncertainty.

Three milestones cover 90% of status calls: dispatched, en route, and completed.

Dispatched means the job is real and someone is coming. This is the message you send when you assign the crew in your dispatch tool. It confirms the appointment, gives a tighter arrival window than the original booking, and includes the tech’s name. It answers the question “Is this still happening today?”

En route means the truck is moving toward the customer’s location. This is the message you send when the previous job closes or the crew leaves the shop. It gives a specific ETA based on drive time and current location. It answers the question “When will you get here?”

Completed means the work is done, the invoice is ready, and you want feedback. This is the message you send when the work order closes. It includes a summary of what was fixed, a link to pay if they haven’t already, and a request for a review. It answers the question “What did you do and what do I owe?”

If you only automate these three messages, you’ll cut status calls by 60% to 75%. Add a fourth milestone for “arrived on site” if you run a lot of commercial work or jobs where the customer isn’t home. That one reassures property managers and landlords that the crew showed up even if they’re not there to see it.

One HVAC business we work with runs 22 trucks across two metro areas. Before automation, their office manager spent 90 minutes a day answering “where’s my tech” calls. After deploying a status agent, inbound call volume dropped 68% in the first month. The office manager now spends that time calling cold leads and booking maintenance agreements. The ROI was immediate.

How It Integrates with Dispatch

The agent doesn’t replace your dispatch software. It sits on top of it and watches for trigger events. When something changes in the system, the agent sees it and acts.

Most trades businesses use ServiceTitan, Housecall Pro, Jobber, or FieldEdge. All of these platforms expose webhooks or API endpoints that let external systems subscribe to events. When a job is dispatched, the platform fires a webhook. The agent receives it, pulls the customer’s phone number and job details, and sends the “dispatched” message. Same process for arrival, start, and completion.

If your dispatch tool doesn’t support webhooks, the agent can poll the system every few minutes and look for changes. It’s less elegant but it works. The customer doesn’t know the difference.

The integration takes a few hours to set up. We map your job statuses to the milestones that matter, write the message templates, and connect the agent to your dispatch API. Then we test it on a few jobs to make sure the timing and tone are right. Once it’s live, it runs without supervision.

You can override it if you need to. If a job is delayed and you want to send a custom message, you send it. The agent sees that you already communicated and skips its automatic update. If a customer opts out of texts, the agent respects that. If a job is flagged as “do not contact,” the agent ignores it.

The Dispatch Voice Agent Covers the Gaps

Status updates eliminate most inbound calls, but not all of them. Customers still call to book new work, ask questions about the invoice, or report an issue with the repair. If no one answers, you lose the job or the relationship.

The 24/7 Dispatch Voice Agent handles those calls. It’s an Omni voice agent that answers every inbound call, qualifies the job, checks your availability, and books the appointment directly into your dispatch system. It sounds like a person. It knows your service area, your pricing structure, and your crew schedules. It can tell the difference between an emergency and a routine call.

If someone calls at 9 PM on a Saturday because their basement is flooding, the agent books an emergency slot and texts the on-call tech. If someone calls on Monday morning to schedule a tune-up, the agent offers three available windows and confirms the booking. If someone calls with a question the agent can’t answer, it takes a message and texts you immediately.

This agent works alongside the status agent. One reduces outbound communication work, the other eliminates inbound communication gaps. Together they handle 80% to 90% of the phone volume that used to land on your desk or your dispatcher’s desk.

We’ve seen this cut missed calls from 15 per week to zero. That’s $1,500 to $4,000 in recovered revenue per week for a typical residential service business. Over a year, it’s $75K to $200K. That’s the cost of a skilled dispatcher, except the agent works nights, weekends, and holidays without overtime.

Follow-Up and Review Collection Close the Loop

Proactive status updates keep customers informed during the job. But the relationship doesn’t end when the truck leaves. You want them to pay on time, leave a review, and call you next time they need work.

The Review and Reactivation Agent handles this. It’s an Omni ops agent that sends a review request within 24 hours of job completion. It monitors the response. If the customer leaves a five-star review, the agent thanks them and asks if they know anyone else who needs service. If they leave a three-star review, the agent flags it for you to call personally. If they don’t respond, the agent follows up once more after three days and then stops.

The same agent tracks service intervals. If you installed a water heater in March and it’s now September, the agent sends a maintenance reminder. If you quoted a roof replacement in May and the customer didn’t book, the agent checks in during storm season. It’s not pushy. It’s timed to the natural cycle of the work.

This is where most trades businesses leave money on the table. They do great work, the customer is happy, and then nothing happens. No review request, no follow-up, no reactivation. The customer forgets your name and calls whoever shows up first in Google next time.

The agent fixes that by staying in touch without adding work to your plate. It’s the difference between a one-time customer and a repeat customer. Over three years, a repeat customer is worth three to five times the initial job value. The agent captures that value automatically.

If you want a practical framework for recovering after-hours calls and reactivating stale leads, we’ve built a worksheet that walks through the process step by step. Grab the After-Hours Call Recovery Plan for Trades and use it to map your current gaps. It pairs well with the audit because it shows you where the biggest leaks are before we build the agents to fix them.

What This Looks Like in a $5M Business

Let’s put numbers to it. You’re running a plumbing business doing $5M in annual revenue. You have 12 trucks, two dispatchers, and an office admin who answers phones and processes invoices. You’re getting 60 to 80 inbound calls per day. Half are new jobs, a quarter are status checks, and the rest are billing questions or follow-ups.

Your dispatchers spend three hours a day answering status calls and sending updates. That’s 15 hours per week, or $30K per year in fully loaded labor cost. Your office admin spends another two hours a day on the same work. Add another $20K. You’re spending $50K a year just keeping customers informed about jobs that are already booked.

Deploy a status agent and that work disappears. The dispatchers focus on routing crews and handling complex scheduling. The admin focuses on invoicing and collections. You recover 25 hours per week of productive time. If you redeploy half of that time to outbound sales or estimate follow-up, you’re looking at $100K to $150K in incremental revenue. The agent pays for itself in the first quarter.

Add the voice agent and you stop missing calls. If you’re currently missing 10 calls per week and half of those are bookable jobs, that’s another $2,500 to $5,000 per week in recovered revenue. Over a year, it’s $130K to $260K. The combined ROI is 4x to 8x in year one.

This isn’t a projection. It’s what we see in businesses that deploy both agents together. The math is conservative because it doesn’t include the value of better reviews, higher repeat rates, or the time you get back to work on the business instead of in it.

Why This Works Better Than a Dispatch App

Most dispatch tools have a customer portal or tracking link. You send the customer a URL and they can see where the truck is on a map. It sounds great. In practice, 15% of customers click the link. The other 85% call anyway because they didn’t see the text, they lost the link, or they don’t want to open a browser.

The problem is friction. You’re asking the customer to take an action. Click here, log in, check the map. It’s one step too many. Most people just call because calling is faster.

An AI agent removes the friction. It pushes information to the customer in the channel they already use. Text message, email, or voice call. No link to click, no app to download, no portal to log into. The update just arrives. It’s the difference between pull and push. Pull requires effort. Push requires nothing.

This is why proactive updates cut call volume and tracking links don’t. The agent meets the customer where they are instead of asking them to come to you.

How to Start

You don’t need to automate everything at once. Start with the three core milestones: dispatched, en route, completed. Pick one job type or one crew and run it as a pilot for two weeks. Measure inbound call volume before and after. If it drops, expand to the rest of the fleet. If it doesn’t, adjust the message timing or content and try again.

If you’re building with Claude or Codex right now, grab the free Working With Claude field guide. Thirty-two pages on the full ecosystem, Claude Code in depth, and how to roll agents out properly. Get the free guide.

If you want to explore more about how AI agents fit into the broader operations of a trades business, start with our guides or dig into the Omni platform overview. The voice and ops agents we’ve described here are part of a larger system that handles everything from lead qualification to invoice follow-up. Status updates are just one piece, but they’re the piece that delivers the fastest ROI because the pain is so visible.

The goal isn’t to replace your team. It’s to give them leverage. Your dispatchers stop answering the same question 40 times a day and start solving the complex scheduling problems that actually require judgment. Your admin stops playing phone tag and starts closing estimates. You stop being the bottleneck and start running the business.

That’s what proactive status updates unlock. Not a better customer experience, though that’s a nice side effect. A more efficient operation that scales without adding headcount. The customers stop calling because they don’t need to. And you get your time back.