How Does Skills-Based Routing Work in Omni-Channel?

Why Queues Alone Fall Short

Queue-based routing is simple by design: a queue usually stands in for a single skill or team, and Omni-Channel pushes each work item to whichever member of that queue is next in line. That works fine when “Spanish-speaking” or “Tier 2 hardware” is the only qualification that matters.

It breaks down the moment a case needs two or three qualifications at once — a Spanish-speaking rep who is also certified on a specific product line, for example. Stacking queues doesn’t solve this cleanly, because a rep would need to join every relevant queue and Omni-Channel would still only be checking membership, not competence. Skills-based routing exists to close that gap: instead of checking “is this rep in the right group,” it checks “does this rep hold every skill this work item requires.”

Both approaches run on the same underlying engine — the routing configuration and queue infrastructure covered in the full guide to Omni-Channel routing — skills-based routing just adds a second filter on top of capacity, as Salesforce documents in its comparison of how skills-based routing differs from queue-based routing. Picture a support queue that handles both billing and technical cases in three languages: with queue-based routing alone, a French-speaking billing specialist and a French-speaking technical specialist look identical to Omni-Channel, because membership is the only signal it has.

How Salesforce Matches a Rep to Every Required Skill

A Skill record identifies an area of expertise — a language, a product line, or a certification like CompTIA or CCNP. Admins create them from Setup by searching Omni-Channel and opening Skills.

How a skill gets attached to a rep depends on which version of Omni-Channel the org runs. Standard Omni-Channel assigned skills through Assign Users and Assign Profiles sections on the skill record. Standard Omni-Channel reached end of support in Summer ’26, and eligible orgs were automatically upgraded to Enhanced Omni-Channel — so on a current org, skills are added directly to each rep’s ServiceResource record instead, per Salesforce’s own Enhanced Omni-Channel overview on Trailhead. If your org’s history includes that migration, the sibling brief on Standard vs. Enhanced Omni-Channel covers what else changed.

Capacity is checked at the same moment, not as a separate later step. A rep can hold every required skill and still be skipped if their current workload already consumes the capacity a routing configuration allows them — which is why a fully-skilled team can still leave work items waiting during a busy stretch.

Setting Up Skills-Based Routing Rules

Rather than assigning skill requirements to every record by hand, most orgs use Skills-Based Routing Rules — a declarative mapping between a work-item field value and a skill. A common example: map the Case Type field value “Product Return” to a “Returns Processing” skill, so every return case is automatically tagged with the right requirement the moment it’s created. Salesforce supports this mapping on Case, Lead, Order, and custom objects.

The setting isn’t global. Per Salesforce’s setup requirements for skills-based routing rules, the routing configuration used by the specific queue the work item passes through must itself be enabled to use skills-based routing rules — so two queues in the same org can behave differently even if both reference the same skill.

What Happens When Skills-Based Routing Can’t Find a Match

There’s no silent downgrade. Salesforce does not reroute an unmatched work item to a rep who’s simply available but missing a required skill. Instead, the item stays pending against that queue’s routing configuration until a service resource who holds every required skill and has open capacity becomes free to take it.

That’s a deliberate design choice, not a gap — but it means the burden of avoiding a stalled queue sits entirely with the admin. In practice, that means cross-training reps to hold multiple relevant skills, or pairing a narrowly-skilled queue with a broader catch-all routing configuration reps can be added to as overflow. Because the underlying pending-routing record stays open rather than erroring out, a supervisor watching Omni Supervisor sees it sitting in the queue’s backlog exactly like any other unassigned work item — nothing flags it as “unroutable” on its own, so build a habit of checking wait times on tightly-skilled queues specifically.