Real estate lead routing

BF

The BrokerFold Team — Product + Engineering

Last reviewed

Team members reviewing lead assignment numbers together

Lead routing is the answer to a question every team eventually asks in anger: who was supposed to call this person? It is the set of rules that takes each new lead — form fill, listing inquiry, tour request, valuation — and puts it in exactly one agent’s hands within seconds, with a record of why. Teams that treat routing as an afterthought pay for the same lead twice: once to generate it, once in the deal that dies unworked.

The three models, honestly compared

Every routing system in the industry is some arrangement of three primitives:

  • Rotation (round-robin). Leads cycle through the roster in turn, optionally weighted so a producer draws a larger share or a new agent ramps up gradually. Strength: provable fairness that survives roster arguments. Weakness: rotation doesn’t check whether the next agent in line is at a kitchen table signing a deal.
  • Claim races (first-to-claim). New leads are offered to a group; the first agent to hit claim wins, within a countdown window. Strength: it selects for availability and hunger at the exact moment the lead is hot. Weakness: unmanaged, it rewards the fastest thumb and can starve part-timers.
  • The shared pool (pond). Unclaimed and overflow leads sit where any agent can pick them up, with the claim locking the person so two agents can’t collide. Strength: nothing falls on the floor. Weakness: pools without review cadence become graveyards.

The mature answer is a blend, expressed as rules: claim races above a price band where speed justifies competition, weighted rotation for the steady middle, and the pool for off-hours and reactivation. Pick one arrangement, write it down where the roster can read it, and change it deliberately when the roster changes — the model matters less than everyone knowing what it is. The fairness dimension of that design has its own treatment in how to distribute leads to agents fairly.

Rules do the real work

Models decide how a lead is assigned; rules decide which leads go where. Useful segmentation is usually simpler than teams expect: source (your site’s organic leads may deserve different handling than paid traffic), geography, price band, and language cover most real rosters. Two disciplines matter more than clever rules. First, returning leads should never re-enter the wheel — a person who inquires again belongs to whoever already owns the relationship, and the owner should be told “they’re back.” Second, every rule needs a default: a lead that matches nothing must land somewhere visible, not in a silent gap between conditions.

Seconds to assign, minutes to call

Routing exists in service of speed to lead — assignment is worthless if the assignee finds out at lunch. In BrokerFold, the routing engine runs assignment first in the capture chain and fires push, bell and email to the winning seat immediately, so the clock that matters — lead-exists to human-knows — runs in seconds. Automated first-touch buys the agent time to get to a phone; it never replaces the call.

The audit spine

The underrated half of routing is proof. Every hop is recorded — the rule that matched, the mode that ran, who claimed what, when — which turns three chronic team arguments into lookups: who got what, who answers fastest, which sources are worth their invoice. Put your own figures into the lead ROI calculator and the case sharpens: at typical Canadian lead costs, the margin between a profitable program and an expensive hobby is rarely the leads — it’s how reliably they reach a human who calls. Routing is that reliability, written down as rules and enforced by software.

Frequently asked questions

Does a solo agent need lead routing?

No — and a good system knows it. Solo, every lead simply arrives with an instant notification. Routing becomes necessary the day a second agent joins, because 'we both watch the inbox' is where leads go to die.

Which routing model converts best?

The one your roster will actually honour. Rotation wins where accountability is strong, claim races win where hunger outruns process, and most mature teams blend them — competitive assignment for premium leads, rotation for steady flow, a shared pool for overflow.

How fast should a routed lead be contacted?

Minutes, not hours. Routing itself should take seconds — the assignment plus the notification — so the human window is everything after the ping. Teams that pair routing with a response-time report see exactly who honours the SLA.

Keep reading

Fold your stack into one.

14 days free. No credit card. Your data stays yours.