Skip to main content
    SupportContact
    Service workflows

    Salesforce IT support ticketing, handled as a workflow.

    IT support tickets sit in queues. Routing rules cannot tell which engineer can actually take the work. SLA breaches show up in reporting after the damage is done. Ortoo Orchestrator handles IT support ticketing in Salesforce as one defined workflow, from intake through triage, routing, and escalation.

    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

    IT support ticketing, in plain terms.

    Salesforce IT support ticketing means running help desk and IT service management workloads on Salesforce, with intake, triage, routing, and escalation as one defined workflow. Engineers pick up tickets matched to skills and capacity, not just queue order.

    The ticketing workflow sits inside Ortoo Orchestrator. Intake captures tickets from email and portal channels, triage classifies them, the routing capability inside Ortoo Orchestrator matches the best engineer, and every action is logged in Salesforce.

    The problem

    Salesforce IT support ticketing fails when intake, triage, and routing are separate logic

    Salesforce has the objects, the data, and the events. What most teams still lack is the workflow that orchestrates them end to end. Salesforce IT support ticketing is one of those workflows that looks like it works until you measure it. Tickets arrive through email and portal. Native assignment rules route by queue. Engineers cherry-pick. Senior engineers drown in escalations while juniors handle simple tickets.

    SLA breaches show up in reporting after they have happened. Re-routing adds friction at every handoff. Reporting cannot explain why a particular ticket ended up where it did, and operations cannot tune the rules without engineering.

    Ticketing routing that ignores skills is just a queue with extra steps.

    Ortoo Orchestrator runs IT support ticketing as one workflow. Intake captures the ticket, triage classifies it, the routing capability inside Ortoo Orchestrator matches the engineer, and escalation rules fire before SLA breach. Every step is logged.

    // HOW IT WORKS

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

    1. 01

      // STEP 01

      Tickets are captured on intake and classified.

      Inbound tickets from email and portal channels are captured into Salesforce. Classification reads severity, category, and product line, applying AI where the input is free text.

      1. Email or portal

        Inbound channel

      2. Create ticket

        Salesforce record

      3. Classify

        Severity, category

      Step 01 — Intake
      01
    2. 02

      // STEP 02

      The best-fit engineer is matched by skill and capacity.

      The engineer must have the skills the ticket requires and the capacity to take it on. If the top match is at workload limit, the workflow looks at the next best match. This step is handled by the triage, routing, and resolution agents inside Ortoo Orchestrator.

      1. Required skills

        Match profile

      2. Capacity check

        Workload, on-call

      3. Next best match

        If top is full

      Step 02 — Triage
      02
    3. 03

      // STEP 03

      SLA-aware escalation fires before breach.

      Escalation criteria are part of the workflow. SLA-at-risk, repeat contacts, and severity-tier triggers escalate tickets the moment criteria are met, with every action logged.

      1. Assign engineer

        Owner set

      2. SLA watch

        Window monitored

      3. Escalate on risk

        Before breach

      Step 03 — Route
      03

    What good IT support ticketing needs

    Three things separate working IT ticketing from a queue with delays.

    Most IT ticketing problems are routing problems wearing a different label. Three things have to be true for the workflow to actually move work. The path is operationally realistic: start with one workflow at a time, expand step by step as the team is ready.

    Book a demo

    Multi-factor matching

    Skills, capacity, severity, and on-call status evaluated together. Sequential criteria miss the right engineer.

    SLA-aware escalation

    Escalation fires before the SLA window closes, not after the breach shows up in reporting.

    Configurable by ops

    Rules change in Salesforce setup, not through engineering tickets and release cycles.

    Before vs after

    What changes when IT ticketing runs as a workflow.

    The tickets do not change. What changes is whether the right engineer gets them in time.

    Before

    Before

    1. 01Queue-only routing
    2. 02Engineers cherry-pick
    3. 03SLA after the fact
    4. 04Manual escalation

    IT ticketing depends on engineer availability and judgment. SLA breaches surface late.

    After

    With Ortoo Orchestrator

    1. 01Skills + capacity match
    2. 02Routed on intake
    3. 03SLA-aware escalation
    4. 04Rule-driven escalation

    IT ticketing runs on every ticket with the same logic. Escalations fire before breach.

    Where it fits

    Works with the Salesforce tools you already use.

    Salesforce IT support ticketing alongside Omni-Channel

    Omni-ChannelService Cloud

    Omni-Channel covers channel-driven routing for chat and voice. The workflow extends it where IT support needs multi-factor logic, capacity constraints, and on-call rotation handling that Omni-Channel does not do natively.

    Tiered IT support with escalation logic

    Tier 1Tier 2Escalation

    Tiered IT support needs routing that knows which tickets belong at which tier and what counts as escalation. The workflow defines those criteria explicitly: severity, customer tier, repeat contact, and SLA at risk.

    Help desk ticketing for internal IT

    Internal ITHelp desk

    Internal help desks run on the same engine as external IT support. The workflow handles intake from staff portals, classification, routing to the right team, and escalation when tickets miss their internal SLA.

    Built for service operations

    IT ticketing service ops can own, end to end.

    Engineers stop sorting tickets and start solving them.

    When the workflow handles intake, classification, and routing, engineers spend their time on the work. Senior engineers stop spending their first hour reassigning tickets that should have routed correctly the first time. The workflow runs from intake to resolution as one connected execution.

    Operations owns the routing logic, not engineering.

    Service ops adjusts the workflow in Salesforce setup as priorities change. No release cycle, no dependency on engineering bandwidth, no risk of stale routing because a change request is queued.

    Specialised agents do the work, not a single generalist AI.

    Each step is owned by a specialised agent with a defined role, including the Triage, Routing, and Resolution Agents relevant to this workflow. Agents pass context between steps, AI is applied only where interpretation adds value, and deterministic logic controls the rest.

    SeverityCategorySkillCapacityOn-callCustomer tierRepeat contactSLA windowRegion

    Signals the ticketing workflow evaluates

    Components of IT support ticketing

    Four elements every IT ticketing workflow needs to cover.

    Ortoo Orchestrator provides the engine. Routing, escalation, and ticket model are configured by service ops.

    Match tickets to engineers whose recorded skill profile fits the ticket category and severity.

    // RULE CONFIG

    P1 incident, on-call routing

    severity
    P1, customer-facing
    category
    Auth, identity service
    skill
    IAM + on-call
    capacity
    Active engineer only
    SLA
    15 min response
    escalation
    Tier 2 at 10 min

    IF severity = P1 THEN route to on-call IAM engineer; escalate to Tier 2 at 10 min.

    Case studies

    Teams running IT ticketing as a workflow.

    Related use cases

    Adjacent service workflows in Ortoo Orchestrator.

    FAQ

    Common questions

    What makes a Salesforce IT support ticketing system different from native Service Cloud?+

    Native Service Cloud handles case intake and queue assignment. The workflow inside Ortoo Orchestrator adds multi-factor routing, capacity-aware matching, on-call rotation handling, and SLA-aware escalation that native rules cannot do.

    How are tickets captured from email and portal channels?+

    Email tickets flow through the email orchestration capability inside Ortoo Orchestrator, which structures them as Salesforce cases or custom records. Portal tickets land directly through Salesforce forms or community submissions.

    Does this work for tiered support models?+

    Yes. Tiered support is configured as routing rules: severity, customer tier, and escalation thresholds all feed the decision. The workflow can apply different rules for Tier 1, Tier 2, and engineering escalation pools.

    How does on-call rotation work with this?+

    On-call status is an input to the routing decision. The workflow reads who is on call from a configured source and matches tickets to available engineers within the relevant team and severity tier.

    Can operations teams adjust routing rules without code?+

    Yes. All routing, escalation, and SLA logic is configured declaratively inside Salesforce setup. Service ops adjusts the workflow as the business changes, without Apex or Flow rebuilds.

    Does this support custom ticket objects?+

    Yes. The workflow extends to any Salesforce object, including custom IT-specific objects (incidents, changes, problems) that ITSM teams sometimes prefer over standard cases.

    Can we use our own LLM provider?+

    Yes. Bring-your-own-LLM is supported, so teams running an OpenAI, Anthropic, or Google enterprise contract route AI calls through their own provider, with costs and audit trails on their own bill.

    How are SLA breaches handled?+

    SLA risk is one of the routing inputs. The workflow re-prioritises, escalates, or reassigns tickets as the SLA window narrows, before the breach occurs. Every escalation action is logged for compliance reporting.

    Run IT ticketing inside Salesforce

    Map the IT support workflow your team should be running.

    Book a 30-minute conversation. We will walk through your current ticketing flow and where workflow execution removes the queue lag and SLA risk.

    Installs natively into Salesforce. Start with one workflow, expand to others as the team is ready. Pricing follows work completed, not token usage.