Salesforce Omni-Channel is the intelligent work routing and agent presence management system within Service Cloud – it automatically assigns Cases, chats, messaging sessions, and voice calls to available, appropriately skilled agents without supervisor triage. Instead of agents manually claiming cases from a queue, Omni-Channel pushes work to agents in real time based on their availability, capacity, and skill set. This guide covers the complete Omni-Channel setup: Service Channels, Routing Configurations, Presence Statuses, Queue integration, and the Omni-Channel Supervisor dashboard for real-time operations management.
The best guide is the one that makes assignment feel orderly.
A useful explanation should help the reader understand where routing fits in the support process.
That means the guide should focus on workflow control rather than configuration language alone.
For many teams, the value is in reducing delays and making handoff decisions more predictable.
It should also show how routing improves responsiveness when many requests are coming in at once.
A good guide should explain what the routing system is meant to solve and why assignment logic matters.
That makes routing part of the operational backbone of the CRM.
Salesforce Omni-Channel Routing is useful because support and sales teams often need work directed to the right person without manual triage. It helps route items based on rules so the team can respond more consistently.
How Omni-Channel Works
The Omni-Channel routing flow:
- A work item (Case, Chat, Messaging session) is assigned to a Salesforce Queue via Case Assignment Rules
- Omni-Channel monitors the queue and identifies available agents who have the appropriate Routing Configuration for that queue
- Omni-Channel selects an available agent based on the routing model (least active, most available, or skills-based) and pushes the work item to their Omni-Channel widget
- The agent accepts or declines the work – declined items go back to the queue and are routed to the next available agent
- When the agent accepts, the Case (or chat, or call) opens automatically in their Service Console workspace
The agent’s availability is managed through Presence Status – agents set themselves to Available when ready to receive work and to Busy or Away when not. Omni-Channel only routes to agents in an Available status for the relevant channel.
Component 1: Service Channels
A Service Channel represents a type of work that Omni-Channel routes. Create a Service Channel for each work type your support team handles.
Setup, then Omni-Channel, then Service Channels, then New:
- Label: the display name (e.g., Support Cases, Live Chat, Email Enquiries)
- Salesforce Object: the Salesforce object this channel routes (Case, LiveChatTranscript, MessagingSession, Voice Call)
- Capacity Weight: how much agent capacity this work type consumes per item. A voice call typically consumes the agent’s full capacity; a chat consumes partial capacity; a case may consume less than a real-time channel. If an agent has capacity of 10 units and a Case has weight 1, the agent can handle 10 simultaneous cases.
Standard Service Channels to create for most B2B support operations:
- Cases – routing email-originated and web-originated cases
- Live Chat – routing chat sessions from your website
- Messaging – routing WhatsApp, SMS, and Facebook Messenger sessions (if using Salesforce Digital Engagement)
- Voice – routing inbound calls (if using Salesforce Service Cloud Voice)
Component 2: Routing Configurations
A Routing Configuration defines how work should be assigned when routed through a specific channel and queue combination.
Setup, then Omni-Channel, then Routing Configurations, then New:
- Routing Priority: a number (1 = highest priority). If an agent can receive multiple work types, higher-priority work is pushed first. Set Voice to Priority 1, Chat to 2, Cases to 3 – ensuring real-time channels are staffed before asynchronous.
- Routing Model: Least Active routes to the agent with the fewest open work items (distributes work most evenly across the team); Most Available routes to the agent with the most remaining capacity.
- Capacity Weight: set at the Routing Configuration level to override the Service Channel default – useful for high-complexity queues where each item should consume more agent capacity.
Component 3: Presence Statuses
Presence Statuses define what states agents can set themselves to – and which Service Channels they are available for in each state. Setup, then Omni-Channel, then Presence Statuses, then New:
- Status Name: what the agent sees in their Omni widget (e.g., Available – All Channels, Available – Chat Only, Break, End of Shift)
- Status Options: Online (available to receive work) or Busy (available but at capacity – no new work pushed)
- Service Channels: which channels this status enables receiving work on – an Available – Chat Only status might only have the Live Chat service channel selected, so agents in that status only receive chat items
Component 4: Queues and Routing
Omni-Channel routes work from Salesforce Queues to agents. Connect a Routing Configuration to a Queue to enable Omni-Channel routing for items in that queue. Setup, then Queues, then edit the queue and add the Routing Configuration in the Omni-Channel section. Then, configure your Case Assignment Rules to route cases to the appropriate queue based on criteria – by product, region, priority, or language.
Skills-Based Routing
Beyond queue-based routing, Omni-Channel supports Skills-Based Routing – routing work items to agents with specific skills rather than (or in addition to) queue membership. This is particularly powerful for multi-product or multi-language support teams.
To configure Skills-Based Routing:
- Setup, then Omni-Channel, then Skills – create Skills for each competency (e.g., Product A Expert, Spanish Language, Enterprise Tier)
- Assign Skills to agents via User records – each agent can have multiple skills, each with a proficiency rating (1-10)
- Configure Routing Configuration to use Skills-Based Routing and define the skill requirements for each queue
- Optionally configure Skill Relaxation: if no agent with all required skills is available within a defined wait time, Omni-Channel progressively relaxes skill requirements until it can route the work item
Omni-Channel Supervisor Dashboard
The Omni-Channel Supervisor tab provides real-time visibility into routing operations – it shows every agent’s current status, capacity utilisation, queue depths, and wait times. Supervisors can:
- Transfer work items between agents if a particular agent is overwhelmed
- Force-close or reassign stuck work items
- Change an agent’s presence status if they have stepped away without updating their status
- Monitor queue depth in real time – if a queue is building up, the supervisor can open the relevant skill set or pull in additional agents
Omni-Channel for Einstein AI and Agentforce Integration
In 2026, Salesforce has extended Omni-Channel to route work to Agentforce AI agents as well as human agents. When an AI agent is configured in your org, it appears as a routing target in Omni-Channel – incoming cases and messaging sessions can be routed to the AI agent first, with automatic escalation to a human agent if the AI cannot resolve the issue.
To configure AI-to-human escalation: in your Agentforce agent configuration (Setup, then Agentforce, then Agents), define the escalation trigger conditions – for example, when the customer asks to speak to a human, when the conversation sentiment score drops below a threshold, or when the issue category is flagged as requiring human handling. The Omni-Channel escalation transfers the full conversation transcript to the human agent’s workspace, so the agent has full context without asking the customer to repeat themselves.
The key metric to monitor for AI-to-human routing is containment rate – the percentage of conversations handled by the AI agent without escalation. A well-configured Agentforce deployment with a robust Knowledge Base and clear escalation rules typically achieves 40-60% containment for common support queries, reducing human agent workload proportionally.
Does Omni-Channel work with Salesforce Classic?
Omni-Channel is supported in Salesforce Classic as well as Lightning Experience, but the full feature set – including the Omni-Channel Supervisor dashboard, Skills-Based Routing, and Agentforce AI routing – is available only in Lightning. Salesforce strongly recommends migrating to Lightning Experience before implementing Omni-Channel, as Classic support is limited and the user experience for agents is significantly better in the Lightning Service Console. The Omni-Channel widget in Lightning provides a real-time work queue, presence status toggle, and capacity indicator in the footer of the Service Console – Classic users see a simpler work notification without the same management interface.
What is the difference between Omni-Channel routing and case assignment rules?
Case Assignment Rules determine which Queue a case is assigned to when it is created – they evaluate case criteria (priority, product, origin, customer segment) and assign the case to the appropriate queue. Omni-Channel routing then takes over from the queue: once a case is in the correct queue, Omni-Channel determines which specific agent within the queue receives the case based on availability, capacity, and routing model. Case Assignment Rules and Omni-Channel are complementary, not alternatives. Without Assignment Rules, all cases go to one queue; without Omni-Channel, agents must manually pick cases from the queue. Together, Assignment Rules route work to the right team and Omni-Channel routes work to the right agent within that team.
How do you handle after-hours routing with Omni-Channel?
Omni-Channel does not have native business hours routing, but you can implement it using Flows. Create a Before-Save Flow on the Case object that runs when a case is created: if the current time is outside your defined business hours (using a custom metadata type to store hours by day), update the Case’s queue assignment to an After-Hours queue that is not monitored by Omni-Channel – instead triggering an auto-response email and setting a callback SLA. For organisations using Salesforce Service Cloud Voice or Digital Engagement messaging, configure business hours directly in the channel settings, which will queue or deflect contacts outside hours without needing a custom Flow.
Can Omni-Channel route to external systems or third-party agents?
Omni-Channel routes within Salesforce – it cannot natively route work items to external systems or agents not licensed in Salesforce. However, you can use the Omni-Channel Open CTI framework to integrate with external telephony platforms (such as Genesys, Avaya, or Amazon Connect via Service Cloud Voice) that handle their own routing. In this architecture, Salesforce Omni-Channel manages digital channel routing (cases, chat, messaging) while the telephony platform manages voice routing – both surfaces in the agent’s Service Console. For organisations that need a unified routing engine across Salesforce and non-Salesforce channels, MuleSoft or a third-party customer engagement platform is required to bridge the systems.
Problem: Cases Are Not Being Routed – Stuck in Queue
The most common Omni-Channel issue is cases sitting in a queue without being pushed to agents. The diagnostic checklist: first, verify that agents have a Presence Configuration assigned (Setup, then Omni-Channel, then Presence Configurations – assign the relevant configuration to agent user profiles). Second, confirm that agents are actually setting themselves to an Online presence status in the Omni-Channel widget in their Service Console – if they are not logged into the widget, they receive no work. Third, check that the Queue is connected to a Routing Configuration (Setup, then Queues, then edit the queue – confirm Omni-Channel Routing Configuration is populated). Fourth, verify that the Routing Configuration’s Capacity Weight does not exceed the agent’s configured capacity – if the weight is 5 and the agent’s capacity is 4, no work will route to that agent. Adjust capacity settings at Setup, then Omni-Channel, then Presence Configurations.
Problem: Work Is Not Being Distributed Evenly Across Agents
If one agent consistently receives significantly more work than others, the routing model configuration is likely the cause. The Most Available routing model sends all new work to the agent with the highest remaining capacity, which creates a pattern where the fastest case-closer is constantly assigned new work while slower agents sit idle. Switch to the Least Active routing model: edit the Routing Configuration (Setup, then Omni-Channel, then Routing Configurations, then edit) and change Routing Model to Least Active. This distributes work based on open item count rather than remaining capacity, creating fairer distribution. Additionally, check whether any agents have significantly higher capacity settings than others – if one agent has capacity 20 and another has capacity 5, the high-capacity agent will receive disproportionate volume even with Least Active routing. Standardise capacity settings across agents on the same team unless specific agents are designated as high-volume handlers.
Problem: Agents Receiving Wrong Channel Work Type
Agents occasionally report receiving chat sessions when they expected to only handle cases, or vice versa. This occurs when Presence Status configurations are overly broad – an Available status with all Service Channels enabled means the agent receives every type of work regardless of their actual channel assignment. The fix is to create distinct Presence Statuses for each channel combination your team uses (for example, Available – Cases Only, Available – Chat and Cases, Available – All Channels) and assign only the appropriate Service Channels to each status. Update the Presence Configuration for each team or role to include only the statuses relevant to that team’s function. Document the status options available to each team in your agent onboarding guide – agents often set themselves to overly broad statuses because they do not understand the channel implications.
The best routing setup is the one that sends work to the right place quickly. If the rules are vague, the queue becomes harder to manage.