When no rep covers a lead's location, the run records a territory-gap row and leaves the lead unassigned. The row's id is derived from the lead, so each lead has at most one gap row ever, refreshed on re-runs. The run report shows the gap count so an owner knows how many leads their coverage map is missing.
Also called: nobody covers this area · lead outside my territory · unrouted lead
- 1Location matching normalises both sides — 'Elkhart County' equals 'Elkhart', 'Indiana' equals 'IN', '46550-1234' equals '46550'
- 2A rep with a territory whose every entry fails normalisation covers nothing, so the misconfiguration surfaces as gaps to fix
- 3Gap rows are upserted on a deterministic id, so re-running the same stuck backlog does not re-spam the log
- 4Gap leads reappear in the remaining count on the next run
Leads whose location nobody covered were being dropped on a text mismatch — Elkhart County against Elkhart, Indiana against IN, a postcode with a four-digit suffix against one without — so leads that were genuinely covered landed in the uncovered pile. Those now normalise before they are compared. A genuinely uncovered lead is recorded once as a gap and left visible for an owner to fix rather than dropped; before, every re-run of the same stuck backlog spawned up to a thousand fresh duplicate gap records and drowned the signal.
- Leads outside coverage silently disappearing
- Spelling drift between lead data and territory setup
- A gap log that grows by a thousand rows every run
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 →