On this page
The text fires. The homeowner replies.
Now what?
That’s the question most shops haven’t answered before they set up a missed-call text-back. The text does its job. The homeowner is on the line, interested, window open. But someone has to pick it up on your end. If that handoff isn’t wired, the lead disappears into an SMS thread nobody checks.
The moment after the text lands
Picture how this plays out in a real shop on a Tuesday at 7 PM.
Your tech is on the last job of the day. Your dispatcher wrapped up at 5. You’re at home. The missed-call text fires automatically, which is the point. The homeowner gets it, types back “yeah we need someone to look at our furnace, it stopped working this afternoon.”
That reply is sitting in a Twilio number. Or a Google Voice inbox. Or an app on your phone that you’re not looking at because you’re making dinner.
Meanwhile, the homeowner is not waiting. They already called two other companies before they called you. One of those companies is probably still in their recent calls. If they don’t hear back in the next few minutes, they try again.
As Jobber’s research shows, 70% of homeowners take the first quote they get. Being first matters more than being cheapest. Firing the automated text buys you the window. But the window closes fast.
The 5-minute gap
Speed-to-lead is a well-documented problem in home services. The threshold that shows up consistently across operator research: five minutes. Under five, you’re in the running. Beyond five, you’re calling someone back who’s already mid-conversation with whoever picked up next.
HVAC owners describe this directly. “By the time I call back, they’ve already booked with someone else.” “We’ve lost jobs because the lead sat in email for a day.”
That second one is the relevant version here. Not email, but the SMS thread. The lead sits in the text thread, and by the time it hits your radar, the job is gone.
The automated text is not the finish line. It’s the starting pistol. What matters is what happens between the reply and the moment someone on your team claims the lead.
What a wired system looks like
A wired system doesn’t stop at the text. It closes the loop into your field-service software.
When the homeowner replies to the text-back, a connected system does three things. It detects the reply. It creates a contact or a job in your FSM, whether that’s Jobber, Housecall Pro, or Workiz. And it surfaces that lead to whoever is dispatching, in the tool they’re already looking at, not in a separate app.
The Jobber API, Housecall Pro, and the Workiz API all support this. An inbound text reply triggers a webhook (a notification that fires automatically when something happens in one app, telling another app to act). The webhook creates a contact record. The dispatcher sees the flag on their board. The lead is claimed before the homeowner dials the next number.
That’s the integration play. The text opens the door. The FSM integration brings the lead inside.
Where it breaks down
The places this falls apart follow a predictable pattern.
Manual steps in the middle. Some setups fire the text automatically but then expect someone to manually log the reply in the CRM. If nobody does that step in real time, the lead sits in limbo. “I’m slammed, I know I should follow up but I can’t” is how most owners describe this. Correct answer, wrong structure. The lead shouldn’t need a person to move it from one place to another.
A CRM nobody actually opens. Some shops have a CRM because an agency told them to get one. The FSM techs use is Jobber. The CRM is a separate tab that gets opened on a good week. If the integration creates a record in something your dispatcher doesn’t look at, the record doesn’t help.
The FSM and the text-back aren’t talking. This is the most common version. The text-back fires from one system, the jobs live in another, and there’s no connection between them. Everything is working individually. Nothing is working together. The homeowner replied. The lead is real. It just never made it to the board.
The system is only as fast as its slowest step. If that step is a human remembering to transfer a lead between apps, the 5-minute window is already gone.
What to check in your own shop
Before adding more automation, it’s worth mapping what you already have.
Where does a lead from a missed call actually land right now? Not where it’s supposed to land. Where does it actually end up when someone calls at 8 PM?
Who sees it, and when? Is that person checking whatever app the lead lands in at 8 PM on a Tuesday?
If the answer is “probably not until tomorrow morning,” that’s the gap. The missed-call text is already a step forward. But the gap between the reply and the dispatcher’s board is where the job gets lost.
Fixing that gap is a different project than setting up the text-back. It requires knowing which FSM you’re using, whether it has an API or webhook support, and what the reply-to-record flow looks like. It’s not complicated, but it does need to be deliberately wired.
If you want to understand how the text-back side works before connecting it to anything else, start with the missed-calls page. That’s the foundation the integration builds on.