AI dispatch software reads an incoming job request, checks which technicians are free, qualified, and closest to the job site, and assigns the work automatically instead of waiting for a human dispatcher to juggle a whiteboard and six phone lines. The best systems also factor in traffic, parts on the truck, and job urgency. Done right, it means fewer idle techs, fewer double-bookings, and jobs getting assigned in seconds instead of minutes.

I build automation systems for service businesses for a living, plumbing included. This post is about what AI dispatch actually does, what it’s worth to a plumbing company, and where the real costs are.

Why do plumbing companies need AI dispatch now?

There aren’t enough plumbers. The U.S. has about 504,500 employed plumbers, pipefitters, and steamfitters right now, with roughly 44,000 job openings projected every year through 2034 (BLS (O*NET)). That’s not a one-year problem. That’s a structural gap that isn’t closing anytime soon.

On top of that, 27% of small business owners nationally currently have unfilled openings for skilled workers (NFIB). If you run a plumbing company, you’ve probably felt this directly: fewer qualified applicants, longer time to fill a tech slot, and more pressure on the techs you already have.

When you can’t hire your way out of a labor shortage, you have to get more out of the people you’ve got. That’s what dispatch efficiency is really about. It’s not a nice-to-have feature. It’s how you survive a market where the workforce isn’t growing fast enough to meet demand.

What does AI dispatch actually do, mechanically?

Strip away the marketing language and AI dispatch is doing a few concrete things:

  • Reading the incoming request (phone call transcript, web form, text) and pulling out the job type, address, and urgency
  • Cross-referencing which techs are available, where they are right now, and what skills or certifications the job requires
  • Scoring the best match based on distance, skill fit, and schedule gaps
  • Sending the assignment to the tech’s phone and updating the office dashboard in real time
  • Flagging exceptions (a tech running late, a job that needs two people, an emergency call that should jump the queue) for a human to handle

None of this replaces your office staff. It replaces the manual matching work that eats up their day. A dispatcher spending 20 minutes figuring out who’s closest to a burst pipe in the north side of town is 20 minutes they’re not spending on customer calls, quoting, or follow-up.

How much more can one dispatcher handle?

This is the number that matters most if you’re running a small office with one or two dispatchers. ServiceTitan’s AI-powered Dispatch Pro has been shown to double the number of jobs a single dispatcher can manage (ServiceTitan).

Think about what that means in plain terms. If your current dispatcher is maxed out running 40 jobs a day, that’s not a hiring problem you solve by adding another body at $45,000 to $55,000 a year plus benefits. It’s a tooling problem. The job isn’t too big for one person. The manual process is too slow for one person.

Does AI dispatch fix missed calls too?

Dispatch and call handling are tangled together more than people think. If your office can’t answer the phone during a rush, you don’t have jobs to dispatch in the first place.

Bonney Plumbing, Electrical, Heating and Air cut missed calls by 60% after adopting ServiceTitan’s AI-powered Contact Center Pro (ServiceTitan). And for the calls that do slip through, ServiceTitan’s AI-driven lead recovery tool converts over a third of previously unconverted calls into booked jobs, specifically 37% (ServiceTitan).

That second number is the one I’d pay attention to if you’re already running some kind of answering service or voicemail. Every missed call you currently write off as lost isn’t actually lost. A decent chunk of those callers will book if someone (or something) follows up fast. That’s recoverable revenue sitting in your call logs right now.

What’s the actual return on this stuff?

Companies that adopt ServiceTitan’s platform, including its AI dispatch tools, see average revenue grow 21% within their first two years (ServiceTitan).

That’s a platform-wide number, not purely a dispatch number, so don’t treat it as a guarantee tied to one feature. But it tells you the direction things move when a plumbing company stops running dispatch off a whiteboard and a group text. More jobs get touched, fewer get dropped, and techs spend more of their day actually turning wrenches instead of sitting in traffic because the closest available guy wasn’t the one who got sent.

What does it cost to build this for a plumbing company?

Here’s where I’ll be direct instead of vague. Big platforms like ServiceTitan bundle dispatch AI into a broader field service management suite. That’s a real option, and it works, as the numbers above show. But it’s a full platform commitment, and you’re renting their infrastructure for as long as you’re a customer.

At Solas AI, I build the same kind of logic (matching jobs to techs by location, skill, and urgency, plus the missed-call recovery layer) as a custom system that runs on infrastructure you own. No monthly platform tax forever, no rebuilding from scratch if you ever want to leave. My retainers run $497 a month for the starter tier, $1,497 for Professional, and $2,497 for Premium, with a one-time setup fee of $1,497. If you want to test the water first, there’s a 30-day pilot at $497.

The difference isn’t that my version is cheaper than ServiceTitan in every case. For a 40-truck company, ServiceTitan’s scale probably makes sense. For a 3 to 10 truck plumbing company that doesn’t want to pay platform pricing forever and wants a system they actually own, a custom build closes most of the same gap at a fraction of the long-term cost, and it keeps running even if you and I stop working together.

Is ServiceTitan the only real option?

No. It’s the biggest name and it has the case studies to prove its tools work, which is why I cited them throughout this post. But it’s built for companies ready to run their whole operation inside one ecosystem. If you’re smaller, or you’ve been burned by vendor lock-in before, a custom-built dispatch and call-recovery system does the core job (match techs to jobs fast, stop missed calls from bleeding revenue) without tying your business to someone else’s platform forever.

I’m security-first by background (CISSP, CISM), which matters more than people realize once you’re routing customer addresses, phone numbers, and job history through an automated system. That data needs to live somewhere you control, with access locked down properly, not scattered across three SaaS tools with their own breach histories.

What should you actually do next?

Look at your own numbers first. How many calls go unanswered during a rush? How long does it take your dispatcher to assign a job right now? How many techs are sitting idle because the system matched them wrong? Those answers tell you whether this is worth fixing yet.

If you want to talk through what a dispatch and call-recovery system would look like for your specific operation, book a free call. No pitch deck, just a straight conversation about where the gaps are and whether it’s worth fixing.