Lead Follow-Up Automation That Does Not Embarrass You

Automation is worth nothing until the stages are honest

The first rule of lead follow-up automation is that it amplifies whatever your pipeline already is. A pipeline nobody updates, automated, becomes a machine that sends confident messages to people whose circumstances changed three weeks ago — which is worse than silence, not better.

So the order is: honest stages, then a rule about speed, then sequences. Most agents do it backwards, buy the tier with the automation builder, and end up with an expensive way to annoy their sphere.

The two rules that do most of the work

Speed on a new lead and a floor under the old ones. Those two cover the majority of what automation is bought for, and both can be built on a free tier without an automation builder at all.

1. Every new lead gets a task on the same day it arrives. Not an email — a task with a person's name on it. Automation's job here is to make sure the task exists, not to do the talking.
2. Nothing sits untouched for fourteen days. Build one saved view filtered to no activity in fourteen days, look at it weekly, and act on the top five. This is a view, not a workflow, and it works on every product on our comparison including the free ones.

What each tier actually gives you

Automation is the feature most often used to separate a cheap tier from an expensive one, and the step is usually the second tier rather than the first. That matters because the headline price you were quoted is often the tier without it.

Two things stand out. Follow Up Boss puts automated follow-up in its entry tier, which is consistent with a product built for teams chasing bought leads. And Wise Agent lists drip campaigns as included with every plan at $42 a month — the cheapest published route to sequences in this comparison.

What not to automate

Do not automate anything that implies you did something you did not do. The temptation in this industry is a message that reads as personal — a note about the neighbourhood, a check-in after a viewing — sent by a rule rather than a person. Clients notice, and the cost of being caught is the referral.

• Automate the reminder to you, not the warmth to them.
• Automate the logistics — document requests, appointment confirmations, closing-date reminders — where a template is what the recipient expects anyway.
• Never automate a message whose content claims first-hand knowledge you do not have.
• Respect the consent and opt-out rules that govern marketing email and SMS in your jurisdiction. Those obligations are real and this is not legal advice — check them with your broker or counsel before you switch a sequence on.

Building the fourteen-day view, step by step

This is the highest-value thing you can build in a CRM and it takes about five minutes on any of the products here. It also needs no automation tier.

1. Filter deals to any stage before closed.
2. Add a condition on last activity date, older than fourteen days.
3. Sort by expected value or commission, descending, so the list ranks itself.
4. Save it, name it something you would say out loud, and pin it.
5. Open it on the same day each week and clear the top five. That is the whole system.

If your CRM cannot do that, it is the wrong CRM regardless of price — every product on the comparison can, including both free tiers. For the setup that comes before it, the guide to what a real-estate CRM actually is covers naming the stages.

Three sequences worth building, and one to leave alone

Almost all the value of automation in this business sits in three sequences, and all three are logistics rather than persuasion. That is not a coincidence — logistics is where a template is what the recipient expects, so nothing about it reads as insincere.

1. The new-lead acknowledgement. One message, sent immediately, that says a real person will be in touch and when. Its job is to buy you the afternoon, not to sell anything.
2. The viewing confirmation. Time, address, what to bring, how to reach you if something changes. The single highest-return automated message in this industry, because it prevents the failure it describes.
3. The under-contract date reminders. Inspection deadlines, financing deadlines, closing date. Dates that bind belong to the software rather than to anyone's memory.

The one to leave alone is the long nurture sequence written in a first-person voice — the one that tells a contact what you noticed about their neighbourhood. Send those by hand, less often, to fewer people, and they will work better than any cadence.

Why the stages have to be honest first

Automation reads the pipeline as the truth, so a stale pipeline produces confidently wrong behaviour rather than no behaviour. A deal left in "showing" after the buyer walked away will keep generating showing follow-ups, and the person receiving them knows exactly what happened.

The fix is not a better sequence, it is a weekly habit of moving records. Fifteen minutes on the same day each week, working the fourteen-day view, keeps every automation you build pointed at something real — and it is the practice that makes the difference between a CRM and a filing cabinet that emails people.

Measuring whether it worked

Do not measure it with an open rate. Measure it with two counts you can take yourself: how many records sat untouched for fourteen days this week compared with last, and how many viewings were confirmed without a phone call. Both are numbers your own CRM can give you, and neither requires trusting a vendor's dashboard.

Where automation goes wrong, concretely

Four failures account for most of the damage, and every one of them is a configuration choice rather than a software defect.

• No exit condition. A sequence that keeps sending after the person replies is the single most common complaint, and it is always a missing rule.
• Two sequences on one contact. Someone who is both a past client and a new lead receives two conversations from one person.
• Business-hours assumptions. An automated message at 3am reads as automated no matter how it is written.
• Stage changes that fire messages retroactively. Tidying an old pipeline can trigger a month of correspondence in one afternoon. Switch sequences off before you do a cleanup.