Missed-call text-back: the first automation every service business should run.

You're a plumber. You're under a house in Keller with a pipe wrench in one hand, and your phone buzzes in your pocket. You can't answer it. You weren't going to answer it. And the person calling — a homeowner with water coming through their ceiling — isn't going to leave a voicemail. They're going to hang up and call the next plumber on Google.

That call was worth somewhere between $250 and $4,000. It just walked.

This is the single most fixable revenue leak in a service business, and the fix costs less than a tank of gas per month. It's called missed-call text-back, and if you only ever set up one automation, make it this one.

Why voicemail is where jobs go to die

Nobody has hard numbers for your business except your own phone log, so pull it up. Count the missed calls from last month. Now be honest about how many of those people left a voicemail. For most trades and home-service shops we talk to, it's a small minority — and the callers who didn't leave one didn't wait around. They had a problem, a search results page full of your competitors, and a thumb.

The pattern is simple: urgent problem, first responder wins. A caller with a dead AC in a Texas July isn't loyal to anyone yet. They're loyal to whoever answers. If you can't answer, the next best thing — by a wide margin — is responding by text within seconds of the missed call.

Texts get read. That's the whole trick. A voicemail asks the customer to do work (call back, wait on hold, maybe get voicemail again). A text does the work for them: it opens a conversation they can answer from the parking lot, the office, or the couch.

The exact flow, start to finish

Missed-call text-back is not complicated. Here's the entire automation:

1. A call comes in and goes unanswered — you're on a job, it's after hours, whatever.
2. The system detects the missed call within a few seconds.
3. It sends an automatic text from your business number: a short, human-sounding "sorry we missed you — what's going on?"
4. The customer replies by text describing their problem.
5. You (or a simple AI assistant) reply when you can — even 20 minutes later, the conversation is alive instead of dead. You've captured the lead before they finished dialing the next company.

Optional upgrades once the basic loop works:

• Auto-ask the qualifying questions: address, photo of the problem, "is this an emergency or can it wait until tomorrow?"
• After-hours booking link: let them grab a slot on your calendar without anyone touching a phone.
• AI reply layer: a small language-model agent that handles the first two or three exchanges (gathering details, quoting your standard service-call fee) and hands off to a human for anything real.

Start with step 3 alone. That one text recovers most of the value.

What it actually costs

Real tools, real prices (as of late 2025 — check current pricing before you buy):

• DIY with Twilio: roughly $1.15/month for a phone number plus about a penny per text. You need someone technical to wire up the missed-call webhook — an afternoon of work for a developer. Cheapest to run, most work to build.
• OpenPhone: business phone system from about $15/user/month with built-in auto-replies to missed calls. The easiest "good enough" answer for a one- or two-person shop.
• GoHighLevel: around $97/month, missed-call text-back is a flagship feature, plus pipelines, review requests, and booking. Overkill if this is all you want; solid if you'll grow into it.
• Podium: several hundred dollars a month. Polished, salesy, aimed at businesses already spending real money on marketing.

Now run the illustrative math for a typical Keller plumber: average job $350, and suppose the text-back recovers just two callers a month who would otherwise have hired someone else. That's $700/month recovered against a $15–97/month tool. Even the pessimistic version of this math clears 5–10x return, which is why we call it the cheapest revenue-recovery automation that exists.

Writing the text so it sounds like you, not a bot

This is where most setups fail. The default templates read like a bank's hold message, and customers smell it instantly. Rules:

• First person, owner's voice. "Hey, this is Mike at Reyes Plumbing — sorry I missed you, I'm on a job. What's going on?" Not "Thank you for contacting us. Your call is important."
• One question, not a form. Ask "what's going on?" and let them talk. Don't open with a request for name, address, and preferred appointment window.
• Admit it's fast for a reason. If you want, be transparent: "This is an auto-text so you're not stuck with voicemail — but a real person reads every reply."
• Match how you actually talk. If you'd never write "we apologize for the inconvenience," don't let your automation write it either.
• Set the callback expectation. "I'll call you back within the hour" only if that's true. If it's 9pm, say "I'll get back to you first thing tomorrow — if it's an emergency, reply URGENT."

Bad: "We are currently unavailable. Please visit our website to schedule an appointment."

Good: "Hey, it's Nate at West Fork — sorry we missed your call, we're with a customer. Text me what you need and I'll get right back to you."

How West Fork approaches this

We build missed-call text-back as the first stop in a client's automation roadmap because it proves ROI in weeks, not quarters. We wire it to your existing business number, write the auto-texts in your voice (we'll interview you and steal your actual phrasing), and only add an AI reply layer once the basic loop is earning. No platform lock-in — if a $15 tool does the job, that's what we recommend.