Assignment Rules You Control: Route by Skill, Priority, Territory, and Capacity
Routing should follow your logic, not a vendor default. Assigner gives you assignment rules you fully control, layered conditions that route by skill, priority, territory, and capacity, so leads, tickets, and tasks land where you have decided they should.
In short
Lead assignment rules are the conditions that decide which person or team receives each incoming lead, based on factors like territory, source, deal size, skill, priority, and current capacity. In Assigner, these rules are the control surface: you build them from plain conditions and layer them in the order you choose, so a rule might send enterprise leads in North America to senior reps who have open capacity, and fall back to a round-robin for everything else. The same rule engine assigns support tickets and ops tasks, so one place governs how all your work is distributed rather than separate settings in three tools. You can change a rule any time, and nothing routes on hidden logic: every assignment shows which rule fired and why. RevOps tools like LeanData build powerful rules but lock them to Salesforce or HubSpot and start around $15,000 a year; Assigner keeps the rules yours and stack-agnostic from $12 per user. Assigner is designed to apply your rules consistently, not to override your judgment; the AI assists and the rules stay under your control.
What you get
Assignment rules, built for support, sales, and ops teams
Your logic, layered
Build rules from plain conditions and stack them in the order you choose, so complex routing follows exactly how you think.
One rule engine for all work
The same rules that route leads also route tickets and ops tasks, so you govern distribution from one place, not three tools.
Change rules any time
Adjust conditions, reorder them, or add a fallback whenever your team, territories, or priorities shift, with no vendor ticket.
Nothing routes in the dark
Every assignment shows which rule placed it, so you can audit, trust, and refine the logic rather than guess at it.
How it works
From incoming work to the right available person, in four steps
Define your conditions
Set the factors that matter: territory, source, deal size, skill, priority, and capacity, in whatever combination you use.
Layer rules in order
Order your rules so the most specific fire first and a sensible fallback catches everything else.
Assigner applies the rules
Each incoming lead, ticket, or task is matched against your rules and assigned to the right available person.
Audit and refine
Every decision shows the rule behind it. Review outcomes and tune conditions to keep routing sharp over time.
Questions buyers ask
Frequently asked questions
What are lead assignment rules?
Lead assignment rules are the conditions that decide who receives each incoming lead. A rule matches attributes such as territory, source, industry, deal size, or language, and assigns the lead to a named person, a team, or a queue. Rules are evaluated in order, and the first one whose criteria match usually wins, with a fallback owner catching anything that matches nothing.
How do you write a good lead assignment rule?
Start with the most specific rule and end with a catch-all fallback, because a lead that matches no rule is a lead nobody owns. Use few conditions per rule so you can explain it later, keep territory and segment definitions in fields rather than in people heads, and decide up front what happens when the matched person is unavailable.
Why are my assignment rules not working?
The four usual causes are order, scope, triggering, and availability. A broader rule sitting above a specific one absorbs the leads first. The rule criteria do not match the data actually arriving. The rule never fires because the record was created by an import or API call that skipped the trigger. Or it fires correctly and assigns to someone who is out, so the lead looks stuck.
Can assignment rules route by capacity?
Native CRM assignment rules generally cannot. They evaluate static field criteria, so they cannot see how much open work a person already holds or whether that person is on shift today. Assigner layers capacity and availability on top of your rule logic, so a rule can require both a skill match and room to take the work before it assigns.
How many assignment rules should a team have?
Fewer than you think. Rule sprawl is the most common failure in mature setups: dozens of overlapping rules that nobody can reason about, often sharing one invisible rotation order. Aim for a small set of specific rules plus a fallback, and express variation such as seniority or ramping through weights rather than through additional rules.
Stop hand-sorting your incoming work
Let Assigner route every ticket, lead, and request to the right available person by skill, workload, and availability, using rules you control. Every assignment shows why. Works beside the tools you already use, no black box.