Real estate lead routing rules

BF

The BrokerFold Team — Product + Engineering

Last reviewed

On this page
A team standing around a board deciding how incoming work gets assigned

Lead routing rules are the written logic that decides which agent gets which lead, in what order, and what happens when the first assignment fails. Teams argue about splits and titles, but routing is where the money actually moves: a lead sent to the wrong person, or to the right person twenty minutes late, converts like a lead you never bought. Good rules share three properties — they resolve in seconds, every agent can predict them, and every outcome is recorded — and everything else is preference.

The criteria worth routing on

Five filters cover almost every Canadian team. Source: a portal lead, a sign call, and a sold-price registration on your own site carry different intent and deserve different owners. Geography: route by the areas an agent actually services — city or region, not neighbourhood trivia. Price band: a $2M listing inquiry should not round-robin to the newest buyer’s agent, and everyone knows it; making that explicit removes the politics. Language: in most GTA and Metro Vancouver markets, matching a French, Mandarin, Cantonese or Punjabi-speaking lead to an agent who speaks it is the single highest-leverage filter available. Capacity: an agent at a family wedding should be one toggle away from out-of-rotation, because rules that ignore reality get bypassed informally, and informal bypasses are where accountability dies.

The criteria that backfire

Seniority routing — best leads to the longest-tenured — is the most common and the most corrosive, because it converts routing into a status ledger and pushes your hungriest agents to a competitor. Micro-geography fails differently: carving the map into tiny exclusive farms means half your leads land in someone’s “territory” while they’re on vacation. And any rule that lets agents preview a lead before accepting it invites cherry-picking, where the visibly easy buyers get grabbed and everything ambiguous rots. If you want a performance incentive, tie eligibility to measured follow-up — the KPI approach — rather than letting individual leads be judged by eye.

Speed beats precision

A perfectly matched agent who responds in an hour loses to a decent match who responds in ninety seconds; the speed-to-lead research is unambiguous about how steeply response value decays. The practical consequence: your routing logic must resolve instantly and automatically, at 9 p.m. on a Sunday, without a dispatcher. That is also why every rule set needs a failure path. Assignment is an offer, not a burial — if the assigned agent hasn’t responded inside your window, the lead must escalate somewhere visible, whether that’s a first-to-claim pool or the team lead’s phone.

A starter rule set for a five-agent team

Written out, a defensible v1 fits on an index card. Sphere and referral leads: to the named agent, always. Listing inquiries above your luxury threshold: to the listing specialist. Language-matched leads: to the matching agent. Everything else: rotation among eligible buyer agents, where eligible means on-duty and current on follow-up. No response in 15 minutes: open the lead to the whole team to claim. Still unowned after an hour: team lead takes it and it counts as a routing failure to review Monday. Which distribution mechanic fills the “everything else” slot — rotation or claiming — is its own decision, and round robin vs shark tank walks through that trade honestly.

Rules only work where the leads live

Routing logic written in a meeting but executed by a human forwarding emails is theatre. In BrokerFold, capture and distribution are one system: a lead from your site lands in the team CRM in the same transaction, routes to a seat by your rules — rotation or claim-based, with the alert pushed to the agent’s phone — and stamps every hop on the contact’s timeline, so follow-up and Monday’s review read from the same record. Consent is captured at the source with the lead, which keeps CASL out of your nightmares. Nothing about good routing requires our platform; running it without a system is the part that doesn’t work.

Frequently asked questions

Should the team lead keep a share of incoming leads?

Only if the team lead is genuinely working them like everyone else. A rainmaker who claims web leads and then disappears into listing appointments teaches the team that routing is politics. Most healthy teams route the lead's own sphere and referrals to the lead, and put paid-for web leads into the shared system on equal terms.

What happens to a lead nobody is eligible for?

Your rules need a default owner — usually the team lead or an admin — so no combination of filters can strand a lead unassigned. Treat any lead that hits the default bucket as a bug report: it means your criteria have a gap worth fixing that week.

Do routing rules matter below three agents?

Less, but the habit does. A two-agent partnership can route by simple alternation, but writing even that down — with an after-hours answer and a reassignment trigger — prevents the resentment that kills small partnerships when one name starts closing more.

Keep reading

Fold your stack into one.

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