A missed call. A quote that's gone quiet. A customer who's due back and hasn't heard from you. Dispatch is what we're building for businesses like yours: HVAC, plumbing, electrical, roofing, landscaping, cleaning, pest control, and similar trades where the phone and the schedule decide whether a job happens. It will connect to what you already use. We'll confirm exactly how Dispatch connects to whatever you already use before your service goes live. It will follow the rules you set for handling it, so a missed call, a quote gone quiet, or a customer due back doesn't just sit there. We'll say so too: every caller who asks will hear that they're talking with AI.
Think about where the phone, the schedule, the estimates, the customer list and the reviews actually live in your shop. If that's five or six separate places that were never built to hand work to each other, then a call gets answered, an estimate goes out, a job gets booked, and what happens after that depends on someone remembering to do it in between everything else on their desk that day.
Nothing there is broken. If that's how it runs at your shop, there's just no one thing watching all of it at once, so the follow-up is the part that quietly doesn't happen: the estimate that went out Monday and never got a second look, the 6pm call that hits voicemail because the office closed at 5, the customer who was due back for a tune-up in the spring and it's now the fall.
The phone. The schedule. The estimates. The customer list. Dispatch will pull what it needs from each into one place that knows what's going on with every customer, instead of one more app that only knows one thing. We're not built around one calendar or job-board product, and we'll confirm exactly how Dispatch connects to your setup before you go live.
A customer who's due back for a tune-up won't fall between your calendar and your customer list. Dispatch will see both, and it'll know it's time to reach out.
You'll tell Dispatch how you handle things: what happens when a quote goes quiet, what happens when a job cancels, what happens when a customer's due back. It will follow the rules you set, not a guess it made up, and when you change your mind about how something should be handled, you change the rule, not wait on us.
Say you tell it to follow up on a quiet quote after two business days. Two business days after a quote goes out with no answer, Dispatch will follow up, the way you told it to, not a day early and not a week late.
The AI won't just answer questions. It will do the follow-up, book the job, chase the estimate, and ask for the review, and when something falls outside what you've told it to handle on its own, it will bring the exception to a person, with the whole story attached, not a guess.
When a customer replies to a follow-up text, Dispatch will read the reply and answer it. If the reply needs a person, a coverage question, a complaint, a price that isn't in the book, it goes to whoever handles that at your shop, with the full conversation already in front of them.
No new phone number. No changes for your customers. Nothing to install.
Here's what happens to one event, start to finish, once Dispatch is live.
An estimate goes quiet. A job cancels. A customer's due back for a tune-up. A call comes in after you've closed. Any one of these is where it starts.
It will pull together what it already knows about that customer from the systems it's connected to: the estimate, the job history, the last time you talked. We're not built around one calendar or job-board product, and we'll confirm exactly how Dispatch connects to whatever you already use before your service goes live.
You'll tell Dispatch how you want each kind of event handled: follow up on a quiet estimate after two business days, text a customer who's due back, or quote a caller from your price book. It will follow the rule you set, not a guess it made up.
A text. An email. A booking on your schedule. A task handed to the right person. Dispatch will do whichever the rule calls for, and when the customer replies, it will read the reply and act on it.
A coverage question, a price that isn't in the book, a reply that needs judgment, a genuine emergency: anything you haven't told Dispatch how to handle will go straight to whoever handles that at your shop, with the full history already in front of them, not a guess.
Every event will get a record: what happened, what Dispatch did about it, and what came of it. Nothing will happen where you can't see it.
Say it's a Monday, once Dispatch is live. An estimate goes out for a water heater replacement, no answer by Wednesday. Dispatch already knows about that estimate and that customer's history from what it's connected to, so on Wednesday afternoon, the rule you set says follow up. It sends a text asking if they have questions, worded the way you told it to sound. The customer texts back Thursday and says yes, please book it. Dispatch reads that and books the job on your schedule, against the working hours and booking rules you set up. You get a note: estimate followed up, job booked, no action needed from you. If instead the customer had texted back angry about the price, Dispatch would have stopped there and brought it to whoever handles pricing questions at your shop, with the whole thread attached.
A missed call will work the same way, it's just one more kind of event. Say it comes in at 6pm, after the office has closed. Dispatch answers, quotes only from the price book you approve, and books the job on your schedule if there's an opening. If the caller needs something outside what you've set it up to handle, it takes a message and gets it to whoever's on call, immediately.
We want to build this with a small number of Colorado service businesses. Fifteen minutes on how your shop handles these today will shape what we build first.
