Setting up Omni-Channel to route Work Items is a five-piece configuration: enable Omni-Channel, configure Service Channels per record type, set up the routing models and queues, configure agent skills and capacity, and build the supervisor dashboards. Each piece has to align with the others; an admin who enables routing without configuring agent skills produces incomplete assignments, and one who configures skills without setting capacity overloads agents on day one. Walk through all five steps before activating routing in production.
- Enable Omni-Channel and configure Service Channels
From Setup, search Omni-Channel Settings, and enable the feature. Open Service Channels and create a Service Channel record for each object type that should be routable: Case, Lead, Chat Transcript, Voice Call, Messaging Session, custom objects. Each Service Channel record specifies the object type, the related Queue, and the routing configuration to use. Save each channel and confirm it appears in the Service Console agent experience for a target user. Document the channel configuration in the Omni-Channel runbook for future admins.
- Set up the routing models and queues
For each Service Channel, configure the routing model that fits the workload: push for voice and chat, queue-based for email, External Routing if you have a third-party engine. Create a Queue in Setup for each work-distribution group (Sales Tier 1, Service Tier 2, Spanish Speakers). Assign the right users to each Queue. Configure the routing rules that send specific work items to specific queues based on record attributes. Test by creating sample records that match each rule and confirming they route to the expected queue and agent.
- Configure agent skills and capacity
From Setup, Skills, create a Skill record for each functional capability the team has (Spanish, English, Financial Products, Technical Tier 2). Assign skills to agents through Skill Assignment records. Set Service Resource records with each agent capacity per Service Channel. Validate the configuration by running a test routing against a target agent: does the routing engine respect the agent skills and capacity? Audit the skill assignments quarterly; agents change roles and skills drift if not managed actively.
- Build the supervisor dashboards
In Salesforce Reports, build the standard service operations reports: items assigned by hour and channel, agent utilization rate, service level, abandonment rate, average handle time. Bundle the reports into a Supervisor Dashboard that supervisors check multiple times per day. Add real-time queue depth and agent state widgets through the Omni-Channel Supervisor view in the Service Console. Train supervisors on reading the dashboards and acting on the metrics: when queue depth spikes, call in overtime; when agent state shows many Available but no work coming through, investigate the routing rules.
- Capacity tuning is the most consequential Omni-Channel configuration. Over-assignment overloads agents; under-assignment increases customer wait times. Iterate based on actual handle times and quality metrics.
- Skills assignment drifts over time as agents change roles. Audit skill assignments quarterly; without active management, skills-based routing assigns work to the wrong agents.
- External Routing lets a third-party engine drive assignment but adds complexity. For most orgs, push or Most-Available routing is sufficient; only adopt External Routing when the third-party engine adds specific value.
- Work Items can be declined by agents. Excessive decline rates indicate either bad routing (wrong agent for the work) or culture problems (agents avoiding hard work); investigate the root cause rather than just hiding the metric.
- Pending Service Routing records are not directly visible to agents; they see the Work Item through the Omni-Channel widget. Troubleshooting routing issues requires querying the underlying records through Workbench or Developer Console.