Auto-assign public leads to reps (round-robin)
Distribute new form and portal leads fairly across your team, or a picked pool.
When a lead lands via a public channel — your marketing site's contact form, the portal contact block, an embedded Jeanus form, or a Zap that POSTs into the intake API — someone needs to own it. By default that someone is nobody: the lead sits in the queue unassigned, and any rep can claim it from the leads list.
If you've got more than one rep and want fair distribution, turn on round-robin.
Turning it on
Settings > Lead routing. Switch mode to Round-robin. Either pick a specific pool of reps (checkbox per rep) or leave the pool empty to route to every active rep in your workspace.
The cursor persists on the tenant, so if you deploy or restart the rotation keeps going in order rather than starting from the top. The settings page also shows you the next rep up so you can sanity-check the effect before real leads arrive.
What gets routed
Round-robin only touches public leads. Currently that's:
- Homepage contact / lead-capture forms.
- Portal contact form on your customer portal.
Leads a rep creates from the CRM (from a search, an enrichment, or the pipeline "+ New lead" button) keep the creating rep's code — the router never overwrites an explicit rep.
POST /api/v1/leads) — those integrations usually already know which rep to tag, and the target table uses a different owner schema. Wire this up when the shape stabilises.What the rep sees
The assigned rep shows up on the lead detail header, and the lead is scoped to them for rep-owned or hybrid visibility modes (see Rep-owned vs shared workspace). The rep also gets a bell notification (top-right of the CRM) linking straight to the new lead so they can respond fast.
Turning it off
Switch mode back to Off. New public leads immediately go back to the unassigned queue. Leads that were already routed stay with their assigned rep — the router doesn't retroactively un-assign.