Should you cap leads per agent?
The BrokerFold Team — Product + Engineering
Last reviewed
On this page
Yes — but cap the right thing. Capping how many leads an agent receives per month is rationing; capping how many active, unresolved leads they can hold at once is capacity management, and it is one of the highest-leverage rules a routing system can enforce.
The failure mode caps exist to prevent
Uncapped distribution has a predictable ending. The strongest agent converts well, so the rules — or the team lead’s instincts — send them more leads. Their active queue grows past what anyone can work properly; follow-up decays from calls to a drive-by text; and the team’s most expensive asset, fresh leads, goes to the person structurally least able to give them first-hour attention. An agent buried under dozens of active leads isn’t a top producer being rewarded — they’re a bottleneck being fed. Meanwhile the rest of the roster, with empty queues and available hours, watches leads age in someone else’s pipeline. Overload isn’t a discipline problem; it’s an arithmetic problem, and only the routing layer can solve it.
What a capacity cap actually does
A cap makes the routing engine consult workload before assigning: when an agent’s active-lead count sits at their ceiling, they temporarily drop out of rotation and the distribution rules pass to the next eligible agent. Nothing is taken away — the moment the agent dispositions leads (converted, nurture with a date, or closed dead), headroom opens and they rejoin. This creates the most useful incentive in team CRM culture: hygiene becomes the price of inventory. The agent who wants more leads must resolve the ones they hold, which is precisely the behaviour every team lead nags about and no amount of nagging produces.
Setting the ceiling honestly
There’s no universal number, so derive yours instead of borrowing one. Count backward from service: define the touch standard a lead deserves, estimate the minutes it costs, and divide the hours an agent genuinely spends on follow-up. Adjust for support — an agent with an ISA feeding them booked appointments can hold multiples of what a solo caller can — and for lead mix, since a queue of long-term nurtures weighs less than a queue of this-week buyers. Then treat the cap as per-agent and adjustable: uniform caps feel fair and route badly. The evidence for a mis-set cap shows up fast in SLA reporting — chronic misses mean the ceiling is too high; an agent constantly parked at cap with clean follow-up means it’s too low.
Caps need an overflow valve
A team at full capacity still generates leads, and they must land somewhere that isn’t silence. Route true overflow to a shared lead pond where any agent with headroom can claim it, or to a designated overflow agent, or — if overflow is chronic — read it as the growth signal it is: your lead generation has outrun your roster, which is the best recruiting argument a team ever gets. A cap without an overflow path just relocates the place leads die.
Making it stick
Two conditions separate capacity routing from theatre. The counts must be automatic — self-reported workload is fiction within a month — which means the cap lives in the same system that owns routing rules and lead status; on BrokerFold, assignment rules and pipeline state share one CRM, so an agent’s availability is computed, not claimed. And the rule must be published: agents accept losing rotation to a ceiling they knew about and control through their own hygiene. What they never accept is discovering, after a good month, that “the system” quietly decided they had enough.
Frequently asked questions
Won't a lead cap punish my best converter?
A pipeline cap rewards them. The cap doesn't limit how many leads an agent can earn — it limits how many they can hoard while idle. A strong converter who works and dispositions leads quickly cycles through the ceiling faster than anyone and ends up receiving more leads than uncapped rotation would have given them. The only agent a cap constrains is the one sitting on a full queue they aren't working.
What's a reasonable cap number to start with?
Start from touches, not folklore. Decide the follow-up standard a team lead should defend — say, meaningful attempts on fresh leads within the hour and scheduled touches on the rest — and count how many active leads one person can hold to it: for most full-time agents without an assistant that lands somewhere in the few dozen, often around 30–50 active leads. Set the first cap there, then let your SLA data move it.
Do caps still matter on a small team with modest lead flow?
Less as a limiter, more as a circuit breaker. A three-agent team rarely hits steady-state overload, but one great ad month or a big open house can flood a queue overnight. A cap that never triggers costs nothing; the one week it does trigger, it protects the exact leads you paid the most to get.
Keep reading
- Real estate lead routing rules The routing criteria that hold up on Canadian teams, the ones that cause fights, and a starter rule set a five-agent team can write down this week.
- How to distribute leads to agents fairly Fair means transparent rules plus accountability, not equal counts. Round robin, first-to-claim, and performance weighting — and when each is the right call.
- When to reassign leads on a real estate team The SLA windows that should trigger reassignment — by lead type — and how automated timers make forfeiting a lead mechanical instead of personal.
- What is a lead pond in real estate? A shared pool of unassigned or recycled leads that any team member can claim and work. How ponds rescue dying leads, and the rules that make them work.