Why jobs slip through when you're busy
The problem isn't that you don't want to respond. It's that responding requires stopping what you're doing, and trades work doesn't pause when the phone rings. You're under a sink, on a roof, or in the middle of a repair that needs your full attention. By the time you're free to call back, the customer has already booked someone else. Or they haven't, but two or three more hours have passed and you're now competing with whoever responded first.
The second problem is volume. During busy season, inquiries stack up. The plumbing company that checks email twice a day is going to lose to the one that has a system for acknowledging every inquiry within minutes.
What AI intake actually does
At its core, it's a response sequence that fires automatically when you miss a call or receive a form submission. The response doesn't try to close the job or quote a price. It acknowledges the inquiry, confirms you're real and available, and asks one simple question to gather more context about the job.
Something like: "Hi, this is [Business]. Got your message about the plumbing issue. To make sure we bring the right parts, can you tell me roughly where the problem is and whether it started today or has been building?"
That's it. The customer replies. You now have context for when you do call back, and the customer feels like someone is actually paying attention. That's the whole workflow. It's not complicated. It's just consistent.
Form Submitted
in 30 Sec
with Details
to Your Queue
with Context
Workflow 1: missed call text-back
This is the first workflow worth building for most trades businesses.
Trigger: a call comes in to your business line and isn't answered within three rings (you define the threshold).
Action: an automated text goes out within 30 seconds. The message is short, reads like a real person wrote it, and includes a link to book a callback time or simply reply with details. The customer gets acknowledged immediately. You get a notification when they reply, along with whatever context they provided.
What this is not: it's not a chatbot that tries to have a full conversation. It's one message that opens a thread. You take it from there when you're free.
Workflow 2: inquiry triage and routing
For businesses that get inquiries through a website form or email, a second workflow handles the sorting. When a new inquiry comes in, the AI reads the message, categorizes it by job type (emergency, scheduled maintenance, estimate request, commercial, etc.), and routes it appropriately. If you have more than one person handling different types of work, it routes to the right queue. If it's a single-person shop, it adds a priority tag and moves the urgent ones to the top.
The useful part isn't the categorization. It's the automatic acknowledgment that goes to the customer while the routing happens: "Got your inquiry. [Business] will follow up within [timeframe]. For emergencies, reply here or call [number]."
That message alone stops most customers from moving on to the next result. This is a similar follow-up problem I cover in this post for property managers, where the same principle applies across a different type of operation.
What AI intake can't do
It can't quote the job. Quoting a trade job requires looking at the situation, asking follow-up questions only an experienced technician can think to ask, and applying knowledge of local material costs and labor time. Any workflow that claims to quote jobs automatically is going to produce numbers that embarrass you.
The intake workflow's job is to get you the information you need to quote accurately and quickly. That's different. It buys you time by making the customer feel handled, while getting you the context to do the actual job assessment right.
Not sure this fits your operation? The 2-minute quiz on this site asks a few questions about your business type and points you to the three workflows worth starting with for a trades business.
Take the quizWhat you need to set this up
- A business phone line that can be configured to trigger an automation on missed calls. Most VoIP systems (RingCentral, OpenPhone, Google Voice Business) support this natively. Traditional landlines need a forwarding workaround.
- A way to receive the customer's reply. Usually a text thread or an email, depending on how your business communicates.
- A short message template written in your voice. You provide it; I write the prompts around it.
- A clear definition of what counts as an "emergency" vs. a "scheduled" job, so the routing logic works right.
One workflow takes about a week to set up. Cost: $750 for one, $1,500 for three. If one missed-callback-turned-job covers the cost, it pays for itself quickly. For most trades businesses with any volume, that happens in the first month.
Common mistakes
Trying to automate the quote
The intake workflow acknowledges the inquiry and gathers context. That's its job. If you try to extend it to pricing, you'll either under-quote and lose money, or over-quote and lose the job. Keep the scope narrow.
Using a generic template
"Your message has been received. We will contact you within 24 hours." reads as a form response and signals to the customer that they're in a queue. Write the auto-response in your actual voice. Use your business name, a specific reference to what they inquired about if possible, and a question that only makes sense for your type of work.
Not testing it before it goes live
Send yourself a test inquiry. Then send one to a trusted customer and ask if it reads like you wrote it. Fix anything that sounds off before real customers see it. The first impression from the auto-response is often the first impression of your business.