Here's the uncomfortable truth about speed-to-lead: most of your fast dials don't get answered. You can hit a fresh inbound lead in under 60 seconds and still land in voicemail, because the person filled out a form on their phone and then set it face-down to keep doing whatever they were doing. The dial being fast doesn't mean the pickup happens. What you do in the 90 seconds after that voicemail is where the connect actually gets recovered.
Full disclosure: I work for ReadySMS, and we build both the power dialer and the SMS side of this, so I have skin in the game. But the cadence I'm about to describe doesn't require our stack to work — it requires you to stop treating the no-answer as a dead end.
Why the call alone leaves connects on the table
An unanswered dial gives the lead exactly two things: a missed call from a number they don't recognize, and maybe a voicemail they may or may not play. Neither is easy to act on. They can't tap a voicemail to reply. They probably won't call back a random number.
A text, by contrast, is:
- Silent-friendly. They can read it in a meeting without picking up.
- Actionable. It carries a name, a reason, and a reply thread they can tap.
- Persistent. It sits in their inbox until they deal with it. A missed call notification gets swiped away in seconds.
Rough industry pattern (frame it as an approximation, not a hard stat): opted-in and expected SMS often see reply rates in the 30–50% range, while cold callbacks from a voicemail sit in the low single digits. When you stack an immediate text on top of the voicemail drop, you're giving the lead the channel they're most likely to actually use.
If you want the underlying math on why speed matters at all before we get to the fallback, the 60-second window piece covers what happens to close rates as a lead ages 5, 30, and 60 minutes.
The cadence, timed to the second
The whole point is that the text lands while the missed-call notification is still on their screen. If you wait ten minutes, the two events feel disconnected. Land the text inside ~90 seconds and they connect: "Oh, that missed call was this."
Here's the sequence for a fresh inbound lead:
| Time | Action | Channel |
|---|---|---|
| 0:00 | Lead form submits | — |
| 0:00–0:45 | Auto-dial fires (speed-to-lead) | Voice |
| ~0:30 | Ring-out, no answer | Voice |
| ~0:35 | Voicemail drop — pre-recorded, 12–18 sec | Voice |
| 0:60–0:90 | Text fallback fires | SMS |
| 5:00 | If no reply, second dial attempt | Voice |
| Next business hour | Third touch, SMS or dial | Either |
The voicemail drop matters here for a boring but real reason: it saves the rep from sitting through the ring-and-recording on every no-answer. On ReadySMS's Team dialer, speed-to-lead auto-dial fires on the new lead and voicemail drop lets the rep hang a pre-recorded message and move to the next record instantly. Across a queue of 40 leads, that's the difference between a rep who's dialing and a rep who's waiting to leave the same voicemail 25 times.
One legal note before you record that drop: voicemail drop is not the same as ringless voicemail. Direct-to-voicemail with no ring has drawn TCPA suits; a normal dial that rings and then drops a message on no-answer is the safer construction. We wrote up the exact technical line here — read it before you build the flow.
The voicemail script and the text have to reference each other
The two touches only compound if they're obviously the same person. Mismatched name or tone and you've just made two strangers instead of one warm one.
Voicemail drop (~15 seconds):
"Hey, it's Marcus from Northgate — I just got your request about the roof estimate and wanted to grab you while it's fresh. I'm going to shoot you a text right now so you've got my number. Reply whenever's good."
SMS fallback, landing ~60 seconds later:
Hi {first_name}, Marcus here from Northgate — just left you a quick voicemail about your roof estimate. Easiest to text: what's a good window to call you today? Reply STOP to opt out.
That's 138 characters, single GSM-7 segment, one billed segment. On the ReadySMS Starter tier that's $0.0155 + $0.0045 carrier = $0.02 to send. If you're recovering even a fraction of no-answer leads that would otherwise go cold, the ROI conversation is over before it starts. See the pricing tiers if you want to run your own volume against it.
A few copy rules that actually move the reply rate:
- Name the reason ("your roof estimate"), not just "following up." Vague texts read like spam.
- Ask one easy question. "What's a good window today?" beats "call me back" — it gives them a low-effort reply.
- Reference the voicemail explicitly so the two touches merge into one identity.
- Keep the opt-out. More on that below — it's not optional.
Where compliance quietly decides whether this works
An immediate dial-then-text on a fresh inbound lead is about as defensible as SMS gets — the person just handed you their number and asked to be contacted. That consent is the whole ballgame. But a few things still have to be true:
- The 10DLC campaign use case has to match. If you register a "marketing" campaign and then send transactional speed-to-lead replies (or vice versa), carriers filter you silently and your 90-second text never lands. This mismatch is one of the most common reasons a working cadence quietly stops working.
- Quiet hours still apply. A lead who submits at 11:40 PM doesn't get a text at 11:41. ReadySMS holds sends outside permitted local hours automatically based on the recipient's area — which matters because a 2 AM "just left you a voicemail" text is both illegal-ish and a terrible first impression. If a big share of your leads arrive off-hours, the after-hours routing cadence is the piece you want.
- STOP has to propagate. Automatic opt-out handling means a lead who replies STOP is suppressed across every campaign, not just the one that texted them. That's table stakes, and it's handled in-app.
None of this makes you lawsuit-proof — compliance is ultimately the sender's responsibility. But a matched campaign, enforced quiet hours, and honored opt-outs is what "doing it right" looks like on inbound speed-to-lead.
When you'd skip the text and transfer live instead
The text fallback is the right move on a no-answer. It is not always the right move on a pickup. If the lead answers, the question becomes whether to work the call live or hand it to a closer — and that depends heavily on lead source and value. High-intent, high-ticket sources often justify a live transfer over a text-back; lower-intent volume sources don't. We broke that decision down by source in when a live transfer beats a text-back.
The dial-then-text cadence in this post is specifically the no-answer recovery path. Pickups branch off before the voicemail drop ever fires.
The second and third touches, briefly
The 90-second text does the heavy lifting, but the cadence isn't done after one message:
- 0:90 — first text (the one above).
- ~5:00 — second dial if no reply. Fresh leads are still warm five minutes in; a second ring often catches them once they've set the phone back down.
- Next business hour — third touch. A short "still want that estimate?" text or one more dial. After this, drop into your normal nurture. Diminishing returns kick in fast, and hammering a non-responder just burns goodwill and segments.
Three coordinated touches inside the first hour recovers most of the recoverable leads. Beyond that you're spending money to annoy people.
The practical takeaway
The fast dial is only half of speed-to-lead. On every no-answer — which is most of them — a voicemail drop plus a text that lands inside 90 seconds gives the lead a channel they'll actually use, while the missed call is still fresh. The pieces that make it work are unglamorous: a matched 10DLC campaign, enforced quiet hours, honored opt-outs, and copy that names the reason and asks one easy question.
If you want to build this, the ReadySMS Team power dialer has the speed-to-lead auto-dial and voicemail drop, and the SMS side handles the compliant fallback on the same platform. Start with 2,500 free credits, wire up one lead source, and watch what the 90-second text does to your callback rate before you roll it wider.