How to set up assignment rules
Assignment rules give every new record an owner automatically. Getting them right means mirroring how your team divides work and handling the edge cases.
The two things people miss are rule order - most specific first - and a fallback so no record is orphaned.
Short answer
Set up assignment rules by deciding what determines ownership (territory, segment, product, account), ordering the rules so the most specific match wins, adding round-robin for even distribution within a group, including a fallback owner, and testing with sample records. Order matters and a fallback is essential, so every record gets a sensible owner and none is stranded.
Step by step
Decide what determines ownership
Choose the attributes that assign records: territory, segment, industry, product, or the owner of a related account.
Order rules specific-to-general
Put the most specific rules first so they win, with broader rules beneath, so records match the most precise applicable rule.
Add round-robin within groups
Distribute evenly among reps in a matched group, respecting capacity, so assignment is fair.
Set a fallback and test
Add a catch-all owner for unmatched records, then test with sample records to confirm they assign as intended.
Order and fallback are what people miss
Two failure modes dominate assignment rules: rules in the wrong order (a broad rule fires before a specific one, so records land generically) and no fallback (unmatched records sit ownerless). Order specific-to-general and always include a catch-all, and assignment stays reliable.
How Ardovo helps
Ardovo applies ordered assignment rules with round-robin and a fallback, and previews how sample records would assign. Rook enriches records first so rules match accurately, and rebalances as your team and territories change, so ownership stays fair and current.
Frequently asked questions
Why does the order of assignment rules matter?
Because records usually match the first applicable rule, so a broad rule placed before a specific one fires first and assigns generically. Ordering rules from most specific to most general ensures each record matches the most precise applicable rule rather than a catch-all.
Do assignment rules need a fallback?
Yes. Some records match no specific rule, and without a fallback owner they sit unassigned and ignored. A catch-all rule ensures every record lands with someone, so nothing is stranded while you refine the more specific logic.
How do you test assignment rules?
Run sample records representing your common and edge cases through the rules and confirm each assigns to the intended owner. Testing catches ordering mistakes and gaps before real records route wrong, which is far cheaper than discovering the problem in production.