The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

How to set up Enhanced Omni-Channel Routing for Service Cloud agents (opens in a new tab)

You will learn what Enhanced Omni-Channel requires, how queue-based, skill-based and external routing differ, and the main steps to enable routing and test it.

Why read this

You will also know that Standard Omni-Channel was retired in Summer '26 and that existing configurations carried over.

  1. Turn on Enhanced Omni-Channel Routing
  2. Choose queue-based or skill-based routing
  3. Configure queues or skills and agents
  4. Define routing configurations
  5. Test with a sample case
The order of steps for a first-time Enhanced Omni-Channel setup

Standard Omni-Channel was retired in Summer ’26, and Salesforce upgraded orgs automatically during the rollout. Enhanced Omni-Channel, generally available since 2023, takes work items such as Cases, Leads, chats, messaging sessions and voice calls and routes them to reps based on availability, skills, capacity and priority. Existing routing configurations, queues, skills and routing rules were carried over. The feature requires a Service Cloud license or one of several add-on licenses, and it works only in Lightning Experience.

To enable it, go to Setup, then Feature Settings, then Service, then Omni-Channel Settings, and turn on Enhanced Omni-Channel Routing. The article describes three routing options: queue-based routing for smaller teams and simpler product lines, skill-based routing for complex cases that need specific expertise, and external routing for keeping logic in a third-party tool that connects through APIs. Enhanced Omni-Channel adds destinations including a queue, a skill, a specific rep and an Agentforce Service Agent.

Queue-based setup can be started with the guided flow under Omni-Channel Setup, which covers creating a queue, assigning agents and setting workload, followed by defining routing configurations. Skill-based setup is more involved: enable Omni-Channel and Field Service settings, create Skills, create active Service Resource records for agents with skill levels and dates, define Skills-Based Routing Rules through skill mapping sets, and confirm the routing configurations use those skills.

The article closes by describing the agent experience: the Omni-Channel Utility Bar item in the Service Console, where agents log in as available and receive incoming work with an audio notification. Its advice is to start with the simplest setup that covers the team, test with a sample Case, and add precision later.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Recommended

Agentforce Service offerings explained for configuration and rollout planning (opens in a new tab)

Readers will learn how to configure and deploy Agentforce Service agents, understand the prerequisites for Omni-Channel routing and Knowledge grounding, and see which legacy channels are being retired.

Why read this

The piece also outlines practical rollout strategies to avoid common implementation pitfalls.

The piece is a guide to Agentforce Service, Salesforce’s AI customer service platform, which was renamed from Service Cloud in October 2025. It covers seven offerings: AI agents, case management, omnichannel contact center, an AI knowledge base, field service, analytics and integrations. For each, it explains what the offering does, what it depends on and where teams tend to run into trouble. The AI agents come in two forms. Help Agent is prepackaged and set up from one screen, and it is grounded on Salesforce Knowledge, uploaded files or a website sync. It needs Enterprise or Unlimited Edition with Agentforce enabled. Service Agent is configurable, with topics, instructions and actions defined by the team, and suits work that touches the company’s own systems, such as order lookups or appointment changes. Agentic features such as Agentic Milestones, MCP support and multi-agent setups are also described. Omni-Channel routing depends on Enhanced Omni-Channel, which the article calls the foundation for Agentforce Service and a requirement for Agentforce Voice and Contact Center.

On the contact center and channels, the article notes that Salesforce is retiring Standard Facebook Messenger and Standard SMS channels in mid-2026, so teams still on them should move to Enhanced channels. It also points to the knowledge base as a dependency: AI answers are only as good as the Knowledge articles behind them, so the author recommends knowledge-centered service habits. Case management, field service work orders, analytics (with metrics such as autonomous resolution rate, escalation rate and CSAT on AI-handled cases) and MuleSoft-based integrations with ERP and telephony systems are each summarized with their key requirements. Pricing mixes per-user licenses, Flex Credits and a per-resolution charge for Help Agent, and the article advises confirming current India pricing with Salesforce.

The rollout advice is the practical core. The author suggests auditing data and the knowledge base first, setting up Enhanced Omni-Channel, launching one AI agent on a single high-volume, low-risk queue, measuring results for a month and then expanding, with budget kept for ongoing tuning after go-live. The article is written by Cloud Odyssey, a Salesforce partner, and it promotes its own services, so its vendor-supplied performance figures (such as 72% of routine inquiries offloaded and 70% resolution on Salesforce’s own help portal) are presented as numbers to test rather than guaranteed results.

Read the original at Cloud Odyssey (opens in a new tab)

Worth reading?