Omni-Channel
Omni-Channel is a Salesforce routing engine that intelligently distributes work items such as Cases, Leads, Chats, and custom records to the most appropriate available agent in real time.
Definition
Omni-Channel is a Salesforce routing engine that intelligently distributes work items such as Cases, Leads, Chats, and custom records to the most appropriate available agent in real time. It considers agent capacity, skills, and availability to balance workloads and ensure fast response times across all service channels.
In plain English
“Okay, picture this: Imagine a hospital emergency room where doctors need to know which patients need help first. Omni-Channel works similarly in Salesforce's Service Cloud - it helps support teams organize customer issues, figure out what's urgent, and make sure nobody waits too long for help.”
Worked example
At NovaCom Telecom, Omni-Channel is configured to route Spanish-language chat requests to agents with the "Spanish" skill, billing Cases to the billing team, and VIP customer inquiries to senior agents. When agent Rachel finishes a chat, Omni-Channel checks her capacity and immediately assigns her the next highest-priority item from the queue.
Why Omni-Channel turns work distribution into a real-time optimization problem
Without intelligent routing, work distribution defaults to the first agent who grabs the case off a queue - which makes sense at small scale and produces wildly uneven workloads at any larger scale. Omni-Channel is the Salesforce engine that fixes this. It considers each agent's current capacity, their skills, their availability, and the urgency of the work item, and routes Cases, Leads, Chats, and custom records to the agent who's best positioned to handle them right now.
The reason this is the right architecture for any non-trivial service organization is that good routing compounds. Agents handle work matched to their skills; queues stay balanced; SLAs are met because the right work hits the right person at the right time. The trade-off is configuration complexity - modeling capacity, defining skills, calibrating routing rules - but for orgs with more than a handful of agents, the productivity gain is meaningful enough to justify the effort.
How to set up Omni-Channel
Omni-Channel is the Service Cloud routing engine — it pushes work items (Cases, Chats, Messaging conversations) to the right agents based on skill, capacity, and availability. Setup is multi-step (Service Channels, Routing Configurations, Queues, Presence Statuses) but the result is a unified work-distribution system.
- Enable Omni-Channel
Setup → Omni-Channel Settings → tick Enable Omni-Channel.
- Create a Service Channel
Setup → Service Channels → New. Pick the object (Case / Lead / Custom). One Service Channel per workable object type.
- Create Routing Configurations
Setup → Routing Configurations → New. Set Routing Model (Most Available / Least Active / External Routing), Capacity Weight (how much of an agent's bandwidth this work item consumes), Push Time-Out.
- Create or reuse Queues + assign Routing Config
Setup → Queues → assign each queue a Routing Configuration. Routing Config + Queue = the routing rule.
- Create Presence Statuses
Setup → Presence Statuses → New. Available / Busy / Offline. Each presence status maps to specific Service Channels — "Available for Chat" only routes Chat work.
- Add the Omni-Channel utility to your Lightning App
Setup → App Manager → Lightning App → Edit → Utility Items → add Omni-Channel. Without this, agents have no UI to set their presence.
- Train agents to set themselves Available
Work routes only when the agent's Presence Status maps to the Service Channel of the queued item.
Most Available (agent with most free capacity), Least Active (agent who took the longest-ago item), External Routing (custom Apex).
How much of an agent's capacity each work item takes. Cases: 1. Chats: 2. Voice: 5.
How long Omni waits for an agent to accept before re-routing. Default: 30 seconds.
Optional add-on. Match work items to agents by skill (Spanish-speaking, Technical-Tier-2).
- Agents must have the Omni-Channel utility on their Lightning App. Without the utility, they have no way to set their presence and receive zero routed work.
- Capacity Weight is per-object, but agents have a single overall capacity (Setup → Service Presence Statuses → set Capacity). Misaligned weights mean an agent at 100% capacity from 4 Cases (weight 1 each = 4 points used) can still receive a Chat (weight 2) if their cap is set to 6 — math errors are frequent.
- Skills-based routing is a paid add-on. Standard Omni-Channel routes by queue + availability only; skills routing requires Service Cloud Voice or the Field Service add-on.
How organizations use Omni-Channel
Configured Omni-Channel with three queues (Wholesale, DTC-eCommerce, Subscription) and skill-based routing so Spanish-language Cases reach a bilingual agent regardless of channel. After rollout, average handle time on Spanish Cases dropped 22% because the routing eliminated the manual transfer step.
Uses Omni-Channel's Presence Statuses to model agent state - "Available", "In Field Visit", "On Lunch", "In Training" - so routing only assigns work when an agent is genuinely capacity-available. Field visits no longer accumulate a queue of Cases the agent cannot see for hours.
Built capacity-weighted routing where a Tier-3 escalated Case consumes 3 capacity units versus a Tier-1 chat at 1 unit. The model prevents senior agents from being routed three escalated Cases at once and produced a measurable drop in escalation handoff between agents.
Trust & references
Straight from the source - Salesforce's reference material on Omni-Channel.
- Route Work with Omni-ChannelSalesforce Help
- Routing Model Options for Service Cloud Omni-ChannelSalesforce Help
Test your knowledge
Q1. What business function does Omni-Channel primarily support?
Q2. Which Salesforce Cloud includes Omni-Channel as a key feature?
Q3. How does Omni-Channel help support agents be more productive?
Discussion
Loading discussion…