CRM playbook: set your lead routing rules

BF

The BrokerFold Team — Product + Engineering

Last reviewed

On this page
A team standup deciding who owns which incoming work

An unrouted lead is a lead beginning to rot — response time only exists once someone owns the response, which is the whole argument of what is speed to lead. Routing rules are how ownership becomes automatic: an ordered list, evaluated top to bottom, first match wins. This lesson is writing that list well.

Step 1: choose a distribution model per rule

Three models, three philosophies. Weighted round-robin shares leads by ratio — a weight of two takes twice a weight of one, with optional monthly caps — and rewards fairness. First-to-claim blasts the lead to a candidate group and starts a fifteen-minute race; contact details stay hidden until someone claims, and an unclaimed lead drops into the shared pond. The pond itself is the third model: a common pool anyone can fish. The trade-offs are argued properly in round robin vs shark tank and first-to-claim leads.

Step 2: write rules you can say out loud

A good rule reads as a sentence: “Listing inquiries under $2M in Oakville go round-robin to Sam at double weight and Priya.” The criteria available — lead source, price band, cities and areas, tags — combine with AND, and a criterion you leave blank simply passes. Rules you cannot read aloud become rules nobody remembers the intent of, and lead routing works best when the whole team understands who gets what and why.

Step 3: always end with a catch-all

One rule at the bottom matches unconditionally and assigns to someone. This is not optional housekeeping — it is the safety net the system is designed around. A rule with a price band deliberately does not match a lead with no price signal; the engine falls through rather than guessing. Without a catch-all, those fall-throughs land unassigned and invisible.

Step 4: keep the human layer honest

Weights and caps are your levers: weight zero pauses an agent inside a rule, a monthly cap stops assignment at an agreed volume, and when every agent in a matched rule is capped or paused, the engine moves on to later rules instead of stranding the lead. Agree on the levers before you set them, and change them in the open — routing decides who gets paid, and surprises here cost trust faster than leads.

Step 5: audit the misses weekly

When nothing assigns, the lead’s timeline says so plainly — no rule matched, or no agent was available. Those notes are your test suite. Sweep them in your weekly follow-up audit and adjust the rule that let each one slip.

What done looks like

Every new lead carries one owner’s name within a minute of arriving, the catch-all sits pinned at the bottom, and a week’s audit finds zero “unassigned” notes without a fix already applied.

The mistake that costs the most

Building elaborate specific rules and skipping the catch-all. The demo looks impressive; then a lead arrives with no price signal, no matched city, and no owner — and the fastest-converting minutes of its life are spent in nobody’s queue.

Frequently asked questions

I am a solo agent — do I need routing rules at all?

One: a catch-all that assigns everything to you. Without it, leads land unassigned and depend on you noticing. With it, every lead gets an owner the moment it arrives, your phone buzzes, and your follow-up numbers stay measurable.

How do I take an agent out of rotation for a vacation?

Set their weight to zero in the rules they appear in — they are paused without being removed, and their history stays intact. Restore the weight when they are back. Monthly caps work the same way for agents who are at capacity rather than away.

Keep reading

Fold your stack into one.

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