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

Block unwanted outbound emails in Email-to-Case using Custom Metadata and Apex (opens in a new tab)

The reader will learn how to prevent accidental outbound replies in Email-to-Case by storing blocked addresses in a Custom Metadata Type and enforcing them with an Apex trigger on EmailMessage.

Agents frequently reply to internal distribution lists or automated mailboxes during Email-to-Case interactions, causing infinite loops or unintended data exposure. Standard workarounds rely on hardcoded Validation Rules or Apex classes, which demand repeated testing and deployments whenever the blocklist changes.

The proposed solution moves the restriction list into a Custom Metadata Type. Administrators gain direct access to manage blocked addresses through Setup, removing the need for developer intervention or version control cycles for simple address updates.

Enforcement occurs via a before insert trigger on the EmailMessage object paired with a dedicated handler class. The code isolates outbound communications, verifies the fifty hundred parent identifier to limit scope to cases, and compares recipient addresses against the metadata records using case insensitive matching.

When a restricted address appears in the to or cc fields, the trigger applies an error that prevents the message from sending. This architecture keeps the logic modular, avoids interfering with inbound case creation or unrelated email automation, and provides a reusable template for other metadata driven routing rules.

Read the original at dev.to (opens in a new tab)

Worth reading?