Lead Routing & Assignment
Decides which agent a visitor is credited to when they browse listings on a team site.
- Built for
- Team lead / brokerage owner
- Also for
- Working agent (receives the routed leads)
What it does
Decides which agent a visitor is credited to when they browse listings on a team site. The broker picks one of three attribution methods: first agent viewed, last agent viewed, or no agent. The choice controls who is attached to the lead when it reaches the CRM.
Key capabilities
- First-touch attribution: the lead goes to the first agent whose listing the visitor viewed
- Last-touch attribution: the lead goes to the most recent agent whose listing the visitor viewed (the default for new accounts)
- No assignment: leads reach your CRM without an agent, so your CRM's own rules decide who gets them
- An agent with their own site always keeps the leads captured on it
- One setting under Website settings
Good to know
- There is no default-agent picker and no custom rules. Round-robin and capacity-aware routing are not built in
- The first/last choice only matters when more than one agent has listings on the site
- Changing the method affects future visitors only; visitors already attributed to an agent keep that agent
- Leads captured on an agent's own site stay with that agent, even with no assignment selected
Why teams choose this
-
Credit goes to the agent whose listings the visitor actually browsed, first or last, whichever the brokerage prefers
-
Teams whose CRM already distributes leads can switch assignment off so nothing arrives pre-assigned
-
Agents with their own site keep their own leads
See Lead Routing & Assignment in your stack
Live demo, no commitment. We'll show you how this fits with HighLevel, Follow Up Boss, and your MLS.