A lead just hit your CRM. The clock starts now. The question most teams answer badly — or never answer at all — is what happens in the next ten seconds. Do you blast-dial and live-transfer to whoever's free? Route to a specific rep with a whisper of context in their ear? Or fire an automated text and let the lead come back to you on their schedule?
The wrong answer isn't "no contact." It's the same contact for every lead. A demo request from your pricing page and a Facebook lead-form click from someone who tapped a coupon ad are not the same buyer, and treating them identically wastes either your reps' time or your hottest opportunities.
Full disclosure: I work for ReadySMS, and we build both the SMS and the Power Dialer side of this stack — so I have a horse in this race. But the framework below is channel-agnostic. Use it even if you never touch our tools.
Why the handoff decision matters more than the speed
We've written before about what happens to close rates when a lead sits 5, 30, or 60 minutes before anyone dials. Short version: the curve falls off a cliff, fast. The first few minutes carry most of the contact-rate advantage.
But speed is only half the equation. Speed plus the right channel for that lead's intent is what actually converts. A live transfer to a high-intent demo request is gold. The same live transfer to a top-of-funnel content download interrupts someone who isn't ready to talk and trains them to dodge your number. You spent your fastest, most expensive motion on the lead least likely to reward it.
So the real decision tree has two axes: how hot is the intent, and how interruptible is this person right now.
The three handoff types, and what each one costs
Before the framework, get clear on what you're choosing between. With a stack like ReadySMS Power Dialer paired with SMS, you've got three real moves:
| Handoff | What it is | Best for | Rough cost per contact |
|---|---|---|---|
| Live transfer (auto-dial) | New lead triggers an instant outbound dial; on connect, the lead is transferred to an available rep | High-intent, phone-ready leads | ~$0.0375–$0.06/min of talk time (dialer plan-dependent) |
| Whisper-coached rep call | Same instant dial, but routed to a named rep with a whispered context cue before they speak | Mid-to-high intent where rep fit or coaching matters | Same dialer minute cost |
| Automated text-back | Lead instantly gets an SMS opening the conversation; replies route to your inbox | Lower intent, after-hours, or "not phone people" | ~$0.0155 + $0.0045/segment on the Starter tier |
Note the cost asymmetry. A 90-second connected call costs more than a dozen text exchanges. That alone tells you not to live-transfer everything — you'd burn agent minutes on leads that a $0.02 text would've handled.
The dialer's transfer, barge, and whisper controls are what make the first two distinct. Whisper lets a manager (or an automated cue) feed the rep "this is a demo request from the enterprise pricing page" before they open their mouth. Barge lets a manager jump into a call that's going sideways. Those features only earn their keep on leads worth coaching in real time.
The framework: map handoff to lead source
Lead source is the cheapest available proxy for intent. You usually know it before you know anything else about the person. Here's how I'd route by source:
Demo / "talk to sales" / pricing-page form → Live transfer
This person raised their hand and asked to talk. They expect a call. The cost of a connected dial is trivial against the value of a sales conversation. Auto-dial, live-transfer, and if you've got bench depth, whisper-coach the rep on which page they came from.
If no rep connects within, say, three rings, fall back to a text-back so the lead isn't dropped. Never let a hot lead hit dead air.
Inbound phone call you missed → Whisper-coached callback + instant text
Someone called you and you didn't pick up. That's high intent and a little bruised. Fire an instant SMS ("Sorry we missed you — calling right back, or reply here if that's easier") and trigger a callback. The whisper cue here is "missed call, be apologetic." Giving the lead the text option respects the ones who'd rather not redial.
Paid lead-form ads (Facebook, Google) → Text-back first, dial as escalation
This is where most teams overspend on dialing. A coupon or ebook click is not a phone-ready signal. Lead with an automated text that confirms what they asked for and asks one qualifying question. If they reply with buying signals, then escalate to a live transfer. You've now spent dialer minutes only on leads that earned them.
This cold-vs-warm split is the same logic we lay out for real-estate teams dividing outreach between dialer and SMS — match the channel's intrusiveness to the lead's temperature.
Content downloads / newsletter / webinar reg → Text-back only (or nurture)
Pure top-of-funnel. A live transfer here gets you opt-outs and a reputation as the company that calls instantly when you grab a checklist. Drop these into an SMS nurture sequence, or hand to email. Reserve the phone for when they signal more.
Referrals / warm intros → Whisper-coached personal call
Highest-trust, lowest-volume. These deserve a human who knows the context, not an auto-queue. Whisper the referrer's name to the rep before they dial. This is a low-frequency, high-care lane — don't automate the warmth out of it.
Layer two: time of day changes the answer
Source sets the default; the clock overrides it. A demo request at 9 PM shouldn't trigger a live dial — that's a quiet-hours problem and a bad first impression. Send the text-back, queue the call for the next permitted window.
ReadySMS enforces quiet hours on sends based on the recipient's local area, which keeps your SMS leg compliant automatically. (Worth reading our full take on why quiet hours are a smart rule, not just a legal one — the after-hours text often outperforms the daytime call because it's not an interruption.) Apply the same restraint to your dialer manually: don't auto-dial leads into their dinner.
So the practical rule: during business hours, route by source. Outside them, default everything to text-back and let the conversation start on the lead's terms.
A worked example: 1,000 mixed leads a month
Say you get 1,000 inbound leads monthly, split roughly:
- 150 demo/pricing requests → live transfer
- 100 missed calls → callback + text
- 400 paid lead-form → text-back, ~20% escalate to dial (80 dials)
- 350 content/newsletter → text-back nurture only
The dump-everything-into-the-dialer approach: ~1,000 connect attempts, agent time spread thin, and 750 of those calls landing on leads who didn't want a call. Reps burn out chasing cold contacts; the 150 real opportunities get the same energy as the ebook grabbers.
The routed approach: ~330 dial attempts (150 + 100 + 80), all on leads with real phone intent, plus ~850 leads getting an instant text at roughly two cents each. On the Starter tier a one-segment text is $0.0155 plus the $0.0045 carrier pass-through — $0.02 per text-back, so 850 texts is about $17. Your agents now spend their minutes where the money is, and nobody hot waits in a queue behind a newsletter signup.
That's the whole point: the framework isn't about doing less. It's about not spending your most expensive motion on your least-ready leads.
Build it in one stack, or you'll lose the handoff in the seams
The reason most teams don't route this cleanly is that the dialer and the texting platform live in different tools, with a brittle Zap holding them together. The text-back fires but the dialer doesn't know the lead replied; the rep calls someone who already booked over SMS.
Running outbound voice and SMS in one platform — with the Power Dialer (plans and minute pricing here) feeding the same conversations inbox as your texts, and a native GoHighLevel integration syncing both legs per sub-account — is what keeps the handoff from falling through the cracks. The escalation from text to live transfer becomes one motion, not a tab-switch and a prayer.
The takeaway
Stop asking "how fast can we contact every lead" and start asking "what's the right first move for this lead, right now." Source tells you intent. The clock tells you whether to dial or text. High intent and phone-ready earns a live transfer or a whisper-coached call; everything else starts as a text and earns the call later.
If you want to map this against your actual close-rate-by-minute math first, start with the 60-second window post, then sketch your own source-to-handoff table before you wire anything up. The framework matters more than the tooling — get it on paper, then pick the stack that lets you run it without seams.