Omni-Channel Settings
Omni-Channel Settings is the Setup page that enables and globally configures Salesforce's Omni-Channel work routing engine.
Definition
Omni-Channel Settings is the Setup page that enables and globally configures Salesforce's Omni-Channel work routing engine. From this single page, admins switch Omni-Channel on for the org, control whether routing pushes work to agents in console or in the standard interface, define decline reasons, set the default service channel behavior, and configure secondary routing options like Omni Supervisor and Skills-Based Routing.
The page sits under Setup > Omni-Channel > Omni-Channel Settings and acts as the master switch. Without it enabled, every other Omni-Channel feature (queues, service channels, presence configurations, routing configurations) is invisible and the omni utility item does not appear in any app. Once enabled, the page acts as a control center: turn on skills-based routing, external routing, secondary routing priority, and the various supervisor features from here.
What each switch in Omni-Channel Settings actually controls
Enable Omni-Channel checkbox
The first toggle on the page activates the entire feature. Once enabled, Salesforce provisions the Omni-Channel Routing engine in the background, creates the AgentWork object, exposes Routing Configuration and Presence Configuration objects, and surfaces the Omni-Channel utility item for inclusion in Lightning apps. Turning Omni-Channel off after work has been routed leaves orphaned AgentWork records that cannot be cleanly closed; treat the enable step as a one-way switch.
Skills-Based Routing toggle
Skills-Based Routing assigns work to agents based on the skills defined on the user (language, product expertise, certification level) instead of just queue membership. Enabling this option exposes the Skills object, lets routing configurations reference skill requirements, and routes incoming Cases or Leads to the agent with the best skill match. Without this, Omni-Channel is queue-based only and skill matching cannot be evaluated. Most enterprise contact centers turn this on.
External Routing toggle
External Routing lets a third-party engine (Genesys, NICE, Five9) make the routing decision and push the assigned work into Salesforce Omni-Channel for presentation to the agent. Salesforce becomes the agent desktop; the external system becomes the queue and routing brain. Enable this when the existing call center investment has a routing engine and you only need Salesforce for the agent UI.
Secondary Routing Priority
Standard Omni-Channel routes by primary priority (Cases of priority 1 before priority 2). Secondary Routing Priority adds a tiebreaker: when two Cases have the same primary priority, route the older one first (or the one with the higher VIP score). Enable this if the contact center has SLA commitments that go beyond the basic queue priority. The setting exposes additional fields on the Routing Configuration object.
Omni Supervisor enablement
The Omni Supervisor toggle exposes the real-time supervisor dashboard with agent status, queue depth, and work-in-progress per agent. Without it, supervisors can only see aggregate dashboards and not the per-agent live view. Omni Supervisor needs its own permission set and app license; the toggle here switches the feature on for the org but does not grant access automatically.
Decline Reasons and Reason Codes
When an agent rejects a work assignment, Omni-Channel asks for a reason. The Decline Reasons section on the Settings page lets the admin define a picklist of valid reasons (Already at capacity, Out of skill, Personal emergency). The reasons feed into the AgentWork.DeclineReason field, which powers supervisor reporting on why work is not being accepted. Without configured reasons, declines default to a generic blank value and the report is useless.
How to enable Omni-Channel and configure the global settings
Enable Omni-Channel from this page first, then layer queues, service channels, presence configurations, and routing configurations through other Setup nodes. The order matters because dependent setup nodes only appear after Omni-Channel is enabled.
- Navigate to Omni-Channel Settings
Setup > Omni-Channel > Omni-Channel Settings. The page is short; every toggle for the org sits on a single screen.
- Check Enable Omni-Channel
Click Edit if necessary. Check Enable Omni-Channel and Save. The downstream Setup nodes (Service Channels, Queues, Presence Configurations, Routing Configurations) now appear under Omni-Channel.
- Enable Skills-Based Routing (optional but common)
Check Use Omni-Channel with Skills-Based Routing if the contact center needs to match work to agent skills rather than just queues. Save.
- Enable Secondary Routing Priority (if SLA-driven)
Check Use with Secondary Routing Priority. Configure the field on the routing configuration once the toggle is on.
- Configure Decline Reasons
Scroll to the Decline Reasons section. Add the picklist values that match your contact center's reporting needs. Save.
- Validate by creating a test work item
After enabling, set up at least one Service Channel, one Queue, one Routing Configuration, and one Presence Configuration. Assign a test user to the queue and route a test Case to confirm the engine works end to end.
Default mode. Work goes to the queue, then to the available agent with capacity. No skills required.
Work matches against agent skill profiles. Requires Skills-Based Routing toggle and configured Skills on users.
Third-party engine decides the routing, Salesforce shows the work. Requires external integration build.
Combination model where some channels route through Salesforce and others through external systems.
- Omni-Channel Settings is a single page but it gates dozens of other Setup nodes. Do not panic if Routing Configurations or Service Channels are missing from the menu; enable Omni-Channel here first.
- Enabling Skills-Based Routing requires every existing Routing Configuration to be reviewed. The field set changes and some legacy queue-only configurations stop routing until they are explicitly opted out.
- Disabling Omni-Channel after agents have done work corrupts AgentWork records. Plan rollout as one-way; sandbox-test the rollback path if leadership reserves the right to back out.
- Decline Reasons configured here are global. To capture channel-specific decline reasons, add a custom picklist on AgentWork through Object Manager and feed the data to your dashboards separately.
Trust & references
Cross-checked against the following references.
- Set Up Omni-ChannelSalesforce Help
- Enable Omni-ChannelSalesforce Help
Straight from the source - Salesforce's reference material on Omni-Channel Settings.
- Omni-Channel OverviewSalesforce Help
- AgentWork SObject ReferenceSalesforce Developers
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…