Leads
Who owns this lead, and what do they do first?
A lead lands at an address. The system finds the territory, picks the next rep in a fair rotation, and gives them their first task. The decision is written down where nobody can edit it.
What it does for you
- Real drawn territory lines, not zip-code guesswork
- A fair rotation that respects each rep's share and skips anyone on pause
- Door-knocking map drops go straight into the live pipeline
- Every open lead carries a next action, or it is not open
What it does not do yet
Nothing on this engine is a design target. What is described above is what runs.
Speed to the first action wins the lead, and a written decision ends the argument.
Status. Shipped. Nothing on this engine is a design target; what is described is what runs.
What it decides
- Which territory the address falls in
- Which rep gets it, on a fair rotation that respects each share and skips anyone on pause
- The first required action and its due time
What goes in
- A name and an address: from a form, a call, a referral or a map drop
- Your drawn territories and each rep's share of the rotation
What comes out
- An owned lead with its first action
- The routing decision, written down where nobody can edit it
What it depends on
- SystemX Actions, which runs the action and its result
- Territories and a rotation you set up once
What it requires
- An address the map can place
- At least one rep in the rotation who is not on pause
What breaks without it
- Leads sit in an inbox with no owner
- Two reps chase the same address
- Nobody can say who got what, or why