You paid $40, $60, sometimes $120 for that Zillow or Realtor.com lead. The buyer filled out the form because they're looking at a house right now, on their phone, probably in the driveway. And if you wait until you're back at your desk to call them, they've already tapped "Contact Agent" on three more listings and two of your competitors are dialing.

The window is brutal. Response likelihood on a portal lead drops off a cliff somewhere between minute five and minute ten. Not "declines gradually over the afternoon" — falls off a cliff. So the cadence below isn't built around thoroughness. It's built around getting a human touch on that lead before your competition does, then falling back to text the instant the call misses.

Full disclosure: I work for Ready. We sell an SMS platform and a Power Dialer that live in the same app, so I have a stake in you doing outbound well. I'll show the math and the timing so you can judge it yourself.

Why a callback loses to an instant dial

Here's the trap most agents fall into. The lead comes in, you get an email or a push notification, you make a mental note to "call them back in a few." By the time "a few" happens, the lead has cooled from actively browsing to casually researching — a completely different conversation. The 60-second window post walks through what happens to close rates at 5, 30, and 60 minutes; the short version is that a dial at minute one and a dial at minute thirty are not the same lead.

The fix is to remove you from the timing loop. The dial should fire off the form submission, not off you noticing the form submission. That's speed-to-lead auto-dial: new lead lands in the CRM, the dialer queues it and rings your line to connect you the moment you pick up. On Ready's Power Dialer, speed-to-lead auto-dial is a Team plan feature ($69/agent/mo), and it's the whole reason to run a dialer on portal leads instead of a manual click-to-call.

One caveat that eats real time: the lead has to actually arrive fast. If your web form routes through Zapier, you can lose a minute or two in the middle. We wrote up that exact latency problem in routing SMS through Zapier — native sync fires instantly, a middleware hop doesn't.

The cadence, minute by minute

This is a compressed cadence for warm inbound leads — people who just filled out a form and, by doing so, gave you consent to contact them. (Cold outreach is a different legal animal; more on that below.) The whole thing runs inside the first ~30 minutes, not over three days.

WhenActionChannelNotes
T+0 (form submit)Auto-dial fires, connects you when the lead picks upVoiceSpeed-to-lead dial from the queue
T+0, no answerVoicemail drop (pre-recorded, 12–15 sec)VoiceNo live rambling; drop and move on
T+90 secCompliant text: reference the property, ask one questionSMSTwo-way, replies land in your inbox
T+10 min, no replySecond dial attemptVoiceDifferent tone — "just missed you"
T+30 min, no replySecond text, softer ask + opt-out languageSMSSpace it; don't hammer
Next business dayThird dial + text if still no contactBothThen hand to normal follow-up drip

The order matters. Dial first because a live pickup on a warm portal lead converts better than anything else you can do. But when the dial misses — and most first dials do — the text that lands in ~90 seconds is what doubles your callback rate. We broke that specific mechanic down in the dial-then-text fallback post: the voicemail alone gets ignored; the voicemail plus a text they can reply to with one thumb gets a response.

Why the voicemail drop instead of a live voicemail

If you leave voicemails the manual way, you're stuck on the line for 20–30 seconds per lead composing a message, and half of them come out worse than the last one. Voicemail drop plays a pre-recorded clip and instantly frees you to take the next connect. On a batch of 40 fresh leads, that's the difference between working the list in real time and falling behind by lead number eight.

One thing worth knowing: aggressive answering-machine detection can clip the front of your drop or, worse, hang up on a live human it mistook for a machine. If your connects feel low, read the AMD false-positive breakdown before you crank detection sensitivity up.

The text that actually gets a reply

The 90-second text is doing a lot of work, so don't waste it. Bad version:

"Hi, this is Dana from ABC Realty. I saw you were interested in a property. Let me know if you'd like more info!"

That's generic enough to be ignored. Better version — reference the specific listing and ask exactly one answerable question:

"Hi Sam, it's Dana — you just looked at 214 Oak St on Zillow. Are you hoping to tour it this week, or still comparing options? Reply STOP to opt out."

Two things: it proves you're a real person who saw their actual action, and it gives them a binary they can answer in three seconds from the sidewalk.

Now the segment math, because it's your money. That message is about 150 GSM-7 characters, so it fits in a single 160-character segment. On Ready's Standard tier that's $0.02 + $0.0045 carrier = $0.0245 per send. Run it across 500 fresh leads in a month and your text-fallback cost is 500 × $0.0245 = $12.25. Add an emoji and you drop to a 70-character unicode limit, which splits a 150-char message into three segments — 500 × 3 × $0.0245 = $36.75. Same message, 3x the bill, for a smiley face. Keep the fallback text plain. (Full tiers are on the Ready pricing page.)

Consent: what "warm" actually earns you

A portal form submission is the strongest consent you'll get in real estate outbound, and it's still worth being precise about what it covers. The buyer asked you to contact them about a property — that's express consent to call and text about that inquiry. It is not a blanket license to blast them promotional listings for the next two years.

So the warm cadence above is on solid footing. The moment you drift into buying a list of "homeowners who might sell" and texting them cold, you've left the safe path entirely — there's no compliant 10DLC route for cold property-owner texts, which we spelled out in cold-texting property owners. The clean rule of thumb from cold vs. warm channel mix: text only people who opted in, dial cold lists under phone rules, and never confuse the two.

A few guardrails Ready enforces so you don't have to remember them at 2:04pm:

  • STOP handling is automatic. A lead who replies STOP is suppressed across your campaigns — no re-messaging by accident.
  • Quiet hours are enforced by the recipient's local time, so your after-hours form fill doesn't turn into a 11pm text.
  • Litigator and DNC scrubbing is available before send, and the standalone scrub add-on is $0.005/contact — cheap insurance against the $500–$1,500-per-text TCPA exposure a single known litigator can create.

None of this makes you lawsuit-proof; consent is ultimately your responsibility. It just removes the dumbest ways to get burned.

Staffing the cadence so it doesn't collapse

The cadence only works if someone is actually available to take the connect when the dial fires. During a busy open-house weekend, portal leads can arrive faster than one agent can talk. If your team is dropping connects because nobody's free, that's not a cadence problem — it's a staffing-math problem, and the staffing math post has the ratios. For a solo agent, the honest answer is: let the text fallback carry the leads you can't get to live, and dial them back the moment you're free.

The practical takeaway

Speed beats thoroughness on portal leads. A dial at minute zero, a voicemail drop, and a plain-text fallback at 90 seconds will out-close a polished callback you make an hour later — every time. Keep the text to one segment, reference the actual listing, honor opt-outs automatically, and only run this cadence on leads who actually opted in.

If you want to test it, Ready gives you 2,500 free SMS credits, no card required, and the Power Dialer has a free tier (1 agent, 500 minutes/mo) to try the dial side — speed-to-lead auto-dial lives on the Team plan when you're ready to fire dials off form fills automatically. Start here and wire up one lead source first before you point your whole pipeline at it.