Real estate lead management is a manager's job, not an agent's. It answers who gets each lead, how fast they must act on it, what happens when they do not, and how the office learns which agents and sources turn enquiries into instructions. This article covers that team-level rhythm and how to run it on the levelpartner.ai platform: automatic assignment, an internal notification to the assigned agent, and a stale-opportunity workflow that recovers leads when the standard is missed.
The four decisions a lead manager makes
Strip away the software and lead management comes down to four decisions, made once and then enforced every day.
Routing: which agent receives which lead. Response standard: how quickly the first reply and the first conversation must happen. Recovery: what happens when an agent misses the standard. Review: how the manager checks results and changes the first three decisions when they are not working.
Most offices make the first decision informally, never write down the second, have no third, and replace the fourth with a monthly sales meeting about closed deals. The result is that strong agents are overloaded, weaker ones coast, and nobody can say where leads are lost.
Routing: the case against pure round robin
Round robin, giving each new lead to the next agent in turn, is the default in almost every CRM because it feels fair. It is fair to agents. It is not fair to the lead, or to the business.
Agents convert at different rates, specialise in different property types and have different capacity in a given week. Sending a high-value seller valuation to a new negotiator because it is their turn costs the office an instruction. Sending a fifth portal lead to an agent already carrying forty open conversations means the fifth gets a slow reply.
Route on three things in this order. First, specialism and territory: sales or lettings, the area, and property type where it matters. Second, capacity: take an agent out of the rotation for a week when their open early-stage leads pass an agreed number. Third, rotation among whoever is left.
How to set up automatic assignment
On the platform, assignment is a workflow. Put an If/Else on the enquiry type or area first, then an Assign To User action on each branch with the agents who cover it. Within a branch, the action shares leads out in turn.
- Go to Automation, then Workflows, click Create Workflow and select Start from Scratch.
- Add a trigger, such as Contact Created or the form your enquiries arrive through.
- Add the Assign to User action.
- Select the users to include in the rotation.
- Set the split traffic field to equally for an even distribution.
Then, straight after the assignment, tell the agent. The order matters: the notification goes to whoever is assigned, so it must come after the assign step.
- In the workflow builder, click the plus button below the assign step to open the list of actions.
- Select Send Internal Notification.
- Enter an Action Name, such as "New lead - assigned agent - SMS".
- Choose the Type of Notification. SMS or the in-app notification suits agents at viewings.
- Set To User Type to the assigned user and write a message with the lead's name, source and property.
- Save the action and test the workflow.
If the contact has no assigned user when the notification runs, that step is skipped and the workflow carries on, which is why a broken branch shows up as silent leads rather than an error.
Suppose the office receives 260 sales enquiries a month. Under pure round robin, each of the eight negotiators would get about 32. If the two most senior convert enquiries to instructions at roughly twice the rate of the two newest, then routing valuation requests above a set price band to the four most experienced, and capping anyone at 35 open early-stage leads, would put the higher-value enquiries with the people most likely to win them. The figures are illustrative.
Response standards that agents can actually meet
Write the standard down and make it specific. A useful version has three parts: a first reply within five minutes during office hours, a two-way conversation attempted within one hour, and a follow-up on day two, day four and day seven if there is no conversation yet.
Agents cannot meet a five-minute standard while they are at viewings. That is where automation and an AI agent earn their place. The AI makes the first reply on web chat, SMS or WhatsApp, answers basic questions about the listing and offers viewing slots. The agent's standard then starts from the moment a person wants to talk to a person. For how that first conversation should be designed, see conversation design for real estate AI.
Out of hours, decide whether the AI books directly into calendars or collects details for the morning. Either is fine. Not deciding is not.
Recovery: what happens when a lead is missed
A response standard with no consequence is a suggestion. Build recovery into the system so that it happens without a manager chasing.
Inside the first hour, the assignment workflow itself does the chasing: a Wait step, then an If/Else on whether the opportunity has left New, with a second notification to the agent and then one to the team lead on the None branch. Beyond the first day, use the Stale Opportunities trigger, which fires when an opportunity has sat in a stage without progress for a set number of days.
- Go to Automation and select Workflows.
- Click Create Workflow, then select Start from scratch.
- Click Add new Trigger.
- Select Stale Opportunities from the list.
- Name the trigger, such as "Lead untouched: reassign".
- Click Add Filters.
- Set Duration in Days to 1.
- Set In Pipeline to your sales or lettings enquiry pipeline.
- Set Pipeline Stage to New.
- Click Save Trigger.
Add the actions after it: a note on the record saying why, an Assign To User step with the eligible agents, and internal notifications to both the old and the new agent. The stale timer only starts once the trigger is live, so leads already sitting in New are not caught; clear those by hand on the first day. Moving or updating the opportunity resets the timer.
Reassignment is the part agents dislike, and it is the part that works. Once agents see that untouched leads really do move, response times tend to tighten quickly. Keep the rules public and identical for everyone, including senior agents, or the system loses credibility at once.
Reassigning leads silently. If an agent finds out from the client that a colleague has called, trust in the system collapses. Every reassignment should notify both agents and leave a visible note on the record.
Review: the weekly half hour
The manager's review is weekly, short and based on the same data the agents see. Four views are enough.
- Leads received, by source and by agent.
- Median time to first reply and to first two-way conversation, by agent.
- Leads reaching a booked viewing or valuation, by source and by agent.
- Leads reassigned, by agent, with the reason.
Look for gaps between agents first. If one agent books viewings from far fewer leads than the others, listen to a few of their calls or read their messages before deciding anything. Then look at sources. A source with many leads and few appointments is either low quality or being answered badly, and the conversation data tells you which. For judging sources by what they eventually produce, see comparing real estate lead sources.
Say the manager notices in a weekly review that lettings applicants from one portal wait a median of three hours for a reply, against twenty minutes for every other source. Suppose the cause is that the portal's emails land in a shared inbox rather than in the CRM. Once the connection is fixed, that source should be answered as fast as the others, and if reply speed drives bookings, its booked viewings would be expected to rise. The scenario is hypothetical.
What most articles on lead management get wrong
They treat it as a funnel problem: capture, nurture, convert, with software at each step. That framing makes lead management sound like something you buy and configure.
In practice it is a management practice that software supports. The routing rules, the response standard, the recovery steps and the weekly review are decisions a manager makes and enforces. The best CRM in the world will not help an office where nobody looks at response times, and a modest system works well in an office where someone does. Choose and configure software to make those four decisions easy to run. Do not expect software to make them for you.
The trade-off
Strict routing, published standards and automatic reassignment take some autonomy away from agents. Experienced agents who are used to choosing their leads, or who hold leads for weeks without contact because they "know the client", will feel managed. Some will tell you it damages morale.
It does change the culture. The office moves from individual agents owning their pipeline to the firm owning a process that agents work inside. What you gain is consistency for the client, visibility for the owner and fair treatment for newer agents who otherwise only get the leftovers. If you lose an agent over it, check their conversion data before you worry. Sometimes it is the agent who was holding leads they never worked.
Troubleshooting
Leads arrive with no one assigned. The contact matched no If/Else branch. Every branch, including None, needs an Assign To User step, even if None goes to the team lead.
Agents say they were never told. The notification sits before the assignment, or the agent has no valid phone number for SMS. Move it after the assign step and check the user's details.
The stale workflow reassigns leads that were worked. The agent called but did not move the stage or log anything. Make moving the opportunity out of New part of the first call.
Old leads were never recovered. The stale timer does not look back. Filter the pipeline for older leads still in New and assign them by hand once.
How this sits with the rest of your system
Lead management depends on two things being right underneath it. Each agent has to keep their individual leads accurate, with a status and a next-action date, or the manager's views show nonsense. That habit is set out in keeping track of real estate leads day to day. And the CRM has to be structured so that sales, lettings and valuations run in separate pipelines with their own stages, as described in real estate CRM structure for a brokerage.
With both in place, the manager's job is thirty minutes a week plus whatever the data says needs attention.
Frequently asked questions
Should new agents get fewer leads?
They should get leads matched to their experience, with a capacity cap and close review in their first months. Give them lettings applicants, lower-band enquiries and nurture leads rather than starving them. Watching their conversion weekly tells you when to widen what they receive.
How fast should a real estate lead get a first reply?
Within minutes during working hours, which in practice means an automated or AI first reply backed by a person within the hour. Out of hours, a prompt acknowledgement and a booking option is enough. Whatever standard you choose, write it down and measure it.
What if an agent disputes a reassignment?
Look at the record together. If the rules were applied correctly and the lead was untouched, the reassignment stands. If the agent had worked the lead but not recorded it, the fix is better recording, not an exception to the rule.
Do we need a dedicated lead manager?
Not usually in an office under about thirty people. A sales or lettings manager can run the weekly review in half an hour once routing and recovery are automated. Larger offices often give the role to one person across both teams.