How We Restored One-Click Case Transfers After Salesforce’s Enhanced Omni-Channel Upgrade
Salesforce Enhanced Omni-Channel made routing more capable. But for one customer service team, it also made one everyday task noticeably harder: transferring a case to the right agent. Before the upgrade, agents using skills-based routing had a simple Transfer button. One click started the handoff.
After moving to Enhanced Omni-Channel, that workflow changed. Salesforce introduced the more flexible Reassign action. The platform gained routing options. Agents gained more decisions, searches, and clicks.
For a support operation handling cases at volume, that difference mattered.
So we rebuilt the experience around a simple principle:
Keep the power of Enhanced Omni-Channel. Remove the friction from the agent workflow.
The result was a custom Salesforce case-transfer experience that uses the skills already associated with a case to make most transfers effectively one click again.
What Changed With Salesforce Enhanced Omni-Channel?
Salesforce Omni-Channel determines how incoming service work gets routed and managed across support teams.
For teams using skills-based routing, the previous experience provided agents with a straightforward way to hand work to another qualified agent.
The agent selected Transfer, and the case could move on.
Enhanced Omni-Channel changed that workflow. Salesforce replaced the previous transfer experience with Reassign, giving teams more control over where work can go. That additional flexibility is useful. But flexibility at the platform level does not always mean simplicity at the agent level.
The Hidden Impact on the Agent Experience
With Enhanced Omni-Channel, agents could reassign work based on several destinations, including a user, queue, skill, or routing flow.
That sounds better on paper. For this team, however, a routine transfer now required several manual decisions.
An agent had to:
Click Reassign.
Choose the appropriate transfer type.
Search for the correct queue, user, skill, or routing destination.
Select the right result.
Confirm the reassignment.
None of these steps is particularly difficult. That wasn't the problem. The problem was repetition.
Agents handling large case volumes were being asked to stop, identify routing information, search for it, confirm it, and repeat the process throughout the day.
They also didn't necessarily know the exact queue names or system terminology Salesforce expected. And they shouldn't have to.
The problem, in three layers
Platform
More routing flexibility
Workflow
More choices and manual inputs
Agent
More clicks, searches, and decisions
The upgrade improved the routing engine. But it added friction to the people using it.
What Does Salesforce Provide Out of the Box?
Salesforce's native answer in Enhanced Omni-Channel is the Reassign action. It is flexible by design. Teams can use it to redirect work based on different routing destinations rather than relying on a single transfer path.
That flexibility works well when agents genuinely need to make those routing decisions.
Our client's workflow was different.
Their operation already relied on skills-based routing. When a case reached an agent, Salesforce had already identified the skills required for that work.
That created an obvious question:
Why ask the agent to manually rebuild routing context Salesforce already knows?
That became the foundation for the solution.
The Custom Salesforce Case-Transfer Solution We Built
We built a streamlined transfer experience around the way this support team already worked.
Instead of asking agents to decide where a case should go from scratch, the solution starts with the skills already associated with the current assignment. That context follows the case into the transfer experience.
Here is what the agent sees
The agent clicks Transfer from the case. A simple screen opens. The skills associated with the current assignment are already displayed and pre-filled.
The agent does not need to:
remember a queue name,
search for the original routing criteria,
recreate the existing skills,
or understand the underlying routing configuration.
If the current skills are correct, the agent can simply confirm the transfer. If the situation requires additional expertise, the agent can add more skills to refine or broaden the routing criteria, with up to five skills available in the custom experience. Then they click Transfer.
The interface stays simple because the routing intelligence sits behind it.
What Happens Behind the Scenes?
Once the agent confirms the transfer, the system uses those skills to find an appropriate available agent. If a matching agent is available, the case can be routed accordingly. If nobody with the required skills is currently available, the case waits within the routing process until a matching agent becomes available.
The agent receives confirmation that the transfer is underway. This means the support rep does not need to understand every routing rule behind the transaction. They provide only the information the system actually needs. The platform handles the rest.
We Also Added Guardrails
Making a workflow faster is useful only if it remains controlled. So the transfer tool does not run indiscriminately. We added safeguards around where and when it can be used.
For example, the experience prevents transfers for cases that are already resolved or currently on hold.
It is also restricted to the relevant case types. That matters. A shortcut without controls simply creates a faster way to make mistakes.
The objective was different:
Reduce unnecessary agent decisions without removing the business rules protecting the workflow.
What Changed for the Support Team?
Before the custom solution, a transfer required multiple actions:
Decide
Search
Select
Confirm
Reassign
With the new experience, the normal path became: Review pre-filled skills → Transfer
No memorizing queue names.
No repeatedly rebuilding routing criteria.
No unnecessary navigation.
No guessing where a case belongs.
The support team kept the routing capabilities of Enhanced Omni-Channel while recovering the simplicity agents valued in the previous experience.
That was the real outcome
We did not try to replace Salesforce's routing architecture. We used it. Then we redesigned the final mile around the people who had to use it every day.
The Bigger Lesson: Platform Capability ≠ User Experience
Salesforce upgrades often solve larger platform problems. They introduce new capabilities, improve architecture, and create more configuration options. But an upgrade can still introduce friction into a specific operational workflow. Those two things can be true at the same time.
The answer is not always to resist the upgrade. And it is not always to accept every new click as unavoidable.
Sometimes the better approach is to preserve the platform improvement while rebuilding the user experience around the actual business process. That is what we did here.
Enhanced Omni-Channel stayed.
Skills-based routing stayed.
The unnecessary friction didn't.
Your Salesforce Upgrade Shouldn't Make Your Agents Slower
Platform upgrades are meant to improve what your service operation can do. They should not force agents to fight the system to complete routine work.
If your Salesforce implementation technically works but everyday workflows still require too many clicks, searches, workarounds, or manual decisions, the problem may not require another platform.
It may require a better implementation.
That's the kind of gap we solve at Truffle Consulting.
We build Salesforce around the way the business actually operates, from Service Cloud and Omni-Channel to Data Cloud, integrations, and AI.
Got a Salesforce workflow that works on paper but slows your team down in practice?
Email us at hello@trufflecorp.com
Let's find the friction and fix it.
Frequently Asked Questions
What is the Reassign action in Salesforce Enhanced Omni-Channel?
Reassign allows teams to redirect supported work items to another routing destination instead of relying on the previous transfer experience.
For teams with more complex routing requirements, that creates useful flexibility. For repetitive, skills-based workflows, it can also introduce additional agent decisions.
Can Salesforce Omni-Channel transfers use skills-based routing?
Yes. Skills-based routing allows Salesforce to match work with agents based on the skills required to handle it.
In this implementation, we used the skills already associated with the current assignment as the starting point for the transfer.
Why build a custom transfer experience instead of using Reassign?
The requirement was not more routing flexibility. The requirement was less friction during a high-frequency agent task.
The native experience required agents to repeatedly select and search for routing information. The custom experience reused existing case context so the agent had fewer decisions to make.
Does the custom solution replace Enhanced Omni-Channel?
No.
Enhanced Omni-Channel remains the routing foundation. The custom solution improves the experience around a specific transfer workflow while continuing to use Salesforce's routing capabilities underneath it.
Comments