Industry
Home Services & The Trades: what to automate, what to keep human.
The money in trades AI is going to the front office: an agent that answers, books, follows up, and dispatches. The booking and dispatch half is the easy, visible half. The expensive half is the call nobody answered, after hours, mid-job, second line ringing, because right now no person owns what happens to it. Drop an AI on top of that and it books the calls it catches while the calls it misses still vanish, except now nobody on your team is watching the phone because 'the AI handles it.' The win isn't a faster dispatch. It's a named owner and a number for the calls that never reached a human at all: the ones a $30,000 install walks in on.
The argument
Trades AI should stop the $30K install from walking out the door because the phone rang at 7:43 on a Tuesday. Front-office speed on the easy calls is real revenue. So is having a named owner and a measured queue for the calls that did not reach a human, the ones the demo never shows. Book the catches faster and put a name on the misses, and the math works.
The trades-AI money is real. So is the half nobody is watching.
Front-office AI in home services is a real revenue lever and the market knows it: Avoca raised over $125M at a $1B valuation in April 2026 to put AI on the phones for HVAC, plumbing, roofing, and electrical shops, and it is running for 800+ contractors. The demo earns the money. The AI answers every call, books the job, follows up on the estimate, and pushes it to dispatch with no CSR. The stakes are real too: as Avoca's own framing puts it, a restaurant that misses a call loses a $30 order; a home-services business that misses one can lose a $30,000 or $40,000 HVAC install.
Here is the part of the math the demo skips. Two different calls get bundled into one product. The call that reaches the AI and gets booked is the demo. The call that never reaches anything, the second line during a heat wave, the 9pm no-heat call, the one that rang four times while the AI was mid-conversation with someone else and rolled to a voicemail no one has owned for years, is the bigger leak by dollar value. Front-office AI sold without an owner for that second call gives you a busier dashboard and a quieter monthly leak.
So a serious owner's question is not 'can it book the call.' It is 'what happens to the calls it does not, and who sees them before the install walks down the street to the next shop.'
Where to deploy trades AI first
Front-office AI is real, and the lower-risk pieces should move first because the revenue is right there. Missed-call text-back so an unanswered call gets an immediate 'we saw you called, what is the address' instead of dying in voicemail. After-hours capture that takes the no-heat call at 11pm, qualifies the emergency, and routes it to whoever is actually on call. Estimate and review follow-up the AI drafts and a human sends. Appointment reminders that cut no-shows. None of these dispatch a crew or quietly close the loop on a job with no human ever seeing it, and each one converts revenue you were already losing.
These earn AI its place in booking and dispatch later, once a named owner on the dead-call list and a callback clock actually exist and the missed-call number is moving. Build the workflows where the gain is visible and the miss is cheap first, then earn the one where a miss is a five-figure job that left without a trace.
Why a booking bot scoring 80% can still leak your month
Trades-AI features look like one bundle: call answering, booking, estimate follow-up, dispatch, review requests, reminders. They do not fail the same way. A late review request costs a Google star. A clumsy reminder annoys a customer. A call routed slightly wrong gets fixed at the next dispatch huddle. A call that no human and no AI ever caught is a job that left and told you nothing, and that one has a five-figure ticket on it.
That asymmetry is why order matters. ServiceTitan's 2026 Residential State of the Trades Report (1,000 contractors, Thrive Analytics, April 2026) found 74% of contractors see AI as key to efficiency and 73% think starting early is an advantage, but only about a quarter are actually using it and more than half say they do not know where to start. The same report shows barely half of contractors respond to a lead within the first hour. The leak is already there, in the dark, before any AI is installed. The job of the AI is to put a number and an owner on it, not paper over it with a booked-call dashboard that looks busy.
Practically: before the AI books a job, a named person owns the dead-call list and a clock runs on it (every missed call gets a human callback inside a defined window, tracked, with a reason logged when it does not convert). AI handles volume. A person owns the ones that fell through, because an AI graded on calls answered will never surface the ones it did not.
The trades AI revenue plan, and the one list nobody else is reading (use this one)
This is the artifact. Not 'be responsive': the plan an owner hands a CSR lead or office manager before any front-office AI goes live, so the calls AI books show up in revenue and the calls it does not still show up to a person. The day is not closed until each line is true:
- Ownership of the dead-call list. AI answers and books; a named person owns every call that reached neither a human nor a completed booking, and works it.
- The emergency triage decision. Whether a no-heat or no-water call is a same-night dispatch is a judgment call with safety and liability in it: AI captures and flags, a human decides.
- Who gets dispatched to what. Crew assignment trades on skill, location, customer history, and what's actually on the truck; AI can suggest, a dispatcher owns it.
- Pricing quoted on the phone. Ballpark numbers and 'it depends' are a human conversation; an AI committing a price sight-unseen is a callback and a fight later.
- The recovery call after a bad job or a complaint. That conversation is the relationship; it does not get automated.
How you'll know it actually worked
Measure trades AI by revenue, both sides. Revenue captured: booked jobs and revenue from the calls AI handled. Revenue recovered: of the inbound that did not reach a live human or a completed AI booking, the share that got a human callback inside your window and the share that turned into a job. If booked revenue rises and dead-call recovery holds or climbs, it worked. If booked jobs go up and the dead-call list quietly grows because nobody owns it anymore now that 'the AI handles the phones,' the AI did not fix the leak. It hid it, and you will find it in slow weeks and a soft month, not on the demo.
How ADA helps home services & the trades
Service paths
AI Implementation for Home Services & Trades
Owner-led trades businesses ($1M–$25M) in HVAC, plumbing, electrical, and roofing who've seen the AI-phone-agent demos and want the missed-call leak actually closed and owned, not a booking dashboard that looks busy.
View service ➞Customer Service AI for Home Services & Trades
Trades businesses drowning in inbound, overflow during peak, after-hours emergencies, second-line calls during a heat wave, that want the routine volume handled without the five-figure emergency call vanishing into an unwatched voicemail.
View service ➞Related workflows
Frequently asked
Should a trades business use an AI phone agent?
Yes, but assign an owner for the calls it misses before you turn on the parts that book and dispatch. AI call answering is the highest-value front-office use case and also the one that can hide your worst losses, because a missed call that no human is watching for now disappears silently. Start with missed-call text-back and after-hours capture, stand up a named dead-call owner with a callback clock, then let AI book and dispatch.
What should trades AI never do on its own?
Own the dead-call list, make the emergency same-night-dispatch call, assign a crew to a job, commit a price over the phone sight-unseen, or run the recovery conversation after a bad job. It captures and drafts and books the routine volume; the judgment and the calls that fell through stay with a person.
What's the first AI workflow a contractor should actually build?
Missed-call text-back or after-hours capture, where a miss is immediately visible and cheap to recover, not the booking-and-dispatch flow where a miss vanishes. It builds the recovery habit and the dead-call number that the booking workflow will later be measured against.
How do we measure whether the AI phone system worked?
Dead-call recovery rate: of inbound calls that reached neither a human nor a completed AI booking, the share that got a human callback inside your window and the share that converted, not calls answered or jobs booked. Booked revenue up while the dead-call list quietly grows is a hidden leak, and it shows up in a soft month, not the demo.
Sources
- ServiceTitan: 2026 Residential State of the Trades Report (1,000 residential contractors, surveyed by Thrive Analytics, April 2026): 74% see AI as key to efficiency, 73% say starting early is an advantage, ~25% currently using AI, >50% unsure where to start, just over half respond to a lead within the first hour
- Fortune: Avoca raises $125M+ at a $1B valuation for trades front-office AI (April 27, 2026); 800+ contractors; the restaurant-vs-HVAC missed-call stakes framing
- ServiceTitan: AI for home service (industry overview)
Next step
