Automatic Assignment Rules: The Right Work to the Right Person
Automatic assignment in a CRM: round-robin, least busy, by expertise and portfolio, reassignment rules and out-of-hours handling.
A new lead arrives, a ticket is opened, a call goes unanswered. All of them raise one question: who will handle it? If the answer is “whoever sees it”, then on busy days the answer becomes “nobody”.
Four assignment models
Round-robin
Everyone in turn. Fair and transparent, with good load balance. But it ignores expertise and current load — and needs a check so work does not land on someone who is away.
Least busy
Assigns by open record count, responsive to workload. The risk: whoever closes fastest keeps receiving new work, while a slower but thorough person receives less.
By expertise
To the right person based on the topic tag. Quality is highest here; the risk is single-person dependency. Never use it without defining a backup.
By portfolio
To the customer’s account owner. Best for relationship continuity, and almost the only correct model in enterprise sales — but leave and departure scenarios must be defined.
For most businesses the right answer is not one model but a layered rule: to the portfolio owner if there is one, otherwise by expertise, otherwise to the least busy.
The forgotten half: reassignment
Assignment rules are usually written for the first assignment and left there. Yet the real loss happens with records that are assigned but never worked. A solid setup also covers:
- A time limit: what happens if an assigned record is untouched for X minutes or hours?
- Reassignment: passing it to someone else when the limit expires. This single rule removes most “nobody looked at it” cases.
- Escalation: notifying a manager if the second assignment also stalls.
- Availability checks: nothing should be assigned to someone on leave, offline or outside their hours.
- Capacity limits: how many open records can one person hold? Unlimited assignment hides queued work.
Out of hours and at peak
Assignment rules should be aware of working hours. A lead arriving out of hours should drop into the next morning’s first queue rather than being assigned to sit with someone overnight. Equally, switching from round-robin to least-busy during peaks noticeably reduces waiting times.
Fairness and transparency
Assignment rules the team knows about get accepted; rules they do not know about produce “I always get the hard ones”. Two practices help: keeping the rule written and accessible, and sharing the number of records assigned per person with the team. Transparency buys more peace than the rule itself.
Measurement
- Time from assignment to first touch — as a median, broken down by person.
- Reassignment rate: if it is high, either the time limit is too short or capacity is insufficient.
- Distribution of open records per person: imbalance means the model is not working.
- Unowned records: the target is zero. Anything else means the rule has a hole in it.
Frequently asked questions
Is automatic assignment needed in a small team?
Even with three people, “are you taking this one?” gets asked several times a day. The benefit is not the division of labour but that no record is left without an owner.
Should agents pick their own work?
Self-selection from a pool can raise motivation but risks the easy work being taken first. A hybrid works: hard or priority records are assigned automatically and the rest stay in the pool.
Should the rule vary by customer?
For enterprise customers yes — the portfolio owner takes precedence. For individual customers the first available person is usually faster and sufficient.
Next step: to see how assignment and reassignment rules are defined, request a demo.