Real Estate Lead Routing Rules for Past-Client Replies and Referrals

A past client replies to your anniversary email: "We're thinking about selling in the spring." The reply lands in a shared inbox, or in the mailbox of an agent who left in August. Nobody answers for four days. Most teams lose these replies through gaps, not through bad service. Written real estate lead routing rules close those gaps. This post covers ownership, a response window and what happens when the agent has gone. It is one piece of our real estate past client follow-up automation system for South Jersey teams. Here is where to start.

Why past-client replies need their own routing

Most routing logic was built for strangers. A portal lead arrives with no history, so you rotate it to whoever is next. Round-robin (giving each new lead to the next agent in line) makes sense there.

It makes no sense for a person who closed with one of your agents two years ago. That person already has a relationship, and handing them to a stranger on the team breaks it.

The volume is worth the effort. National Association of REALTORS® reports that in 2025 the typical REALTOR® earned 28% of business from repeat clients and another 22% from referrals from past clients and customers. That is the 2026 Member Profile, which NAR released on June 25, 2026. It is a national median for individual members, not a figure for your team or for South Jersey.

So half of a typical member's business comes from people who already know someone. Those people deserve a routing path that reflects it.

Past-client traffic comes in three forms, and each needs its own rule:

• A reply to an email or text you sent (an anniversary note, a market update, a check-in).
• A direct call, text or form from a past client who found you on their own.
• A referral: a past client introduces a friend, relative or coworker.

Rule 1: One owner per past client, stored in one field

Every past-client record needs a single relationship owner. Not "the team." Not two agents. One name, in one field, that the CRM (customer relationship management software) can read.

The default we suggest is the agent of record on the client's last closed transaction. Pick a default and write it down. Then list the exceptions you will allow, such as a client who asked for a different agent in writing.

This only works if the field is filled in and current. If your records are patchy, fix that first. Our past-client list audit covers the six fields every follow-up system needs, and the owner field is one of them.

A routing table you can adapt

Here is the shape of the rules. The windows are example settings for you to tune. They are not benchmarks.

Example routing rules by inbound type

Inbound type	First owner	Backup if no reply	Example window
Reply to a nurture email or text	Relationship owner	Team lead	Same business day
Direct call or form from a past client	Relationship owner	Team lead	Two business hours
Referral of a new person by a past client	Relationship owner of the referrer	Team lead	Two business hours
Owner has left the team	Team lead holds it	Reassignment queue	Same business day

Anything the owner does not touch inside the window goes to the backup. The backup is a named person, not a shared inbox that everyone assumes someone else is watching.

Rule 2: Set a response window and define what stops the clock

Marketing tools often quote a "five-minute rule" for lead response. Those figures come from studies of web-form leads and are mostly published by software vendors. We have not found a source that measures past-client replies specifically, so we do not quote one here.

What we can say is simpler. A past client who writes to you is not comparison shopping yet. A slow reply still tells them you are busy, and it lets another agent get a call in first.

Write your window as three parts.

1. The clock. Does it run on business hours or wall-clock time? A Saturday-morning reply with a "same business day" window waits until Monday. Decide whether that is acceptable.
2. What stops it. A human reply, call or text. An auto-acknowledgement does not count. If you send one, say plainly that a person will follow up.
3. What happens at the limit. The task moves to the backup and the owner is notified. The team lead sees a breach count.

Volume matters here too. Replies cluster after campaigns. If you send a batch of messages in January, the replies arrive in a wave. Our January-to-March follow-up calendar shows where those waves fall. Check that your agents can actually meet the window on your heaviest send day.

The custom real estate CRM we build ties lead routing to agent follow-up in one system. The same logic works in an off-the-shelf CRM if it supports owner fields, task timers and escalation. What matters is that the rule is written first.

Rule 3: Treat referrals as new leads with a "referred by" link

A referral has two people in it: the past client who made the introduction and the new contact. Your CRM should store both and link them.

The new contact goes to the referrer's relationship owner by default. The referrer chose that agent's name when they made the introduction. Skipping the agent breaks the chain of trust.

Three exceptions come up often:

• The new contact is outside your market. The owner decides whether to refer them to an agent elsewhere. Referral fees and agreements between brokerages are a matter for your broker and attorney, not for the CRM.
• The owner is at capacity or away. The backup picks it up, and the owner is told.
• The owner has left. See the next section.

Also route a thank-you to the referrer. It should be a human message, sent within the same window as the introduction. If you want a record of which clients refer most, the "referred by" field gives you that count for free.

When the agent has left the team

This is the case most routing plans skip. Left unplanned, a departure leaves hundreds of past clients attached to a name that no longer answers.

Set the sequence before anyone leaves:

1. Day of departure. The owner field on every record flips from the agent to the team lead. Nothing is left blank or pointing at a closed account.
2. Mailbox and phone. Replies to the old agent's address should reach a monitored place. Whether you forward them, and for how long, is a decision for you, your broker and the departing agent. Settle it in writing.
3. Holding period. The team lead owns the records for a set period while you decide who takes each client.
4. Reassignment. Assign by a stated rule, not by whoever asks first. Useful inputs include neighborhood, price range, language, current workload and any client preference you have on file.
5. A personal note. The new owner introduces themselves to each client. Do not send a mass "your agent has left" email without someone approving the wording.

Who is entitled to the relationship when an agent leaves depends on your agreements with the agent and your brokerage, and on licensing rules. We do not give legal advice. Your broker of record and attorney should settle that. The CRM's job is to make sure the reply does not sit unanswered while that gets settled.

A client who replies to a departed agent should get a human answer within your normal window. That answer can say, plainly, that the agent has moved on and who will help. It is better than silence.

What to automate and what stays human

Routing is rule-based, so most of it can run without anyone touching it. Assigning the owner, starting the timer, escalating at the limit and notifying the backup are all mechanical.

Three parts need judgment:

• Reading the reply. An AI step can sort replies into labels such as "ready to sell," "has a question," "out-of-office" or "unsubscribe," and show the label with the original message. A person reads the message before replying. If the label is wrong, the person changes it. That correction should be logged.
• Drafting the answer. A model can draft a response from the client's CRM record. The owner edits and sends it. Nothing goes out unreviewed.
• Opt-outs. A request to stop messages should be honored by the system at once and logged. Questions about consent for texting and email belong with your attorney.

This is the kind of work our CRM-connected email marketing automation covers: replies from nurture emails flow back into the CRM with an owner and a timer attached. We make no claim about how many replies you will get. That depends on your list, your content and your market.

Test the rules before March 2027

Do not wait for a real reply to find a hole. Build ten test records and send a dummy reply for each case in the table. Use these:

• A client whose owner is active.
• A client whose owner is on vacation.
• A client whose owner left last month.
• A referral with a known referrer.
• A referral with a blank owner field.
• A reply that arrives on a Saturday night.

Watch where each one lands, who gets the notification and what happens when the window expires. Every gap you find in testing is one you will not find through a lost listing.

Once live, track three numbers weekly: replies with no owner, replies that breached the window, and how long the oldest open reply has waited. Those three tell you more than a dashboard full of open rates. Replies often start with a message that prompted them, so see how we build those in home anniversary emails and the CRM fields they pull from.

If your rules need workflow beyond what your CRM supports, AI workflow automation with human approval steps is how we build the reply sorting and draft step. Tell us what your team does today, and we will tell you plainly whether it needs custom software or just a better-configured tool.

Frequently Asked Questions

What are real estate lead routing rules?

They are written instructions for who receives each new inquiry, how quickly they must respond, and what happens if they do not. For past clients, the rules usually assign the reply to the agent who closed the last transaction, set a time limit, and name a backup, such as the team lead, for missed deadlines or departed agents.

Should past-client replies go through round-robin routing?

Generally no. Round-robin suits anonymous leads with no history. A past client already knows an agent on your team, and a random assignment breaks that relationship. Route the reply to the relationship owner first and use a backup only when the owner does not respond within the window you set.

What should happen to past clients when an agent leaves the team?

Reassign their records to the team lead the day the agent leaves, so no reply sits with a dead account. Then hold them briefly while you assign each client by a stated rule. Who is entitled to the relationship depends on your agreements and licensing rules, so ask your broker and attorney.

How fast should we reply to a past client who answers a nurture email?

We suggest a human reply within the same business day as a starting window, then tighten it if your agents can meet it. We know of no source that benchmarks past-client replies specifically, so treat any number as a setting to test on your own team rather than an industry standard.

Past-client replies are too valuable to be left to a shared inbox. If you want help writing these rules and building them into your CRM, talk to us about a real estate CRM built around how your team works.