A plumber's phone rings at 2:14 PM while he's under a sink with both hands wet. It rings out. The caller — someone with a burst supply line and water spreading across a kitchen floor — does not leave a voicemail. They hang up and dial the next result on Google. By 2:16 PM that job belongs to a competitor, and the plumber never knew the call happened until he checked his log at dinner.
That's the whole problem in one scene. The lead was real, the intent was high, and the only thing that lost it was silence during the two minutes the caller was still deciding. Full disclosure: I work for Ready, and we build the SMS and dialer tooling I'm about to walk through — so read the math with that in mind, but the math is the point.
Why a voicemail is the wrong tool for an inbound miss
Voicemail assumes the caller will wait for you. Inbound service callers don't. When someone calls a plumber, an HVAC company, or a clinic, they usually have an urgent, specific need and a browser tab full of alternatives. Rough industry numbers put the share of missed inbound calls that never leave a voicemail somewhere north of 80% — and the ones who do leave a voicemail are often calling three other places while they wait for your callback.
So the question isn't "how do I return voicemails faster." It's "how do I re-open the conversation before the caller commits to someone else." Three tools compete for that job:
- Manual callback — you notice the miss and dial back yourself
- Missed-call text-back — an automated SMS fires the instant a call goes unanswered
- Auto-dial reconnect — a power dialer queues the missed number and calls it back automatically
They're not mutually exclusive. But they behave very differently inside that 60-second window, so let's price each one honestly.
The three options, side by side
| Approach | Time to first touch | Fires when you're busy? | Feels intrusive? | Cost per recovery attempt |
|---|---|---|---|---|
| Manual callback | 10 min – hours | No — depends on you noticing | Neutral | Your time only |
| Missed-call text-back | 10–60 sec (automated) | Yes | Low — async, they reply when free | ~$0.0245–$0.049 (1–2 segments) |
| Auto-dial reconnect | 30–90 sec (automated) | Yes | Higher — an immediate ring back | ~$0.0375–$0.06/min of talk time |
The manual callback is where most local businesses live by default, and it's the worst of the three for one reason: it depends on a busy person noticing a miss. If you're on a roof, in a crawlspace, or with a patient, you don't notice. The average manual callback for a service business lands 30 minutes to several hours later — long past the window where the lead was still choosing.
The speed-to-lead math nobody wants to hear
The close-rate decay on inbound intent is steep and well documented in sales research: a lead contacted inside the first minute converts at several times the rate of one contacted at 30 minutes, and the curve keeps falling from there. We wrote up the shape of that decay in detail in The 60-Second Window — the short version is that most of your close-rate advantage is spent in the first five minutes and nearly all of it in the first 30.
Put dollars on it. Say a burst-pipe job averages $450, and 20 people call your plumbing shop this week when nobody could pick up.
- Manual callback, ~1 hour later: maybe you reconnect with 4 of 20 and book 2. Revenue: $900.
- Missed-call text-back, ~45 seconds: you reconnect with 12 of 20 (async text is easy to answer) and book 6. Revenue: $2,700.
The delta is $1,800 in one week, and the incremental cost of the text-back is trivial: 20 missed calls × one or two SMS segments each. At Ready's Standard rate of $0.02/segment plus the $0.0045 carrier pass-through, a two-segment recovery text costs about $0.049. Twenty of them is $0.98. You are spending a dollar to recover $1,800 of intent that would otherwise have walked.
Why text-back beats an auto-dial reconnect for the first touch
An auto-dial callback sounds faster and more aggressive, and there are lead sources where dialing first genuinely wins — we broke that down by source in Text-First or Dial-First. But for an inbound miss specifically, the text has three edges:
- The caller just tried to reach you by phone and failed. An immediate ring-back can read as robotic or spammy, especially if it hits while they're already dialing your competitor.
- Text is async. If they're at work, driving, or standing in a flooding kitchen, they can reply "yes come now" in three seconds without a conversation. A call demands they stop and talk.
- A text opens a thread you can keep. The reply lands in your inbox and you can keep working the lead — quote, schedule, confirm — over the same channel.
The strongest pattern isn't text or dial. It's text first, then dial the ones who reply or the high-value sources. That's the exact sequence in our dial-then-text fallback writeup — the auto-text lands in under a minute, and your power dialer queues a callback for the ones showing intent, so a human isn't burning time dialing dead numbers.
What the text-back should actually say
Keep it one segment if you can — 160 GSM-7 characters — so it fires as a single billed message and lands clean. Something like:
"Hi, this is Mike at Rapid Plumbing — sorry we missed your call. Reply here and I'll get someone out today. What's going on?"
That's 118 characters, one segment, $0.0245 all-in. Note there's no emoji — a single emoji drops your per-segment limit from 160 to 70 characters and can silently push a short message into two or three segments. If you're sending these at volume, that matters; if you want the full breakdown on why, reducing SMS costs covers the segment math.
One more thing that's easy to get wrong: this is a transactional message triggered by an inbound call, not a marketing blast. Register it as a transactional/customer-care 10DLC use case, not marketing — registering the wrong use case is a common reason delivery silently drops.
Setting it up
The whole thing is an automation with three moving parts:
- Trigger on missed/unanswered inbound call. In GoHighLevel, that's a workflow trigger; Ready's native GHL integration keeps the inbound call event and the outbound text mapped to the same location, so agencies managing multiple clients keep everything isolated per sub-account. The GHL SMS setup guide walks the connection.
- Send the text-back within your permitted hours. Ready enforces quiet hours by the recipient's local time, so a 2 AM miss doesn't fire a text that violates TCPA windows — it holds until morning.
- Route replies into your unified inbox and queue a dial-back. Replies land in the conversations inbox (and in GHL), and Ready's Power Dialer can auto-queue the high-intent ones for a human callback — voicemail drop, transfer, and whisper included on the paid tiers.
One guardrail before you ship it: put a loop check on the workflow so a single number can't get re-triggered on every callback. A misfired workflow can text one contact 40 times before anyone notices, and that's a fast way to earn a spam complaint.
The practical takeaway
For a local service business losing inbound calls, the ranking is clear: an automated missed-call text-back beats a manual callback because it doesn't depend on you noticing, and it beats an immediate auto-dial for the first touch because it's async and reads less like a robot. The auto-dial earns its place as the second touch — reserved for the leads who reply and the sources worth a human's time.
The economics aren't close. Recovering a $450 job for under a nickel of SMS is the kind of ROI you don't have to squint at. The only real work is wiring the trigger, keeping the message to one segment, and registering the right 10DLC use case so it actually delivers.
If you want to test it, Ready gives you 2,500 free credits and no credit card to start — enough to run a month of missed-call recovery and watch what comes back. See the product and pricing, or sign up and build the workflow this afternoon.