Skip to main content
    SupportContact
    Use case · Intelligent routing

    Intelligent case routing in Salesforce.

    Static assignment rules route cases without context. Skills, workload, and SLA state aren't part of the decision. Ortoo Orchestrator evaluates all three together at the point of assignment, inside Salesforce, owned by operations.

    TEAMS RUNNING ON ORTOO ORCHESTRATOR

    IG
    Jaguar Land Rover
    Komatsu
    OppFi
    Sage
    Splunk
    Verivox
    Volvo
    IG
    Jaguar Land Rover
    Komatsu
    OppFi
    Sage
    Splunk
    Verivox
    Volvo

    What it is

    Intelligent case routing, in plain terms.

    Intelligent case routing in Salesforce is rules-based assignment that reads case context, agent state, and SLA targets together, then routes to the agent best placed to resolve. It replaces static round-robin and queue-based assignment with multi-factor logic.

    Standard Salesforce ships assignment rules and Omni-Channel. They handle the basic shape. Ortoo Orchestrator adds the skills matching, capacity weighting, and SLA-aware escalation that operations teams need to keep routing decisions defensible at scale.

    Why this matters

    Routing without context is routing that needs babysitting.

    Intelligent case routing in Salesforce starts from one premise: the assignment decision should reflect what the team actually knows about the case and the agent.

    When that decision is reduced to a queue and a round-robin, the team ends up working around it. Cases get reassigned manually. Senior agents pick the queue clean. Junior agents inherit work they aren't ready to handle. Visibility lives in spreadsheets.

    Ortoo Orchestrator evaluates skills, capacity, priority, and SLA against rules operations teams configure in Salesforce setup. The routing decision is logged, reportable, and adjustable without a release cycle.

    // HOW IT WORKS

    Triggered by case context. Not by who is watching the queue.

    1. 01

      // STEP 01

      Read the case on arrival.

      Channel, priority, customer tier, region, language, and any custom field are evaluated the moment the case is created. The context the team would use manually is captured as data, not as tribal knowledge.

      1. Case arrives

        Channel, priority

      2. Read attributes

        Tier, region, language

      3. Custom fields

        Captured as data

      Step 01 — Read
      01
    2. 02

      // STEP 02

      Score against live agent state.

      Skills, current workload, availability, and SLA risk are weighed together against the rules operations has defined. The match is deterministic and reviewable, not opaque.

      1. Match skills

        Required vs available

      2. Weigh capacity

        Live workload

      3. Factor SLA risk

        Priority weighted

      Step 02 — Score
      02
    3. 03

      // STEP 03

      Assign, log, and escalate.

      The chosen agent gets the case, the decision is logged in Salesforce, and timers start. If no agent matches or the case stalls, the defined escalation path fires automatically.

      1. Assign agent

        Decision recorded

      2. Log in Salesforce

        Reviewable trail

      3. Arm escalation

        Fires before breach

      Step 03 — Assign
      03

    What intelligent routing requires

    The three signals that separate guess-work from defensible routing.

    Intelligent routing isn't a feature. It is a decision built from three signals, evaluated together, every time a case arrives.

    Book a demo

    Skills

    Agent expertise is mapped against case attributes in Salesforce, so specialist work reaches specialists by default.

    Capacity

    Workload limits are evaluated live so capacity-weighted routing distributes cases fairly across the team.

    SLA

    Priority and SLA risk weigh into the decision, so high-priority work gets surfaced instead of waiting its turn.

    Static rules vs intelligent routing

    The same backlog, decided very differently.

    Static rules ignore the parts of the decision that matter most. Intelligent routing reads them on every case.

    Before

    Native rules only

    1. 01Round-robin or queue catch-all
    2. 02Skills tracked in spreadsheets
    3. 03Capacity assumed, not measured
    4. 04Escalation handled manually

    The team works around the rules instead of with them.

    After

    With Ortoo Orchestrator

    1. 01Multi-factor decision per case
    2. 02Skills mapped inside Salesforce
    3. 03Capacity weighted at assignment
    4. 04Escalation fires before SLA breach

    The decision is recorded, reportable, and tunable by operations.

    Where it fits

    Works with the Salesforce tools you already use.

    With Salesforce Omni-Channel

    Service Cloud

    Omni-Channel handles channel distribution. Intelligent case routing sits on the assignment decision itself, adding the skills, capacity, and SLA logic Omni-Channel does not evaluate. The two run together.

    For Salesforce Field Service

    Field Service

    Field cases require routing that reads location, certification, equipment, and travel. The same engine extends to Work Orders, Service Appointments, and Service Resources, with each rule visible to operations.

    Intelligent routing vs lead routing

    Service Ops

    Lead routing optimises for speed-to-contact and territory. Case routing optimises for skills match, SLA handling, and capacity. Ortoo Orchestrator handles both inside one engine, so revenue and service teams share infrastructure.

    Built for service operations

    Routing logic operations teams own, end to end.

    Configured by operations, not by developers.

    Rules live in Salesforce setup. Adding a skill, lifting a capacity limit, or rerouting a region is a configuration change, not a release. The team that owns the SLA owns the rule.

    One step inside a broader workflow.

    Routing is one stage in an orchestrated process. Triage, routing, AI-assisted classification, and SLA escalation run together inside Salesforce, with one audit trail.

    Distribution you can see and adjust.

    Routing decisions are reported back to operations so imbalances surface before they turn into SLA misses. The people closest to the work adjust the rules directly.

    SkillsCapacitySLARegionTierLanguageChannelPriorityWorking hours

    Signals the rule evaluates

    Components of an intelligent routing rule

    Four elements every defensible routing rule covers.

    Ortoo Orchestrator provides the engine. The rule itself is configured by operations.

    Agent expertise is captured in Salesforce against the cases they handle, so specialist work reaches specialists.

    // RULE CONFIG

    Tier-2 EMEA — billing skill

    channel
    Email, web
    priority
    >= P2
    region
    EMEA
    skills
    Billing, Tier-2
    capacity
    < 75% utilization
    sla
    Respond 30m

    IF skill = Billing AND region = EMEA THEN route → EMEA-Billing-Pod, weight by capacity.

    Case studies

    Service teams running intelligent routing today.

    Related use cases

    Adjacent routing patterns in Ortoo Orchestrator.

    FAQ

    Common questions

    What makes routing 'intelligent' vs standard assignment?+

    Intelligent routing evaluates multiple signals (skills, capacity, SLA, priority, region) together against operations-owned rules, instead of relying on round-robin or single-factor queue logic. Decisions are deterministic, reviewable, and adjustable.

    Does this replace Salesforce assignment rules?+

    No. It runs alongside them. Native rules stay where they fit; Ortoo Orchestrator handles the cases that need multi-factor logic and SLA-aware escalation.

    How does it interact with Omni-Channel?+

    Omni-Channel handles channel-level distribution. Intelligent case routing sits on the assignment decision itself. Together they cover channel routing and multi-factor assignment.

    Who configures the routing rules?+

    Operations teams, in Salesforce setup. Rule changes do not require a developer or a release cycle.

    Can it route custom objects?+

    Yes. Any Salesforce object can participate in routing workflows, including custom objects and Work Orders.

    How does AI fit in?+

    AI is used for classification, prioritisation, and assist; deterministic routing logic stays in control. Teams can introduce AI gradually with human-in-the-loop fallback and BYOM support.

    What changes first when this goes live?+

    Manual reassignment drops, capacity balance improves, and SLA breaches caught reactively become escalations triggered proactively.

    Getting started

    See intelligent routing on your cases.

    Book a 30-minute session. We will map one of your case-routing scenarios and show where Ortoo Orchestrator would change the outcome.

    Installs natively into Salesforce. Most teams have working routing within a few days, adjusted by operations as the business changes.