Skill Based Routing in Salesforce with an Omni-Channel Flow: 8 Rules From a Real Build

The first time I wired up an Omni-Channel flow for skills, I saved a test case and Salesforce refused it with a null pointer error about something called “skillOption”. The second time, the flow worked perfectly and a billing case still sat in the queue all afternoon, because no rep on the team had the Billing Disputes skill.

Both lessons came from the same build, and this post is the notes from it. You will set up skill based routing in Salesforce with an Omni-Channel flow, where the element that connects the flow to the agent is the Route Work action. A record-triggered flow picks the skill, a subflow routes the case, and you will know which settings break it and how to stop work from getting stuck.