A lead fills out your form. Your dialer fires inside 60 seconds. The phone rings four times and rolls to voicemail — or the lead sees an unknown number, thumbs it to silent, and keeps scrolling. That's the moment most sales orgs treat as a no. The rep marks "no answer," drops the lead into a callback queue, and dials the next one.
That's the mistake. A no-answer on the first dial isn't a rejection — it's a person who requested contact and then couldn't (or wouldn't) pick up an unknown number. The text that lands 90 seconds later, from the same brand they just filled out a form for, closes the gap. In my experience running these cadences, a well-timed text after an unanswered speed-to-lead dial recovers somewhere around a third of no-answers into a live conversation. Not a scientific number — a working one.
Full disclosure: I work for ReadySMS, and we ship both the Power Dialer and the SMS that this cadence runs on in one platform. That's the bias. The playbook below works on any stack that can dial fast and text fast; I'll just show you the math on ours.
Why the first dial gets ignored (and why the text doesn't)
Think about what the lead actually experiences. They typed their number into a form maybe 40 seconds ago. Their phone rings from a number they don't recognize. There's no context on the screen — just ten digits. Even a warm, high-intent lead defaults to "spam" on an unknown inbound call.
A text is different. It's asynchronous — they read it when they glance down, not when it interrupts them. It carries context in the first six words. And it gives them a low-friction way to respond ("yes" / "call me at 2") that a missed call doesn't. When the call and the text come from the same brand within two minutes, the text also retroactively explains the call: oh, that was them.
We covered the raw callback lift in a companion piece — when the speed-to-lead call goes to voicemail, the 90-second text roughly doubles callbacks. This post is about the recovery cadence after an unanswered ring, and the exact template and consent line that keeps it compliant.
The timing: 90 seconds, not 9 minutes
The window matters as much as the message. The whole reason speed-to-lead works is decay — a lead's willingness to engage drops fast in the first few minutes. We broke that curve down in the 60-second window post: the difference between dialing at 1 minute and 30 minutes is enormous.
The follow-up text obeys the same physics. Here's the sequence I run:
- T+0:00 — Lead submits. Speed-to-lead auto-dial fires (Team plan on the Power Dialer does this automatically on new leads).
- T+0:60–0:90 — Dial goes unanswered / rolls to voicemail. Optionally drop a short voicemail.
- T+1:30 — Automated text fires. Same brand, referencing the exact thing they just asked about.
- T+5:00–8:00 — If no reply, one second dial attempt.
Ninety seconds is the sweet spot: long enough that the call has fully rolled to voicemail and the lead has put the phone down, short enough that they still remember filling out the form. Wait nine minutes and you're texting a stranger.
The template that recovers
The single biggest mistake is sending a generic "Hi, is this a good time?" text. It reads like a broadcast. The template that recovers references the specific thing the lead requested and identifies the caller.
Here's a structure that works for an inbound web lead:
Hi Jordan — this is Mia at Northgate Roofing. Just tried you about the free roof inspection you requested. Easier to text? Reply YES and I'll grab a time, or call me back at this number. Reply STOP to opt out.
Break down why each piece is there:
- First name + rep name + brand — kills the "who is this" reflex.
- "Just tried you about [the specific request]" — retroactively explains the call and proves this isn't cold.
- "Easier to text?" — offers the low-friction channel instead of forcing a callback.
- A binary reply option (YES) — one thumb-tap to advance.
- STOP language — required, and not optional.
Count the characters on that message and you're over 160, which means it splits into multipart segments (160 GSM-7 for the first, 153 each after). No emoji — keep it GSM-7 so you don't crater the limit to 70 characters and triple your segment count. On ReadySMS Standard, that two-segment text costs 2 × ($0.02 + $0.0045) = $0.049 per lead. Recover a third of a hundred no-answers into live conversations for under five dollars of texting. That's the entire economic argument.
The consent line you can't skip
Here's where sales teams get careless. The dial is fine — telephone contact of a lead who gave you their number for that purpose sits in a different bucket than cold marketing. The text is where 10DLC and TCPA rules bite.
For this cadence to be defensible, you need three things in place:
- Express consent captured on the form. The submission that triggered the dial should include an opt-in checkbox and disclosure that they'll receive calls and texts. ReadySMS records that opt-in attestation as part of the audit trail on bulk and API sends.
- STOP handling that actually works. Every message carries opt-out language, and inbound STOP propagates so the contact can't be messaged again across any of your campaigns — automatically, not manually.
- The right campaign use case. If you registered your 10DLC campaign as "marketing" but this is a customer-care / lead-response text, you can hit silent delivery failures. We wrote about that exact mismatch in why the wrong 10DLC use case silently drops delivery.
None of this makes you lawsuit-proof — compliance is ultimately the sender's responsibility. But quiet-hours enforcement (holds sends outside the recipient's local permitted window), STOP propagation, and consent capture together turn a risky habit into a documented process. That's the difference between "we text leads back" and "we can show exactly what consent we had and when."
Dial-then-text vs text-then-dial: pick by source
The 90-second-text-after-no-answer cadence assumes a dial-first order. That's right for high-intent, phone-comfortable leads — demo requests, quote requests, inbound calls. It's not always right.
| Lead source | First touch | Why |
|---|---|---|
| Demo / quote request | Dial, then text at 90s | High intent, expects a call, phone in hand |
| Cold-ish web opt-in | Text, then dial | Lower intent, text warms before the ring |
| After-hours submission | Text immediately, dial next business hour | Quiet hours block the send anyway; text sets the appointment |
| Older aged lead | Text-first, low cadence | The ring reads as spam without warm-up |
We go deeper on choosing the order by source in text-first or dial-first. The point: the abandon-recovery text is a component you slot into whichever order the lead source calls for — it's not a fixed script for every lead.
The staffing reality that makes automation non-optional
One rep cannot dial a hundred fresh leads inside 60 seconds each, then hand-type a follow-up text at the 90-second mark. The whole cadence only holds when the dial and the text fire automatically off the lead-created event. That's what speed-to-lead automation on the Team plan does — auto-dial on new leads, and the follow-up text triggered by an unanswered outcome.
If you're sizing a team around this, the staffing math post walks through how many agents you actually need to hit sub-minute dials at volume. Short version: the automation carries the timing, the reps carry the conversations that the automation surfaces.
The practical takeaway
A no-answer on your first speed-to-lead dial is a person, not a dead record. The text at 90 seconds — same brand, referencing their specific request, offering a one-tap reply, carrying STOP language — recovers a meaningful share of those into live conversations for pennies apiece.
Three things make it work: fire it fast (90 seconds, not 9 minutes), reference the exact request so it doesn't read cold, and capture consent up front so the text is defensible. The dialer and the SMS living in one platform is what lets the whole sequence trigger off a single lead-created event instead of a rep juggling two tools.
If you want to price the text side against your current volume, the cost calculator does the segment math, and the Power Dialer plans show where speed-to-lead auto-dial kicks in. Start with 2,500 free credits and run the cadence on a live batch before you commit to anything.