--- title: "Salesforce routing, across every object | Ortoo" description: "Salesforce routing sends every record to the right owner by skills, capacity and SLA. See how native rules and Omni-Channel work, and where they stop." lang: en json-ld: | [ { "@context": "https://schema.org", "@type": "Organization", "name": "Ortoo", "url": "https://ortooapps.com/", "logo": "https://ortooapps.com/ortoo-logo-square.png", "parentOrganization": { "@type": "Organization", "name": "Ascendx" } }, { "@context": "https://schema.org", "@type": "WebSite", "name": "Ortoo", "url": "https://ortooapps.com/" }, { "@context": "https://schema.org", "@type": "Article", "headline": "Salesforce routing", "description": "Salesforce routing sends every record to the right owner by skills, capacity and SLA. See how native rules and Omni-Channel work, and where they stop.", "dateModified": "2026-07-16", "datePublished": "2026-07-16", "author": { "@type": "Organization", "name": "Ortoo" }, "publisher": { "@type": "Organization", "name": "Ortoo" }, "mainEntityOfPage": "https://ortooapps.com/resources/pillar/salesforce-routing" }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://ortooapps.com/" }, { "@type": "ListItem", "position": 2, "name": "Resources", "item": "https://ortooapps.com/resources" }, { "@type": "ListItem", "position": 3, "name": "Salesforce routing", "item": "https://ortooapps.com/resources/pillar/salesforce-routing" } ] }, { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is routing in Salesforce?", "acceptedAnswer": { "@type": "Answer", "text": "Routing in Salesforce is the logic that assigns each record to the right owner. Native assignment rules and Omni-Channel cover leads and cases. Ortoo Orchestrator extends routing to every object, weighs skills, capacity and SLA together, and keeps the decision adjustable after the record is created." } }, { "@type": "Question", "name": "What is the difference between case routing and case assignment?", "acceptedAnswer": { "@type": "Answer", "text": "They describe the same job. Case routing, case assignment and case distribution all mean delivering a case to the right owner. The difference is only depth: static rules assign once, multi-factor routing reads case and agent context together." } }, { "@type": "Question", "name": "How do I set up skills-based routing in Salesforce?", "acceptedAnswer": { "@type": "Answer", "text": "Native skill-based routing tags agents with skills and matches work to them. To route on skills together with capacity, availability and SLA, teams add a matching layer such as Q-assign on Ortoo Orchestrator, configured in Salesforce setup without code." } }, { "@type": "Question", "name": "Can Salesforce reassign a case after it is created?", "acceptedAnswer": { "@type": "Answer", "text": "Native assignment rules fire once and do not reassign on their own. Ortoo Orchestrator rebalances on a schedule, so a case moves when capacity, availability or SLA risk changes, not only at creation." } }, { "@type": "Question", "name": "How is Omni-Channel routing different from Q-assign?", "acceptedAnswer": { "@type": "Answer", "text": "Omni-Channel delivers work from queues to agents in the console. Q-assign matches the right agent on skills, capacity, availability and SLA before delivery and keeps adjusting after. They work together; Q-assign extends Omni-Channel rather than replacing it." } }, { "@type": "Question", "name": "Does Salesforce routing work for custom objects?", "acceptedAnswer": { "@type": "Answer", "text": "Native assignment rules cover only leads and cases. Ortoo Orchestrator routes custom objects, opportunities, work orders and tasks on the same model as leads and cases." } }, { "@type": "Question", "name": "What is round robin routing in Salesforce?", "acceptedAnswer": { "@type": "Answer", "text": "Round robin assigns records to each owner in a group in turn, so work is distributed evenly. Ortoo Orchestrator supports weighted and conditional round robin, plus controlled pull queues that stop cherry-picking." } }, { "@type": "Question", "name": "Do routing decisions respect business hours and out-of-office?", "acceptedAnswer": { "@type": "Answer", "text": "Native routing can assign work to agents who are offline. Ortoo Orchestrator reads login state, working hours and calendar out-of-office, so records are matched to agents who can actually start them." } } ] } ] --- [Skip to main content](#main-content) [Support](/support)[Contact](/contact) [![Ortoo logo, workflow orchestration for Salesforce](/assets/ortoo-logo-gradient-C54UkOOH.webp)](/) Ortoo Orchestrator Solutions Why Ortoo Resources About [Pricing](/pricing) [Map your workflow](/contact?intent=workflow-mapping)[Book a demo](/contact?intent=demo) [Book a demo](/contact?intent=demo) On this page 1. [01 What is Salesforce routing?](#what-is-salesforce-routing) 2. [02 How does native Salesforce routing work?](#native-salesforce-routing) 3. [03 Where native routing stops](#where-native-stops) 4. [04 Routing by object: case, lead, and any Salesforce object](#routing-by-object) 5. [05 Omni-channel routing vs Q-assign routing](#omni-channel-vs-q-assign) 6. [06 Skills-based routing in Salesforce](#skills-based-routing) 7. [07 How Salesforce routing is set up](#how-its-set-up) Salesforce routing # Salesforce routing Salesforce routing is how a new record reaches the right owner, by skills, capacity, territory and SLA, the moment it is created. Salesforce provides assignment rules and Omni-Channel, which cover the basic shape. They route leads and cases once, at the point of creation, and they do not adapt when workload, availability or SLA state change afterward. Ortoo Orchestrator adds the routing layer above the assignment rules and Omni-Channel already running, so every object is matched on the conditions that actually decide the right owner, and the decision stays logged and adjustable without a release. [Book a demo](/contact?intent=demo)[See Q-assign](/solutions/q-assign) INSIGHT 33,600 hrs Reclaimed a year at Cars.com Quantified outcome from ops teams running an orchestration layer on top of existing Salesforce automation. Definition ## What is Salesforce routing? Salesforce routing is the logic that delivers a record to the right owner at the right time. The terms case assignment, case routing and case distribution describe the same job for cases; the same idea applies to leads, opportunities, work orders and custom objects. Routing decides the owner by one or more strategies: the right person (skills, capacity), the right time (availability, business hours), and the right context (territory, language, account, priority). Native Salesforce routes on fixed field values. Routing that reflects how a team actually works reads the state of the team and the record together, at the moment of assignment. Native Salesforce ## How does native Salesforce routing work? Salesforce ships two mechanisms. Assignment rules match leads and cases to a queue or user against fixed criteria, and fire once, at creation or on update. Omni-Channel distributes work from queues to agents in the console, with queue-based routing, skill-based routing, and external routing that hands the logic to a third-party tool over APIs. Between them they cover the basic shape: get a lead or case to a queue, and push it to an available agent. What they do not do is adapt after the rule fires, weigh several factors into one decision, or route objects beyond leads and cases. The gap ## Where native routing stops Six questions signal that native routing needs a layer above it. Each is a real limit, not a criticism. - Reassignment after creation. Assignment rules fire once. If a record needs to move after it is created, that is manual. - Real-time workload. Native routing reads workload at the point of assignment, not on a rolling basis as work is resolved. - Complexity weighting. Several factors (product, language, availability, location, tier) rarely combine into a single defensible score. - Business hours and out-of-office. Records get assigned to agents who are offline, creating a lag between arrival and response. - Round robin and pull. Controlled, weighted distribution and pull queues that stop cherry-picking are not native behaviours. - New channels inheriting the logic. As inbound channels are added, applying the same assignment logic to each one is manual work. Ortoo Orchestrator answers each: continuous rebalancing handles reassignment and real-time workload, multi-factor matching handles complexity weighting, schedule-aware routing handles business hours and out-of-office, and object-agnostic routing applies one model across every channel and object. Deterministic logic controls the decision, and every routing decision is logged and reportable. Coverage ## Routing by object: case, lead, and any Salesforce object Native assignment rules cover leads and cases. Ortoo Orchestrator routes leads, cases, opportunities, work orders, tasks and custom objects on one model, so the same skills, capacity and SLA logic applies wherever work arrives. See it applied to each object in the routing cluster below: case routing, lead routing, lead distribution, opportunity assignment, work-order assignment, custom-object assignment and territory assignment. Omni-Channel ## Omni-channel routing vs Q-assign routing Omni-Channel and Q-assign are not either-or. Omni-Channel delivers work to agents in the console. Q-assign matches the right agent on rich attributes (skills, capacity, availability, SLA) before delivery, and keeps adjusting after it. Teams already on Omni-Channel extend it with Q-assign rather than replace it. Salesforce is retiring standard Omni-Channel and moving orgs onto Enhanced Omni-Channel, which is a natural moment to add the matching layer above it. Strategy ## Skills-based routing in Salesforce Skills-based routing assigns work to the agent whose skills fit the record. Native skill-based routing tags agents and matches on skills alone. Multi-factor routing reads skills together with current capacity, availability and SLA state, so a skilled agent who is at capacity or offline is not handed work they cannot start. Setup ## How Salesforce routing is set up Routing on Ortoo Orchestrator is configured by operations in Salesforce setup, point and click, no code. Rules are readable, the routing decision is logged on the record, and changes take effect without a release cycle. A full routing model can be built and tested in a sandbox before anything reaches production. Related reading ## Explore the routing cluster [ Intelligent case routing in Salesforce Case routing that reads skills, capacity and SLA together at the point of assignment. ](/use-cases/intelligent-case-routing-salesforce)[ Lead routing in Salesforce The full lead routing workflow, from capture to qualified handoff. ](/resources/pillar/lead-routing-salesforce)[ Q-assign, routing on Ortoo Orchestrator The routing engine: object-agnostic matching on skills, capacity, availability and SLA. ](/solutions/q-assign)[ Omnichannel 2.0 Extend Omni-Channel with the matching layer above console delivery. ](/solutions/omnichannel-orchestration)[ Omni-channel routing in Salesforce How native Omni-Channel routing works, and where it needs extending. ](/resources/blog/omni-channel-routing-salesforce)[ Skills-based routing without overloading admins Designing skills-based routing that reads capacity and availability too. ](/resources/blog/how-to-design-skills-based-routing-in-salesforce-without-overloading-admins)[ Operational workflow management in Salesforce The coordination layer above Salesforce automation that routing sits within. ](/resources/pillar/operational-workflow-management-salesforce)[ Salesforce Help: create assignment rules Salesforce's own documentation on native lead and case assignment rules. ](https://help.salesforce.com/s/articleView?id=service.creating_assignment_rules.htm&type=5)[ Salesforce Help: Omni-Channel routing Salesforce's documentation on queue, skill and external Omni-Channel routing. ](https://help.salesforce.com/s/articleView?id=ind.admin_utilization_management_routing.htm&type=5)[ Salesforce Help: Enhanced Omni-Channel Salesforce's guidance on moving from standard to Enhanced Omni-Channel. ](https://help.salesforce.com/s/articleView?id=004868010&language=en_US&type=1) Frequently asked ## Common questions What is routing in Salesforce? Routing in Salesforce is the logic that assigns each record to the right owner. Native assignment rules and Omni-Channel cover leads and cases. Ortoo Orchestrator extends routing to every object, weighs skills, capacity and SLA together, and keeps the decision adjustable after the record is created. What is the difference between case routing and case assignment? They describe the same job. Case routing, case assignment and case distribution all mean delivering a case to the right owner. The difference is only depth: static rules assign once, multi-factor routing reads case and agent context together. How do I set up skills-based routing in Salesforce? Native skill-based routing tags agents with skills and matches work to them. To route on skills together with capacity, availability and SLA, teams add a matching layer such as Q-assign on Ortoo Orchestrator, configured in Salesforce setup without code. Can Salesforce reassign a case after it is created? Native assignment rules fire once and do not reassign on their own. Ortoo Orchestrator rebalances on a schedule, so a case moves when capacity, availability or SLA risk changes, not only at creation. How is Omni-Channel routing different from Q-assign? Omni-Channel delivers work from queues to agents in the console. Q-assign matches the right agent on skills, capacity, availability and SLA before delivery and keeps adjusting after. They work together; Q-assign extends Omni-Channel rather than replacing it. Does Salesforce routing work for custom objects? Native assignment rules cover only leads and cases. Ortoo Orchestrator routes custom objects, opportunities, work orders and tasks on the same model as leads and cases. What is round robin routing in Salesforce? Round robin assigns records to each owner in a group in turn, so work is distributed evenly. Ortoo Orchestrator supports weighted and conditional round robin, plus controlled pull queues that stop cherry-picking. Do routing decisions respect business hours and out-of-office? Native routing can assign work to agents who are offline. Ortoo Orchestrator reads login state, working hours and calendar out-of-office, so records are matched to agents who can actually start them. See it on your routing ## Show us one record type. We will show you the routing. Bring the object that generates the most manual reassignment, cherry-picking, or off-hours lag. We will map it as a governed routing workflow in Ortoo Orchestrator, on your existing Salesforce setup. [Book a demo](/contact?intent=demo)[See Q-assign](/solutions/q-assign) ![Ortoo logo, workflow orchestration for Salesforce](/assets/ortoo-logo-C6Mjw-cG.svg) Workflow orchestration in Salesforce, executed by specialized agents under controlled AI. PRODUCT - [Orchestrator](/orchestrator) - [Solutions](/solutions) - [Pricing](/pricing) ## PRODUCT - [Orchestrator](/orchestrator) - [Solutions](/solutions) - [Pricing](/pricing) WHY - [Why Orchestrator](/why-orchestrator) - [Customers](/case-studies) ## WHY - [Why Orchestrator](/why-orchestrator) - [Customers](/case-studies) RESOURCES - [Blog](/resources/blog) - [Downloads](/resources/downloads) ## RESOURCES - [Blog](/resources/blog) - [Downloads](/resources/downloads) USE CASES - [Case assignment](/case-assignment) - [Lead assignment](/lead-assignment-in-salesforce) - [Email-to-Anything](/solutions/email-to-anything) - [See all use cases](/use-cases) ## USE CASES - [Case assignment](/case-assignment) - [Lead assignment](/lead-assignment-in-salesforce) - [Email-to-Anything](/solutions/email-to-anything) - [See all use cases](/use-cases) COMPANY - [About](/about-ortoo) - [Ascendx Approach](/ascendx-approach) - [Careers](https://ascendx.cloud/vacancies/) - [Contact](/contact) ## COMPANY - [About](/about-ortoo) - [Ascendx Approach](/ascendx-approach) - [Careers](https://ascendx.cloud/vacancies/) - [Contact](/contact) LEGAL - [Privacy policy](/privacy) - [Terms of service](/terms) - [Cookie policy](/cookies) ## LEGAL - [Privacy policy](/privacy) - [Terms of service](/terms) - [Cookie policy](/cookies) © 2026 Ortoo. An Ascendx Company. All rights reserved. [](https://www.linkedin.com/company/ortooapps/)[](https://x.com/OrtooApps)