Good assignment design pays back over years. Bad assignment design produces "who owns this lead" tickets every week. The pattern below favors declarative-first, Queue-mediated, with clear escalation; it works for most orgs and only needs the more advanced patterns (ETM, Omni-Channel) when the basic pattern hits scale limits.
- Map the assignment decisions per object
For each assignable object (Lead, Case, Account, Opportunity), document the inbound channels, the routing criteria, the target user or queue, and the SLA. The map is the input to every other step.
- Build Queues for shared ownership before specific reps
Public-Group-backed Queues per team. Inbound records assign to the Queue; reps accept from the Queue when they pick up the work. The Queue pattern survives org-chart changes.
- Configure Assignment Rules for declarative routing
Setup, Object Settings (Lead, Case), Assignment Rules. Build one active rule per object. Order entries by specificity; first match wins. Skip the Round Robin pattern here; use Flow for that.
- Use Flow for Round Robin and capacity-aware routing
Round-Robin Lead assignment, capacity-aware case routing, holiday and PTO logic. Flow handles these patterns more cleanly than Assignment Rules and is easier to maintain.
- Evaluate Omni-Channel for high-volume routing
Service Cloud teams with 1,000+ cases per day benefit from Omni-Channel's capacity model. Lead-routing teams with similar volume should evaluate Sales Engagement or third-party.
- Document the reassignment policy
Account Owner cascading behavior, Lead reassignment timing, Case reassignment via Quick Action. Document so reps know what to expect when ownership changes.
- Audit assignment quality quarterly
Pull a report of records assigned to the wrong owner, records sitting in queues past SLA, records assigned to inactive users. Each is a routing issue that compounds over quarters.
Manual, Assignment Rule, Queue-based, Round Robin, Territory, Omni-Channel. Layer to fit the use case.
User, Public Group, or Role. Public Group is the most flexible and survives org-chart changes.
Whether related records follow on owner change. Configured in Account Settings; document the choice.
Whether assignment considers rep skills or current workload. Omni-Channel for skill-based at scale.
Per-Assignment-Rule-entry toggle. On for high-SLA records, off for low-touch.
- Only one Assignment Rule per object can be active at a time. Reorganizing routing requires editing the active rule or deactivating and replacing it.
- Queue membership through Roles breaks on org-chart changes. Public Groups survive; Roles do not.
- Bulk reassignment triggers sharing recalculation that can block other org activity. Schedule for off-hours for reorgs and mass owner changes.
- Assignment Rules and Flow can both modify OwnerId in a save context, producing race conditions if both fire. Pick one mechanism per object per scenario.
- Records assigned to inactive users persist with the inactive user as owner. Schedule a quarterly audit of records owned by inactive users and reassign.