The owner-facing distribution manager with three jobs: a status-driven setup checklist (enable → reps → territories → route the backlog), an explanation of exactly how a lead gets routed and how the rep score is weighted, and the configuration itself — master settings plus a per-rep grid with per-row drafts and honest run reporting.
Also called: who gets the lead · round robin · assign leads to reps · territories
- 1Score percentages shown in the explainer are computed from the engine's saved weights, never hardcoded, so the explanation cannot drift from the behaviour.
- 2Territory chips are validated and normalised — states to postal codes, counties suffix-stripped and title-cased, ZIPs to five digits — so chips speak the same dialect the matching engine does.
- 3Per-row drafts mean saving one rep never resets another.
- 4A distribution run renders its full result in a persistent card rather than a transient toast.
- 5Supporting editors cover locations and service areas, territory maps, and an all-reps coverage map.
The header lays out the three jobs and why the first exists: 'so a first-time owner lands on a path, not a wall of controls'. Deriving the score percentages from the engine is explicitly to keep one source of truth. Territory normalisation exists because a chip typed as 'Kane County' and an engine matching on 'Kane' silently routes nothing.
- New-lead assignment was manual and slow.
- Territory text did not match what the routing engine compared against.
- The scoring explanation could drift from the actual weights.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →