Lead buckets & routing
A lead bucket is a named group of leads with a set of agents and/or teams assigned to work them. Where a lead's source tells you how it arrived, a bucket decides who works it — so a brokerage can funnel the right inquiries to the right people without touching every lead by hand.
What a bucket is for
Think of buckets as the brokerage's routing lanes:
- Commercial leads go to the commercial agents.
- Relocation leads go to the relocation team.
- Luxury leads go to the listing specialists.
Each bucket has a name and a roster of assigned agents and/or teams. A lead routed into a bucket becomes visible to the people on that roster (plus brokers and admins, who always see everything).
Buckets add reach — they never hide
A bucket is an access layer, and it only ever adds visibility:
- A lead routed into a bucket becomes visible to that bucket's assigned agents and teams.
- A lead in no bucket keeps its normal visibility.
- A bucket never hides a lead from someone who could already see it. If you owned or could see a lead before, a bucket won't take that away.
So routing a lead into "Relocation" lets the relocation team pick it up; it doesn't pull the lead away from whoever already had it.
Routing a lead
Routing hands a lead to a bucket's people. From the lead — or from the Pipeline board's bucket filter — route it into the bucket that fits, and everyone assigned to that bucket can now work it. Newly arrived, unrouted leads sit under Needs routing until someone claims or routes them.
Who manages buckets
Creating buckets, and assigning agents or teams to them, is a broker, admin, or team-lead task — it's part of setting up how the brokerage distributes new business. Agents see and work the buckets they're assigned to; they don't create them.
Buckets are a Workspace-level setting: they belong to your brokerage, not to a single Realm. The same buckets apply across every lead the brokerage takes in.