Omni-Channel Routing
A Service Cloud feature that automatically routes incoming work items (cases, chats, leads, custom objects) to the most appropriate available agent based on agent capacity, skills, and routing configuration.
Definition
A Service Cloud feature that automatically routes incoming work items (cases, chats, leads, custom objects) to the most appropriate available agent based on agent capacity, skills, and routing configuration.
In plain English
“Omni-Channel Routing is the Service Cloud feature that automatically routes incoming work items (cases, chats, leads, anything) to the most appropriate available agent. It considers agent capacity, skills, and routing configuration so the right work goes to the right agent.”
Worked example
Ramelow Mining's contact center uses Omni-Channel Routing to distribute incoming work - chat, email, voice - across 80 agents. The routing engine considers each agent's current capacity (each chat counts as 1 unit, an email as 0.5, a call as 3), their skills (Spanish-speaking, mining-equipment specialist, hazmat-trained), and the routing model configured per channel (Most Available for chat, Least Active for voice). When a Spanish-speaking customer's hazmat-related Case lands in the queue, Omni-Channel Routing finds the agent with both skills below capacity and routes the work to them. Without Omni-Channel Routing, the same triage would happen via supervisors manually distributing tickets.
Why Omni-Channel Routing matters
Omni-Channel Routing is a Service Cloud feature that automatically routes incoming work items (cases, chats, leads, custom objects, messaging conversations) to the most appropriate available agent based on agent capacity, skills, and routing configuration. It moves contact center operations away from manual queue picking and toward intelligent automated routing, ensuring work flows to agents who have the right skills and the capacity to handle it.
Omni-Channel is one of the most impactful Service Cloud features for high-volume contact centers because it eliminates the inefficiency of agents picking work from queues. Without Omni-Channel, agents browse queues looking for work, which leads to cherry-picking easy items, missed urgent items, and uneven distribution. With Omni-Channel, the platform pushes the right work to each agent automatically. Configuration involves defining service channels, routing configurations, presence statuses, and agent skill assignments, with options for both standard rule-based routing and custom Flow-based routing for complex needs.
How to set up Omni-Channel Routing
Omni-Channel Routing is the engine that auto-assigns incoming work — Cases, Chats, Leads, custom objects — to agents based on capacity, skills, and configuration. The whole feature, not a single Setup page. To set up routing, you configure Service Channels, Routing Configurations, Queues, Presence Statuses — see each respective term for those details.
- Enable Omni-Channel
Setup → Omni-Channel Settings → Enable. Foundational toggle.
- Create Service Channels
Setup → Service Channels → New. Each is a category of work (Cases, Chats, custom). See service-channel.
- Create Routing Configurations
Setup → Routing Configurations → New. Define routing model (Most Available / Least Active / External / Skills-Based) + capacity weight. See omni-channel for full details.
- Create Queues + assign Routing Configurations
Setup → Queues. Each Queue gets a Routing Configuration that drives the actual routing logic.
- Create Presence Statuses
Setup → Presence Statuses. Drives what agents pick from to indicate availability.
- Add Omni-Channel utility to the Lightning Service Console App
Setup → App Manager → Edit Service Console → Utility Items → add Omni-Channel.
- Configure Skills (optional, for Skills-Based Routing)
Setup → Skills → New. Each Skill represents a competency ("Spanish-speaking," "Tier 2 Technical"). Assign to agents.
Most Available / Least Active / External Routing / Skills-Based.
How much of an agent's bandwidth each work item consumes.
How long Omni waits for an agent to accept before re-routing.
Match work to agents by competency.
- Skills-Based Routing requires a separate Field Service or Service Cloud Voice license. Standard Omni-Channel routes by queue + availability only.
- Capacity is per-agent, set on Service Presence Status. Misaligned capacity weights produce strange routing — an agent at "100% capacity" still receives a Chat (weight 2) because their cap is 6 (Cases worth 1 each totaling 4).
- Push Time-Out is critical. Default 30 seconds; setting too short causes ping-ponging across agents, too long delays escalation. Tune based on real workflow.
How organizations use Omni-Channel Routing
Implemented Omni-Channel Routing to eliminate cherry-picking from their case queues, with the platform now distributing work evenly based on capacity and skills.
Combines skills-based routing with capacity management so agents only get work they can handle, with the right expertise.
Uses Omni-Channel for all their service channels (cases, chats, messaging) so all incoming work flows through unified routing.
Trust & references
Straight from the source - Salesforce's reference material on Omni-Channel Routing.
- Route Work with Omni-ChannelSalesforce Help
- Set Up Omni-Channel RoutingSalesforce Help
Test your knowledge
Q1. What is Omni-Channel Routing?
Q2. Why use Omni-Channel over manual queues?
Q3. What does Omni-Channel route?
Discussion
Loading discussion…