Enterprise DNA
Key Findings

See which back-office workflows can justify AI in a 10-truck plumbing company, how to estimate payback, and what to check before choosing a system.

Is AI Worth It for a 10-Truck Plumbing Company?
Insight ai

Is AI Worth It for a 10-Truck Plumbing Company?

Sam McKay

Is AI worth it for a 10-truck plumbing company?

It can be, but not because AI is new or because another software vendor says every office task should be automated. For a 10-truck plumbing company, the useful question is narrower: which repetitive work is costing you enough in missed revenue, owner time, or slow follow-up to justify paying to change it?

The usual suspects are calls that reach voicemail while the crew is working, dispatch decisions that keep the owner glued to the phone, and estimates that go out but don’t get another touch. Those problems have a dollar value. If an agent can reliably reduce them, you have a business case. If the process is already working well or the software can’t handle your actual workflow, you probably don’t.

For plumbing, HVAC, electrical, and roofing businesses, repeatable operational problems can create potential leakage. That doesn’t mean automation will recover all of it. Your own calls, jobs, margins, and admin time determine whether the investment makes sense.

A good assessment starts with the work, not the product. This is the logic behind the AI audit for trades businesses. It helps identify which workflows deserve attention and which ones should stay as they are.

The three workflows to measure first

A 10-truck operation is big enough for a steady stream of calls, estimates, and dispatch changes, but may not have enough office staff to cover every moment of the day. The owner or GM often becomes the backup for all three. That can feel normal until you count the hours and the jobs that fall through.

Calls that don’t become booked jobs

When everyone who can answer the phone is busy, a caller may hear voicemail. Some leave a message, but many don’t. They might call another plumber, especially when water is leaking or the heating has failed.

For a missed job, the potential value depends on the work. Not every missed call would have become a booked job, and revenue isn’t the same as gross profit. That makes call handling worth measuring.

Start with your call log. Count calls that arrived after hours or during busy periods, how many reached voicemail, how many left a message, and how many eventually booked. Then estimate the contribution margin on the jobs you can reasonably attribute to missed calls. If your phone system doesn’t provide this data, manually tracking calls for a couple of weeks is better than guessing.

Dispatch work that keeps landing on the owner

The owner might start the day routing crews, then spend it answering questions about job priority, travel time, parts, and customer availability. Dispatch also involves exceptions. A job runs long, a technician needs a part, or an emergency comes in while the schedule is full.

For some businesses, this can add up to substantial owner or admin time. That doesn’t mean an agent can replace the person who knows the crews and customers. It does mean routine intake and coordination may be taking time away from decisions only the owner can make.

Measure time spent on calls and routine dispatch tasks separately from time spent resolving unusual problems. Automation is more likely to help with the first category. If parts availability is a recurring source of delay, compare dispatch work with your process for tracking truck inventory in real time. Better call handling won’t fix a van that arrives without the part.

Estimates that don’t get followed up

An estimate is a job that has already taken time to scope and price. But after it’s sent, the next action can depend on somebody remembering to check the pipeline between calls and dispatch changes.

Follow-up may help convert stale estimates, depending on the business, the estimate, and the quality of the follow-up. Treat that as a possibility to test, not a guarantee. Look back at a sample of estimates that were marked lost or left open. How many received a timely second contact? How many later booked after a customer came back on their own?

For a fuller cost picture, see what AI automation costs for a plumbing company. Compare the likely monthly cost with the value of work recovered and staff time freed, not with a vendor’s headline about how many tasks it can automate.

What the workflow looks like from call to follow-up

A useful agent doesn’t just talk. It needs a defined job, information to work from, a place to record what happened, and a clear handoff when it reaches a limit.

Take an after-hours call about a leaking pipe. A voice agent could answer, ask questions to understand the issue, and sort it as an emergency or scheduled request using rules set by the business. It could check the dispatch tool for an available slot, book within the permissions you’ve approved, and text the customer a confirmation. If the situation falls outside the rules, it should route or escalate it rather than improvise.

The next morning, the dispatcher can see the call, the customer’s details, the issue, and the action taken. The team can review a recording or transcript if that’s part of the agreed setup. The agent shouldn’t promise a response time or price your business hasn’t approved. It should also be clear about what it can and can’t book.

The estimate workflow is just as specific. An estimate follow-up agent could track estimates as they’re sent, then follow up on a schedule set by the business. Messages can be tuned to the trade and job size, with a way for the customer to reply or ask for a person. If a customer declines or books, the agent should stop the sequence and update the record. The aim isn’t to pester every prospect. It’s to make sure a real estimate doesn’t disappear because nobody had time to follow up.

After completed work, a review and reactivation agent could ask a happy customer for a review. It can also contact past customers when a service interval makes sense. That means the business needs a sensible rule for who counts as happy, what service is due, and how to handle a complaint or opt-out. The agent can support your process, but it shouldn’t ask for a public review from a customer whose issue is unresolved.

These are separate workflows with separate risks. A missed-call process needs emergency rules and booking access. Estimate follow-up needs accurate status data and approved wording. Review requests need a customer experience check. Start with the workflow that has the clearest cost and the cleanest source data.

If the mechanics of vehicle stock are part of the same operational drag, automating truck inventory is a related question to assess. It may be a separate investment, rather than something to bundle into a first project.

Estimate payback before choosing a system

You don’t need a complex financial model. You do need to separate recovered revenue from recovered profit and avoid counting the same benefit twice.

For each workflow, write down four things:

  1. Current volume. How many calls, estimates, or customer reactivation opportunities are there in a typical month?
  2. Current outcome. How many are missed, delayed, or left without a next step?
  3. Recoverable value. What portion could realistically change with a consistent process, and what is the gross profit on that work?
  4. Full cost. Include setup, monthly software, integration, staff training, ongoing review, and the time your team spends maintaining the process.

A simple call example uses your own numbers: missed eligible calls per month × the share you expect to book × average gross profit per booked job. Compare that estimated monthly gross profit with the monthly cost of the call workflow. For estimates, use the number of stale estimates you can actually contact and the bookings you can attribute to follow-up. Don’t add revenue from a recovered call to a second calculation if it already appears in your booked-job totals.

Time saved matters too, but value it carefully. If an agent gives a dispatcher an hour back, that hour only becomes a financial benefit if it reduces overtime, avoids another hire, or gives the person capacity for work that contributes to the business. Owner time is important, but don’t enter every freed hour as cash savings.

Then test a conservative case. What if only a small share of missed calls turns into jobs? What if follow-up produces fewer bookings than you expect? What if setup takes longer than expected? If the investment only works under optimistic assumptions, keep measuring before you commit.

Don’t ignore the workflow around the agent. A dispatch system with incomplete schedules, inconsistent job types, or no clear emergency policy will make automated booking harder. The same goes for estimates that aren’t consistently marked as won, lost, or open. Clean up the steps that feed the process before judging the technology.

A short operational review can help narrow this down. Book a 60-min Omni Audit and use the time to identify the workflow, data, and financial assumptions worth testing.

What to check before you choose a system

Ask how the agent handles exceptions before you focus on its demo. Can it recognize a situation that shouldn’t be booked automatically? Can your staff take over without losing the conversation? Can it use your actual dispatch tool, or will someone have to copy details across systems? What happens when the customer gives an incomplete address or calls about an existing job?

For follow-up, ask how it knows an estimate has been accepted, declined, or changed. Confirm who approves message wording and how replies reach the right person. For calls, make sure your team agrees on the difference between an emergency and a scheduled visit. Those rules are operational decisions, not settings to leave to a vendor.

Ask how results will be measured, too. A call workflow should report on calls answered, qualified, booked, and escalated. An estimate workflow should show which estimates received follow-up and what happened next. Agree on a baseline before launch so you can compare outcomes after it has been running.

Finally, plan for a human owner. Someone needs to review exceptions, keep service rules current, and decide what to change when the workflow isn’t producing the expected result. The goal is less repetitive work, not a system nobody understands.

For a broader view of related automation work, you can also review AI customer feedback for trades businesses. Reviews and reactivation can support repeat work, but they should be measured separately from new calls and estimate conversion.

A practical next step

The After-Hours Call Recovery Plan for Trades is a worksheet for mapping what happens when a call comes in outside office hours. Use the downloadable plan to note who answers today, what qualifies as an emergency, how booking works, and when a call needs a person. You can get the worksheet directly before you change your phone process.

For a 10-truck plumbing company, the first good investment is often a narrow workflow with visible leakage, a clear measure, and a safe handoff. That might be after-hours calls, estimate follow-up, or customer reactivation. It doesn’t have to be all three, and it doesn’t have to begin with a large system replacement.

If you want help choosing the first workflow, see Omni for trades businesses, then book a 60-min Omni Audit. Bring a recent call log, a sample of estimates, and a rough view of dispatch time. We’ll use those to assess where the dollars are going and whether a focused automation project can earn its place in the business.