Platform / Lead routing
Routing that cannot overwrite a person.
Territory rules decide who owns an account the moment a contact is created, imported or merged, and every lead at that company inherits that owner. The write only ever fills an empty owner, so a rule can never take an account off the rep a manager put there.
Included at $499 per seat per month
How an account finds its rep
priority order, first match wins
name in your named list
employee_count gte 1000
location contains boston
employee_count between 50 and 999
When no rule matches
Territories are evaluated lowest priority number first and the first rule that matches ends it. Nothing below the match is looked at, so a specific territory placed above a broad one always takes the account.
How it runs
Lead routing that is automatic at the account, and a plan you apply at the lead.
Two things here assign work, and a routing page is exactly where a vendor blurs them together. Territory rules really do fire on their own, inside the same request that created the record. Lead level distribution does not: it hands a manager a plan and waits. Both are useful and only one of them is automatic.
automatic
Territory rules, at the account grain
Runs inside the write that created the record, on eight paths: a contact created, updated or merged, a CSV import, the public API, and three campaign audience imports. The account gets an owner and a territory, and every lead at that company inherits the owner when it is created.
preview, then apply
Round robin and least loaded, at the lead grain
This one does not write on its own, and we would rather say so than let you find out later. A manager asks for a plan across up to fifty unassigned leads, sees which rep each one would go to and why, and applies it. Until that click, no lead has an assignee.
Then it ranks what landed
The score is stored on the contact and the database refuses anything outside 0 to 100, so it cannot drift into a number nobody can interpret. Speed to lead is measured against a five minute target and reported in its own view, with tiers at five minutes, thirty minutes and twenty four hours. It is a mirror, not an alarm: nothing in the product pages a rep when the clock runs out.
One hundred points, five ways to earn them
hot at 75
- Email engagementmax 25
- Company fitmax 25
- Behavioural signalsmax 20
- Decision-maker levelmax 15
- Recencymax 15
A perfect engagement record on its own is worth 25, which is cold. Hot needs three factors to agree, which is the point of capping each one: nothing gets to the top of a rep's list on a single loud signal.
A score that ages on purpose
half life, 30 days
Thirty quiet days halve the score, sixty quarter it. Without that, the top of a queue slowly fills with leads that were interesting last quarter, and the ranking stops being a ranking.
Why this is different
The category reassigns and apologises. This refuses to.
Routing is where a CRM quietly does damage. A rule fires, an owner changes, and the rep discovers it from a calendar invite for a meeting that is no longer theirs. Here the assignment is a guarded write that can only fill an empty owner, so the entire sweep is safe to re-run and every decision a person already made survives it untouched.
How the category behaves
The rule is the authority. An owner somebody set by hand gets replaced, and it falls to a person to notice and put it back.
SAGARIS
The person is the authority. An account that already has an owner is not a row the write can match, so the rule passes over it and nothing changes.
update accounts set owner_id where owner_id is null
That clause is the whole promise. It is part of the statement rather than a check performed first, which is what makes it hold under a race and what makes re-running the sweep a non-event.
A guard, not a good intention
The condition travels inside the update rather than running before it. There is no window between checking that an account is unowned and writing to it, which is why a manual assignment made at the same instant cannot lose the race.
Safe to run again, and again
Sweep the unassigned queue as often as you like. Anything already owned is skipped, and the round robin cursor advances by how far the batch moved instead of being overwritten, so concurrent runs add up rather than collide.
Ownership lives on the company
Once an account belongs to a rep, every lead at that company inherits that owner as it is created. Two reps do not end up working the same building because two enquiries arrived through different doors on different days.
The questions buyers actually ask.
- MOST ASKED
Territory routing is. Rules evaluate on eight write paths, including a contact created in the app or through the public API, a contact update, a merge, a CSV import and three campaign audience imports, and the account is assigned inside the same request. Lead grain distribution is not automatic and we will not imply otherwise: round robin and least loaded produce a plan a manager reads and applies, and nothing is assigned until they do.
Bring your territories. We will run them on your accounts.
Any routing tool looks correct on a demo list. Bring the rules you use today and a real slice of your accounts, and we will show you which territory each one lands in, which rule matched it, and which ones nothing matched at all. That last group is the one worth seeing before you buy anything.