Omni-Channel Routing
Omni-Channel Routing is the Service Cloud feature that pushes work items (Cases, Leads, Chats, Messages, Voice calls, custom records) to service agents based on agent availability, skill match, capacity, and channel priority.
Definition
Omni-Channel Routing is the Service Cloud feature that pushes work items (Cases, Leads, Chats, Messages, Voice calls, custom records) to service agents based on agent availability, skill match, capacity, and channel priority. Instead of agents pulling work from queues (the legacy pattern), Omni-Channel pushes the next available item to the agent best suited to handle it. Routing happens continuously: as soon as an agent finishes a case, the system assigns the next one.
Omni-Channel runs on Salesforce's routing engine, which evaluates Service Channel definitions (Case, Chat, Message), Routing Configurations (how work is prioritized), Presence Statuses (whether an agent is available for which channels), and Skill-Based Routing (matching item requirements to agent abilities). The combination produces a routing decision per work item per agent. Agents see incoming work in the Omni-Channel widget (a floating panel in the Service Console) and accept, decline, or auto-accept based on configuration. The model scales from small support teams to thousands of agents across multiple lines of business.
How Omni-Channel Routing pushes the right work to the right agent at the right time
Service Channels and the work item types
Each Service Channel maps to a Salesforce object type that can be routed. Standard channels cover Case, Lead, Chat (legacy live agent), Messaging (modern messaging), Voice, and any custom object. Each Channel has its own capacity weight, configurable Routing Configuration, and Service Console placement. A messaging chat consuming 5 capacity points means an agent set to capacity 100 can handle 20 chats simultaneously; a phone call consuming 100 means the agent can handle one call at a time.
Routing Configurations and the prioritization logic
A Routing Configuration defines how items in a queue route to agents. Two routing models: Most Available (push to agent with lowest current load) and Least Active (push to agent who has been idle longest). Each Routing Configuration also sets the Priority (1-9, lower is higher priority) which determines order across channels. A Voice channel at priority 1 always routes before a Case channel at priority 5, even if the Voice channel has 100 waiting items.
Presence Statuses and what they signal
Agent availability is governed by Presence Statuses (Available, On Break, Lunch, In Meeting, Offline). Each status is configured to receive work on specific channels (Available accepts all channels; In Meeting accepts none; Lunch could optionally accept escalations only). Agents pick a Presence Status from the Omni-Channel widget; the routing engine only pushes work to agents in a work-eligible status. Presence Status changes are audited on the UserServicePresence object for shift reporting.
Skill-Based Routing
Beyond channel and queue routing, work items can require specific Skills (Spanish-language, Financial Products, Tier 2 Technical). Each item is tagged with required Skills; each Service Resource (agent) has Skills assigned with a Proficiency Level. The routing engine intersects skills and proficiency to pick the best-fit agent available. Without skill-based routing, all queue members are equivalent; with it, the right SME gets the right case automatically. Skill-based routing requires Service Cloud Voice or a separate Field Service license at the higher tier.
Capacity, Push Time-Out, and decline behaviour
Each agent has a per-channel capacity (max simultaneous chats, max simultaneous cases). The routing engine never exceeds this. Push Time-Out controls how long an item waits for an agent to accept before re-routing; defaults to 60 seconds. Agents can decline an incoming item (configurable); declined items either re-route to another agent or return to the queue. Auto-Accept skips the decline step entirely; the item lands on the agent regardless. Voice almost always auto-accepts; chat and case sometimes allow decline for triage.
Omni-Channel Flow as the modern entry point
Salesforce''s newer Omni-Channel Flow lets admins build routing logic in Flow Builder instead of relying solely on queue assignment rules. The flow runs on the work item before routing, can examine record fields, branch on conditions, and assign Skills or set Routing Configuration dynamically. This is the recommended approach for any new Omni-Channel rollout; legacy queue assignment rules are still supported but lack the flexibility of flow-based routing.
Reporting and the UserServicePresence audit trail
Standard reports on Omni-Channel pull from AgentWork (every routed item), UserServicePresence (every status change), and PendingServiceRouting (items waiting for an agent). Three standard report types: Agent Work History, Service Channel Status, and Routing Performance. Build dashboards on Average Speed of Answer, Abandon Rate, Agent Occupancy, and Items per Hour per Channel. Operational metrics drive workforce planning; without them, service teams are guessing at agent staffing.
Enabling and configuring Omni-Channel Routing
Omni-Channel setup runs in five stages: enable the feature, define channels, build presence statuses, configure routing, and add the Omni-Channel widget to the Service Console. Plan one to two weeks of admin time for a non-trivial rollout.
- Enable Omni-Channel
Setup, Omni-Channel Settings, Enable Omni-Channel. This activates the Service Channel object and the underlying routing engine. After enable, the Omni-Channel widget is available in the Service Console app builder.
- Define Service Channels
Setup, Service Channels. Create one per work-item type: Case, Lead, Messaging, Voice, and any custom object the org routes. Each Channel needs an object name and a capacity model (per-item weight).
- Build Presence Statuses
Setup, Presence Statuses. Create at minimum Available, On Break, and Offline. Assign each status to a Service Channel set: Available accepts everything; Offline accepts nothing. Add status options for break, lunch, meeting based on shift policy.
- Configure routing per channel and queue
Setup, Routing Configurations. For each channel-queue combination, set Routing Model (Most Available or Least Active), Priority (1-9), Push Time-Out, and capacity weight. Assign Routing Configurations to the right queues.
- Drop the Omni-Channel widget on the Service Console
App Builder, edit the Service Console app, add the Omni-Channel utility widget to the utility bar. Agents see the widget floating at the bottom of the console; they pick a Presence Status and incoming work appears in the panel.
Most Available (lowest current load) or Least Active (idle longest). Most Available balances load; Least Active rewards utilization. Pick per channel.
1-9, lower is higher priority. Determines cross-channel routing order. Voice typically priority 1, Cases priority 5, Leads priority 7.
Seconds an item waits for an agent to accept before re-routing. 60 seconds default; lower for voice, higher for cases that need triage.
Items push directly without the accept step. Standard for voice; optional for chat and messaging; rare for cases.
- Presence Statuses are per-org, not per-queue. An agent set to Available is available to every Service Channel that includes Available in its routing config.
- Capacity is per-channel per-agent. Total occupancy across channels can exceed any single channel''s cap; do not assume capacity 100 means 100 total items.
- Skill-Based Routing requires the Service Cloud Voice or Field Service license at a higher tier. The base Omni-Channel license does not include it.
- The Omni-Channel widget needs to be on the utility bar of every Service Console app agents use. Missing widget = agents do not receive routed work even if everything else is configured.
- Omni-Channel Flow and legacy queue-based routing can both be in play, with the flow overriding the queue. Audit which path each Service Channel uses.
Trust & references
Cross-checked against the following references.
- Omni-Channel OverviewSalesforce Help
- Omni-Channel RoutingSalesforce Help
Straight from the source - Salesforce's reference material on Omni-Channel Routing.
- Set Up Omni-ChannelSalesforce Help
- Skill-Based Routing for Omni-ChannelSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
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…