Every new account or lead entering the system gets routed to an owner within minutes, not hours. The agent applies a routing rule hierarchy: first checking if the account is a named account with a designated owner, then matching to the correct territory assignment, then evaluating rep capacity within the territory to avoid routing to reps at the top of their workload limit. Routing rules handle edge cases that break manual processes: what happens when the assigned territory rep is on leave, what happens when an inbound lead matches two territory rules due to a multi-location company, what happens when the lead is from a company already in active pipeline with a different rep. Every routing decision is logged with the rule that triggered it, so assignments are auditable and disputes are resolvable with data.

Ownership changes — rep departures, promotions, team restructures, territory adjustments — create account coverage gaps that persist until someone manually cleans them up, which often takes weeks. Unassigned accounts in active pipeline are one of the leading causes of deal loss that never gets attributed correctly. The agent monitors ownership status continuously and triggers automatic re-routing events when ownership becomes invalid: a rep who leaves has their account portfolio redistributed according to territory rules within the same business day, new territory boundaries are applied to affected accounts immediately rather than in the next quarterly cleanup, and accounts that have been unowned for more than 24 hours generate a management alert rather than silently sitting in limbo.

Territory assignments define the account universe each rep is responsible for — but within a territory, workload can become imbalanced as accounts move through the pipeline at different rates. The agent monitors workload metrics per rep: active account count, accounts in active pipeline, inbound volume by week, and coverage activity density. When a rep's workload score crosses a high-water mark — too many active accounts relative to their capacity based on historical coverage rates — the routing logic adjusts to temporarily direct overflow accounts to lower-workload reps in the same segment rather than stacking more on an already-full territory. Workload balancing prevents the common pattern where some reps are stretched thin while others have the capacity to take more.

Routing rule conflicts are inevitable at scale — an inbound lead from a named account subsidiary, a company that spans two territory boundaries, a lead that matches an SDR's prospecting sequence and an inbound routing rule simultaneously. The agent applies a rule hierarchy to resolve conflicts deterministically rather than randomly or by whichever rep submits a claim first. Conflict resolution logic is configurable and transparent: each conflict is logged with the competing rules, the resolution applied, and the rationale. Sales Ops can review all conflicts in a single view, update the rule hierarchy when patterns reveal systematic gaps, and track conflict frequency by rule type to identify which rule combinations are most error-prone.