Call a plumber at 6:40pm and there's a decent chance nobody picks up. Call a busy salon on a Saturday and you get the same silence — they're mid-appointment, not ignoring you. Across most local service businesses, somewhere around a fifth of inbound calls go unanswered. That's the round number I've seen quoted for years, and it lines up with what actual owners tell me: overflow during the day, dead air after hours.
Here's the part that stings. A caller who doesn't reach you doesn't leave a voicemail and wait. They tap the next result. Your missed call becomes your competitor's booked job, and you never even knew it happened.
Full disclosure: I work for Ready, an SMS platform. So I have a horse in this race. But the missed-call text-back is one of the few automations where the math is so lopsided it barely matters which tool you use — as long as you're sending something the second a call drops. Let me show you the setup and the numbers.
What a missed-call text-back actually does
The mechanic is simple. A call comes in, rings out, and goes unanswered — after hours, or because everyone's busy. Instead of leaving the caller in silence, an automation fires an SMS within a few seconds:
"Hi, this is Mike's Plumbing — sorry we missed your call! We're with a customer right now. Text us what you need and we'll get right back to you. Reply STOP to opt out."
Now the caller has a thread open. They can tell you the water heater's leaking without dialing anyone else. You've converted a dead call into a live text conversation — and text conversations are far easier to answer at your own pace than a voicemail you have to call back.
The whole thing runs off two ingredients: a trigger on the missed call, and a place for the reply to land. In Ready, the reply lands in the unified inbox (and inside GoHighLevel if you've connected it), so whoever's free can pick up the thread. No app-switching, no "who's got the phone."
The consent question — because you can't skip it
An unprompted marketing text to a cold number is a problem. A reply to someone who just called your business is a different animal, and it's worth understanding the distinction.
When someone dials your number, that's an inbound contact they initiated. Responding to that specific inquiry is a reasonable business reply, not a broadcast. But two things keep you clean:
- Keep the first text transactional. Answer the call they made — don't stuff a coupon in there. "Sorry we missed you, text us what you need" is a reply. "20% off drain cleaning this week!!" is marketing, and that changes the consent picture.
- Include the opt-out and honor it instantly. Ready's automatic STOP handling catches any inbound STOP or UNSUBSCRIBE and propagates the opt-out so that contact won't get messaged again across your campaigns. That's the audit trail you want.
If you do want to move that person onto a promo list later, get real opt-in for that separately. The text-back reply and your marketing list are two different consents. Don't blur them.
And the boring-but-load-bearing prerequisite: you need registered 10DLC for this traffic to land. Unregistered application-to-person SMS gets carrier-filtered, which means your clever text-back never arrives. Ready handles brand and campaign registration in-app — roughly ~$10/mo per brand and ~$20/mo per campaign in carrier fees, approval usually 1–3 days. Do this before you turn the automation on, not after you notice replies aren't sending.
The ROI math, worked out
Let's use a mid-range service business — an HVAC shop, a mobile mechanic, a pest control outfit. Assume an average job value of $400 (round number, adjust to yours).
Say you take 500 inbound calls a month. At a ~22% miss rate, that's 110 missed calls. Not all of them are new jobs — some are existing customers, some are sales calls, some are wrong numbers. Call it half that are genuine potential work: 55 real opportunities you're currently dropping.
Now the recovery rate. Text-back conversion isn't magic, and I won't pretend it is. But recovering even 20–30% of an otherwise-lost opportunity is realistic when you're the only one who bothered to text back. Take the conservative end — 20% of 55 = 11 recovered conversations. Not all of those book. Say half book a job: about 5–6 jobs/month you weren't getting.
At $400 each, that's ~$2,200–$2,400 in monthly revenue from work that was walking out the door.
What it costs you to send
Here's the cost side, on Ready Standard pricing ($0.02/segment + $0.0045 carrier pass-through = $0.0245 all-in):
| Item | Volume | Cost |
|---|---|---|
| Text-back to 110 missed calls | 110 × 1 segment | $2.70 |
| Reply thread (say 4 more segments each on the ~55 real ones) | 220 segments | $5.39 |
| 10DLC brand + campaign carrier fees | monthly | ~$30.00 |
| Total monthly | ~$38 |
So you're spending roughly $38 a month to recover on the order of $2,200. Even if I'm off by half on the recovery rate — even if you only book 2–3 jobs — the automation still returns more than 20x its cost. This is one of the rare cases where the worked math genuinely embarrasses the objection.
Want to run it against your own miss rate and job value? The full missed-call setup post goes deeper on the trigger config.
Text-back vs. text-then-dial
The pure text-back is the floor. If you have someone who can call back, pairing the auto-text with a fast dial-back closes more — the text buys you the caller's attention, the call closes the job while they still have their problem front of mind. There's a real timing window here, and it's shorter than most owners assume; the dial-back window breakdown covers it, and Ready's Power Dialer has speed-to-lead auto-dial that can fire on a fresh contact.
For after-hours calls, though, the text-back alone carries the load — nobody's dialing back at 9pm, but a caller will happily text "leaking water heater, can someone come tomorrow?" and check their phone in the morning for your reply.
Setup, start to finish
If you're on GoHighLevel or using Ready standalone, the build is short:
- Register 10DLC in-app. Start this first — it's the 1–3 day gate.
- Connect your number and inbox. For GHL users, the OAuth integration two-way-syncs messages per sub-account, so replies show up where your team already works. The GHL SMS setup guide walks the connection.
- Build the trigger. Fire an SMS on missed/unanswered call. Keep the copy transactional and add the STOP line.
- Add a guardrail. Make sure the automation fires once per missed call, not on a loop. Misconfigured workflows can text someone repeatedly — the duplicate-send guardrail post shows the audit.
- Assign the inbox. Decide who watches replies during and after hours. A recovered lead that sits unread for six hours is a lead you re-lost.
Where it's not worth it
Honesty check: if you answer basically every call — a solo operator who lives on the phone and never misses one — the text-back has little to catch. And if your average job is genuinely tiny (a $12 transaction), the recovery revenue may not justify the setup effort, though at ~$38/mo the bar is low. This automation shines when you have real overflow, real after-hours demand, and a job value worth chasing. Most service businesses clear that bar easily.
The takeaway
A missed call at a local business isn't neutral — it's a warm lead actively shopping, and silence is the one response that guarantees you lose them. A transactional text-back, sent in seconds, keeps the conversation on your side of the fence. The setup is an afternoon, the running cost is roughly a lunch, and the recovered work is measured in hundreds of dollars a month at plausible rates.
Start with 2,500 free credits, no card required, and turn the automation on for a single month. Watch the inbox. If even a couple of "sorry we missed you" texts turn into booked jobs, the decision makes itself — you can sign up here and see it against your own call volume.