Automated follow-up sequence across voice calls and text messages for real estate leads

Automated Real Estate Follow-Up: A Cadence That Survives Your Calendar

October 24, 2026

Playbook · Updated 24 October 2026

The lead was never bad. The follow-up just stopped.

Follow-up is the one part of the job with no deadline attached, so it is the first thing a busy week eats. Here is how to build a sequence that keeps running when a closing blows up — by lead source, with the right stop conditions.

Why "follow up more" never works as advice

Every agent knows the arithmetic. A lead comes in, you call once, maybe twice, send a text, and then a listing appointment runs long, an inspection blows up a deal, and the record goes quiet. Two weeks later it is buried under forty newer ones. Telling yourself to follow up more does not fix this, because the problem is not motivation. It is that follow-up has no deadline, and anything with no deadline loses to everything that has one.

Automated follow-up is not about sending more messages. It is about making the sequence survive your calendar. The system does not get pulled into a closing, does not forget which contact it spoke to on Thursday, and does not decide a lead is cold because it feels cold. What follows is how to design one that behaves well.

Principle 1 — Different sources, different cadences

A portal enquiry, an aged database contact and a past client are not the same lead and should not get the same sequence. One cadence for everything is why automation gets a bad name: it is too aggressive for the sphere and too timid for a hot web lead. Three starting templates:

Lead sourceFirst 48 hoursDays 3–14After
New web / portal leadVoice call within seconds; SMS on no-answer; second call at a different time of dayAlternating voice and text, varying the hour, each with a specific reasonMonthly long-horizon touch
Aged lead (90+ days silent)One voice attempt with a reason — a price change, a new listing in their search areaOne text, one more call at a different hourQuarterly, unless they engage
Past client / sphereNothing automated on day oneAnniversary and market-update touches, lightTwo to four times a year, human-sounding, always with an easy reply

These are templates, not rules. The right numbers come from reading your own transcripts after the first two weeks and adjusting what was too much or too little.

Principle 2 — Voice and text do different jobs

Voice establishes whether there is a real conversation to have. It asks your qualifying questions, handles the routine objections, and either books to your calendar or exits with a reason recorded. Text does the low-friction work in between: confirmations, reminders, a link, a reply to a missed call, a question that is easy to answer with one thumb. Used together they cover the two ways people actually respond. Used interchangeably they annoy everyone — a long qualifying interrogation by SMS is as wrong as a phone call to confirm a time that was already confirmed.

Principle 3 — Vary the hour, respect the time zone

The same number that never answers at 2pm often answers at 7pm. A retry cadence that repeats the same slot three times is not persistence, it is noise, and it trains the lead to ignore you. Each attempt should move the hour. Timing also has to be time-zone aware: a relocation lead from California should not get a 6am call because the workflow fired on Eastern time, and an international enquiry should be reached during their day. Calling windows are a compliance matter as well as a courtesy one; they are set by you and your broker, and the system enforces them.

Principle 4 — Stop conditions matter more than the script

The fastest way to make automation feel robotic is to keep sending after the person has already responded. Define the events that end a sequence and route to a human: a reply, a booking, an opt-out, or any answer you have flagged as intent ("we're meeting another agent Saturday"). When one fires, the sequence stops, the record is tagged, and you get the thread with the transcript attached — so you open with what the lead said, not with "just following up".

Principle 5 — Non-response is not a no

Most people are not ready this week. The leads who never answer the first fortnight are not dead; they are the slow half of the business, and the slow half is where listings come from eighteen months out. Move them to a reduced long-horizon cadence rather than deleting them. Holding the record costs nothing, and on a per-second billing model unanswered dials cost very little. See long-horizon seller nurture for how that cadence is structured.

What has to be true in the CRM for any of this to work

Follow-up only works if the systems agree on what happened. Every call needs to leave a disposition, a transcript and a next action on the contact, so the sequence knows where it is and you can read what the lead said six weeks ago before you pick up the phone yourself. If your outcomes live in a dialler the CRM cannot see, the cadence will double-call people and skip others. The write-back requirements are set out in what should write back after every call.

Build order, if you are starting from nothing

  1. Pick one lead source — usually new web leads, because speed matters most there.
  2. Write the first-48-hours cadence and the stop conditions. Agree calling windows and disclosure language with your broker.
  3. Connect the calendar so a good call can become a booking without a hand-off. See booking inside the conversation.
  4. Run it for two weeks. Read every transcript. Fix the script before you add a second source.
  5. Then point it at the list you already stopped calling. That is the fastest honest test of whether it is worth keeping — the service page for automated follow-up explains how we set it up.

Frequently asked questions

How fast should a new real estate lead be followed up?

As close to immediately as your system allows. Intent on a web enquiry decays quickly and most portal leads reach several agents at once, which is the entire argument for automating the first contact rather than fitting it around your day. AI IntelliCall places the first call within seconds of the lead reaching the CRM, at any hour.

How many follow-up attempts should a sequence make?

More than most agents manage by hand, spread across days and times of day rather than clustered. The exact cadence is set per lead source — a portal enquiry and an aged database contact deserve different treatment — and tuned from the transcripts in the first weeks.

Does the automation stop when someone replies?

Yes. A reply, a booking, or any answer you have flagged as intent ends the sequence, tags the record and routes the person to you. The point is to stop at the right moment, not to finish the script.

What happens to leads who never respond?

They move to a reduced long-horizon cadence rather than being deleted. Non-response is not a no, holding the record costs nothing, and voice usage on unanswered dials is small at $0.23 per minute billed by the second.

Start with the list you already stopped calling

Point the system at leads you know you abandoned and watch what comes back. 14-day trial, no contract.

Book a live demo

Related reading

About this playbook. Written by the AI IntelliCall Solutions team. Cadences shown are starting templates we configure per lead source; they are not promises of response rates, and outbound calling and texting carry consent, do-not-call and calling-hour obligations that are yours and your broker's to set.

Scott Lehr

Scott Lehr

Scott Lehr is a co-founder of AI IntelliCall Solutions, which builds AI voice and chat assistants that call, qualify and book appointments for real estate teams. He works in South Florida real estate and writes here about applying AI calling, conversational AI and CRM automation to real agent workflows.

Back to Blog