Omni-Channel Settings
Omni-Channel Settings is the Setup page in Salesforce Service Cloud that turns the Omni-Channel work routing engine on for an org and holds its global, org-wide options.
Definition
Omni-Channel Settings is the Setup page in Salesforce Service Cloud that turns the Omni-Channel work routing engine on for an org and holds its global, org-wide options. From this one page an admin enables Omni-Channel itself, switches on Enhanced Omni-Channel Routing, allows skills-based and direct-to-agent routing, sets the work-item session expiration, and defines the decline reasons agents pick when they reject a work assignment.
You reach it at Setup > Feature Settings > Service > Omni-Channel > Omni-Channel Settings. Think of it as the master switch. Until the Enable Omni-Channel checkbox is selected, the rest of the feature stays hidden: Service Channels, Queues, Routing Configurations, Presence Configurations, and the Omni-Channel utility item all stay out of view. Once it is on, the page becomes the control panel for the routing options that every downstream component depends on.
What lives on the Omni-Channel Settings page
The Enable Omni-Channel master switch
The first control on the page is the Enable Omni-Channel checkbox, and it activates the whole feature. Selecting it and saving provisions the routing engine, exposes the AgentWork object, and surfaces the Omni-Channel utility item so you can add it to a Lightning app. Before this box is checked, Service Channels, Routing Configurations, Presence Configurations, and Presence Statuses do not appear in Setup, and agents have no way to accept routed work. This is why enabling Omni-Channel is always the first step in any Service Cloud routing build. Treat the switch as effectively one-way. Once work has been routed and AgentWork records exist, turning the feature back off leaves those records behind with no clean way to close them, and it pulls the utility item out of every app that referenced it. In practice teams enable it once in a sandbox, validate the full setup, and then enable it in production as part of a planned deploy rather than flipping it casually during business hours.
Enhanced Omni-Channel Routing
Enhanced Omni-Channel Routing is the modern, server-side version of the routing engine, and it is a checkbox on this page. The original model ran routing through agent browser sessions, which meant work could stall if an agent closed the tab or lost connectivity. The enhanced model moves the routing decision to the Salesforce platform, so work is assigned reliably even when an agent is between sessions. It is also the prerequisite for several newer capabilities. Skills-based routing rules, direct-to-agent routing, and routing for messaging and voice channels all expect the enhanced engine. When you turn it on, Salesforce migrates eligible queues and channels to the new model and the settings page reveals the related options that depend on it. New orgs generally start here because the older browser-based model is being phased toward legacy status. If you inherit an older org, check whether Enhanced Omni-Channel Routing is on before you debug routing behavior, because the two models handle capacity and assignment differently.
Skills-based and direct-to-agent routing
Once Enhanced Omni-Channel Routing is on, the page shows the option labeled Enable Skills-Based and Direct-to-Agent Routing. Skills-based routing matches a work item to the agent whose assigned skills (language, product knowledge, certification, region) satisfy the skills the item requires, rather than relying on queue membership alone. Omni-Channel then assigns the item to the first qualified agent who has spare capacity. Direct-to-agent routing lets you send a work item to one specific named agent, which is useful for callbacks, follow-ups, or VIP handling where continuity with the same person matters. Both options are switched on from this single checkbox, and both then need follow-up configuration elsewhere. You define skills under Setup, assign them to agents as service resources, and mark a Routing Configuration to use skills-based routing rules. The settings page only opens the door. It does not build the skill model for you, so plan the skill taxonomy before you flip the switch.
Decline reasons agents choose from
When an agent rejects a routed work assignment, Omni-Channel can ask why. The decline reasons you define on the settings page populate the list the agent picks from, and the chosen value lands on the AgentWork record so supervisors can report on it. Without configured reasons, declines collapse into a single blank value and the data tells you nothing useful. With a short, deliberate set (for example, at capacity, wrong skill, needs escalation, technical issue) you get a clear picture of why work is bouncing and where coaching or staffing needs to change. Keep the list tight. A handful of distinct, action-oriented reasons beats a long menu that agents click through without thought. Decline-reason reporting is one of the few places where Omni-Channel exposes agent behavior at the moment of refusal, so the quality of these picklist values directly shapes how well a supervisor can manage the floor. Review the list periodically and retire reasons nobody selects.
Work item session expiration
The settings page includes a session-expiration value that controls how long Omni-Channel keeps trying to route a particular work item before it gives up. If no eligible agent accepts within the window, the item stops being pushed and falls back to its queue for manual pickup or a fresh routing pass. The default is generous, but contact centers with tight service-level agreements often shorten it so stale items do not sit in routing limbo while a customer waits. Setting it too short causes items to bounce back to the queue before a briefly busy agent frees up, which creates churn. Setting it too long lets an item chase unavailable agents while the clock runs. The right value depends on your average handle time and how quickly agents cycle through work, so tune it after you have watched real traffic rather than guessing on day one. This single field has an outsized effect on perceived responsiveness, especially for live channels like chat and messaging.
Where the settings page stops and other setup begins
It helps to be clear about the boundary of this page. Omni-Channel Settings holds org-wide switches and defaults. It does not hold the per-queue or per-channel rules that actually decide how a given work item moves. Those live in separate objects. A Routing Configuration sets the routing model, priority, and capacity weight for a queue. A Service Channel ties an object such as Case, Lead, or a messaging session to a routing setup. A Presence Configuration governs how much work an agent can hold at once and which statuses they can choose. Presence Statuses define whether an agent is available or away for each channel. The settings page turns the engine on and exposes those objects, but you still build each one. Newer orgs may also route through Omni-Channel Flows, which let an admin design routing logic visually and send work to queues, skills, agents, or bots. Knowing this split saves time when you are deciding where to make a change.
How to enable and configure Omni-Channel
Enabling Omni-Channel is the gateway to every other routing component. Here is the order most admins follow on the settings page itself, before building queues and routing configurations elsewhere.
- Open the settings page
From Setup, use Quick Find to go to Omni-Channel Settings under Feature Settings > Service > Omni-Channel. This is the page that holds every org-wide switch described here.
- Enable Omni-Channel
Select the Enable Omni-Channel checkbox and save. Saving provisions the routing engine and reveals Service Channels, Queues, Routing Configurations, and Presence Configurations in Setup.
- Turn on Enhanced Omni-Channel Routing
Select Enhanced Omni-Channel Routing so routing runs server-side rather than through agent browser sessions. This is the prerequisite for skills-based and messaging-channel routing.
- Allow skills-based and direct-to-agent routing
If you route by skill or to specific agents, select Enable Skills-Based and Direct-to-Agent Routing, then save. You still define skills and update Routing Configurations afterward.
- Set decline reasons and session expiration
Add a short list of decline reasons agents choose when rejecting work, and review the session-expiration window so unaccepted items return to the queue at a sensible time.
The master checkbox that activates the routing engine and exposes all other Omni-Channel objects and the utility item.
Switches routing to the reliable server-side engine and unlocks skills-based, direct-to-agent, and messaging-channel routing.
Lets routing match work to agent skills or send it to one named agent, after you build the skill model and update routing configurations.
The picklist of reasons agents select when declining a work assignment; the value is stored on AgentWork for supervisor reporting.
How long Omni-Channel keeps pushing an unaccepted work item before it falls back to the queue for manual pickup.
- Enabling Omni-Channel is effectively one-way. Once AgentWork records exist, turning it off strands them and removes the utility item from every app.
- Switching on Enhanced Omni-Channel Routing changes how capacity and assignment behave, so retest existing routing rather than assuming old configurations behave the same.
- The settings page only enables skills-based routing. You must still create skills, assign them to service resources, and mark each Routing Configuration to use skills-based routing rules.
- A session-expiration window that is too short makes work bounce back to the queue before briefly busy agents free up; tune it against real traffic.
Trust & references
Cross-checked against the following references.
- Enable and Configure Omni-ChannelSalesforce
- Enable Skills-Based RoutingSalesforce
Straight from the source - Salesforce's reference material on Omni-Channel Settings.
- Set Up Omni-ChannelSalesforce
- Routing Model Options for Omni-ChannelSalesforce
Hands-on resources to go deeper on Omni-Channel Settings.
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 customer experience metric would Omni-Channel Settings help improve?
Q2. Which Salesforce Cloud includes Omni-Channel Settings as a key feature?
Q3. How does Omni-Channel Settings help support agents be more productive?
Discussion
Loading discussion…