A brokerage running four lead sources — paid search, a listing portal, an in-house referral network, and a Facebook ad campaign — has a routing problem hiding inside its growth numbers. Leads come in around the clock, agents have different availability windows, and nobody built explicit rules for who gets what. The result is that the highest-cost lead, the one from paid search at 9 p.m., sits in a shared inbox until a morning agent logs in the next day.
Where the breakdown usually lives
Most teams default to a round-robin distribution. One CRM admin sets it up, it runs for a year, and nobody revisits it. Round-robin is neutral, which is another way of saying it is indifferent — it does not know that Agent A closes paid search leads at twice the rate of Agent B, that Agent C does not work weekends, or that the referral leads from a specific partner almost always ask about a narrower price range that Agent D focuses on.
Say a team gets 40 leads a week across those four sources. If 10 of those come in after 7 p.m., and only one agent has agreed to be on evening call, then the 9 other agents in the round-robin absorb leads they will not act on until morning. The contact opportunity is gone. The lead does not know that — they submitted a form expecting a human response.
From Real Estate AI Group
Want this built for your team?
A 30-minute call is enough for us to tell you what's realistic — no obligation, no generic pitch deck.
Book a callWhat a routing workflow actually does
A routing workflow sits between the lead source and the CRM assignment. It reads a small set of inputs before it assigns: source, time of submission, agent availability status, and any qualifying data the lead form captured (price range, buyer or seller, zip code, language preference). With those inputs, it applies a decision tree that the brokerage controls.
A working version of this might look like: leads from the paid search campaign during business hours go to two agents who have agreed to a 5-minute response commitment; leads from that same source after 7 p.m. go to a single on-call agent or, if no one is marked available, trigger an AI text agent to hold the conversation until a human picks it up in the morning. Referral leads from one specific partner always go to a single agent who has an existing relationship. Portal leads get routed by the zip code field.
The workflow does not guess. It follows the rules the brokerage defined. If no rule matches, it defaults to a designated fallback agent and creates a task to review why the rule set did not cover the case.
Building it without replacing your CRM
The integration point is usually a webhook or a Zapier/Make step between the lead source and the CRM. Most CRMs used in residential brokerage — Follow Up Boss, kvCORE, Chime — have an API or native webhook that accepts a new contact with an assigned owner. The routing logic sits upstream of that assignment step.
The practical build order is: map every active lead source, list every active agent and their documented availability window, write the routing rules in plain English before touching any tool, and then build the workflow to match those rules exactly. Skipping the written rules step and going straight to the tool is the most common reason these builds fail — the workflow ends up encoding whatever the person building it assumed, not what the brokerage actually wants.
Audit first. Know what you have before you automate it. That is the only way to avoid spending three weeks building a workflow that enforces a broken process faster.
What changes after it runs
The most immediate change is visibility. A routing log shows, per lead source, per agent, per time window, exactly where every lead went and when. A brokerage that has never seen that data before often discovers that one agent has been getting 30 percent more leads than anyone else because they were always first in the round-robin queue, not because they are the best fit.
The second change is accountability. When routing is explicit, an agent cannot say they did not get the lead. The log shows the assignment timestamp, the notification sent, and when the first contact attempt happened. That data is useful for performance conversations and for refining the rules over time.
Where to start
List your four or five highest-volume lead sources and ask, for each one: who should get this lead, during what hours, and what happens if that person is unavailable. Write those answers down before opening any workflow tool. That document is your routing spec, and it is the most valuable thing you can bring to anyone you ask to build this for you.