A routing rule that actually respects territories

Round-robin routing has one job — spreading leads evenly — and it does that job so well that it will happily hand your largest open opportunity in Germany to whichever rep is next in line, even if they started on Monday and have never sold into the DACH region.

In onboarding sessions, this is the routing problem teams bring up most often. The fix isn't a smarter round-robin. It's routing that checks ownership first and only falls back to rotation when there's no clear owner.

Why a smarter round-robin isn't the fix#

The tempting approach is to build one clever rule: blend territory fit, rep capacity and queue depth into a single score and send the lead to whoever scores highest. It sounds sophisticated. In practice it produces exactly the outcome you were trying to avoid, because a weak territory match can still lose to a strong capacity score — and your enterprise account in Munich ends up with someone in Toronto.

Blended scores are also hard to explain. When a rep asks “why did this lead go to Marcus?”, the answer should be one sentence, not a weighted formula.

Sequence, not blend. Ownership rules run first, rotation runs last.

The two rules, in order#

Aurora evaluates routing rules from top to bottom and stops at the first match. That makes a simple, predictable structure possible:

Rule 1 — territory owner#

If the account maps to a territory, route it to that territory's owner, regardless of how busy they are. We define territories once under Routing → Territories:

Existing customers and open opportunities should sit even higher: a rule above the territory rule that routes to the CRM account owner whenever one exists. That way expansion signals from a current customer always reach the person who already knows them.

Rule 2 — everything else#

Anything without an owner — new markets, unassigned regions, self-serve signups with no clear geography — goes into ordinary round-robin across the full team. If your team mixes senior and junior reps, use weighted round-robin (for example 40 / 30 / 30) rather than an even split.

1. CRM account owner exists      → assign to CRM owner
2. Territory match                → assign to territory owner
3. Score ≥ 80 and size ≥ 200      → weighted round-robin (senior pool)
4. Everything else                → round-robin (whole team)

Handling overflow and time off#

Territories get busy unevenly, and people go on holiday. Two settings keep the rules strict without leaving leads stranded:

• Availability. When an owner marks themselves out of office, Aurora skips them and moves to the next matching rule — for territories, we recommend a named backup, such as Sofia covering DACH while Lena is away.
• Daily limits. If an owner hits their daily alert limit, additional leads go to the shared inbox rather than being reassigned silently. A manager can then decide whether to hand them out or hold them for the owner.

What changed when we switched#

We moved our own sales team to this setup in early 2026. Over the following quarter, the share of qualified leads reassigned manually after routing fell from about 22% to under 4%, and the median time from qualification to first touch dropped from 3.1 hours to 47 minutes — mostly because reps stopped second-guessing whether a lead was really theirs.

Testing before you switch#

Routing changes affect people's pipeline, so test them before they go live. In Aurora, choose Test rules above the rule list and pick any recent visitor: you'll see which rule would match, who would be assigned and where the alert would go, without sending anything. Run it against ten or fifteen of last month's best leads and check that every one lands where your team expects.

The routing documentation covers every assignment method, destination and setting mentioned here.