Skip to main content
    SupportContact
    Field service workflows

    Salesforce work order assignment, handled dynamically.

    Field engineers get work orders that do not match their skills or certifications. Travel time gets ignored; capacity ceilings are guesses. Dispatchers spend their day reassigning manually. Ortoo Orchestrator handles Salesforce work order assignment as a defined workflow, with skills, location, and capacity weighed together.

    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

    Work order assignment, in plain terms.

    Salesforce work order assignment is the workflow that matches each Work Order to the best-fit engineer based on certification, location, equipment, travel time, and current capacity. It runs on intake and on schedule changes, with reassignment when conditions shift.

    Work order routing sits inside Ortoo Orchestrator. The routing capability inside Ortoo Orchestrator extends to Field Service objects, including Work Orders, Service Appointments, and Service Resources, with the same multi-factor logic that handles cases and leads.

    The problem

    Salesforce work order assignment breaks when location, certification, and capacity sit in different systems

    Native Salesforce assignment does not factor in skills, capacity, and territory together as one decision. Salesforce work order assignment usually depends on a dispatcher's spreadsheet, a certification list that lives in HR, and the engineer's calendar. Three sources, three sources of truth, and a Field Service queue that does not reconcile any of them.

    Engineers travel further than they should. Certifications expire without anyone noticing until a job is misassigned. Capacity ceilings are guesses, so peak days drown senior engineers while juniors sit idle.

    Field service routing that ignores certification is field service routing that fails the audit.

    Ortoo Orchestrator runs work order assignment as one workflow. Skills, certifications, location, travel time, and capacity all weigh together in the routing decision, with the audit trail compliance teams expect.

    // HOW IT WORKS

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

    1. 01

      // STEP 01

      Work orders are evaluated against the engineer pool.

      On creation and on schedule changes, the workflow reads the work order against the eligible engineer pool. Certification, skill, location, travel time, and capacity all feed the decision.

      1. Work order in

        Field Service object

      2. Eligible pool

        Cert + skill

      3. Score options

        Distance + capacity

      Step 01 — Match
      01
    2. 02

      // STEP 02

      The best-fit engineer is matched in real time.

      The workflow picks the engineer with the right certification, the closest viable location, and capacity to take the job. If the top match is unavailable, the workflow looks at the next best option.

      1. Best fit engineer

        Top score

      2. Slot job

        Respect calendar

      3. Reserve capacity

        Live ledger

      Step 02 — Schedule
      02
    3. 03

      // STEP 03

      Reassignment fires on schedule and capacity changes.

      Engineers call in sick; jobs run over; certifications expire. The workflow reassigns affected work orders to maintain coverage, with every reassignment logged for the dispatcher.

      1. Notify engineer

        Mobile push

      2. Track changes

        Sick, overruns

      3. Auto-reassign

        Next-best fit

      Step 03 — Dispatch
      03

    What good work order assignment needs

    Three things separate working work order routing from a dispatcher's spreadsheet.

    Most field service teams hit the same three problems. Three things keep the routing workflow operationally useful and compliance-defensible. The path is operationally realistic: start with one workflow at a time, expand step by step as the team is ready.

    Book a demo

    Certification awareness

    Routing respects current certification status, not last quarter's roster.

    Location and travel time

    Closest viable engineer wins, with travel time as a routing input alongside skill.

    Real-time capacity

    Engineer workload refreshes as jobs complete; the next assignment reflects current state.

    Before vs after

    What changes when work order routing runs as a workflow.

    The work orders do not change. What changes is whether the right engineer can take them.

    Before

    Before

    1. 01Dispatcher spreadsheet
    2. 02Static certification list
    3. 03Guessed capacity
    4. 04Manual rerouting

    Three sources of truth and a manual reconciliation every morning.

    After

    With Ortoo Orchestrator

    1. 01Workflow matching
    2. 02Live certification
    3. 03Real-time capacity
    4. 04Auto-reassignment

    One workflow, live data, audit trail on every assignment.

    Where it fits

    Works with the Salesforce tools you already use.

    Salesforce work order assignment with Field Service

    Field ServiceService Appointments

    Native Salesforce Field Service handles scheduling. The workflow extends to multi-factor assignment, applying certification, capacity, and travel time alongside skill match. Both systems coexist, with the workflow handling the assignment decision.

    Work order assignment for regulated field work

    CertificationCompliance

    Regulated industries (utilities, healthcare, telecoms) need work order routing that respects certification expiry and licensing. The workflow checks current certification status before assignment and produces an audit trail compliance teams can read.

    Work order assignment for high-volume dispatch

    High volumeDispatch

    Teams handling hundreds of work orders per day need routing that runs at intake, not in the dispatcher's queue. The workflow holds up at volume, applying the same multi-factor logic to every job.

    Built for field service ops

    Dispatch that runs as a workflow, not a morning spreadsheet.

    Dispatchers stop reconciling spreadsheets.

    When the workflow handles certification, capacity, and location together, dispatchers spend their time on exceptions rather than on daily reassignment. The team's throughput rises in proportion to active engineers.

    Engineers work jobs they are certified and equipped for.

    Certification-aware routing prevents misassignment of jobs that require specific qualifications. Engineers see jobs they can actually complete, and customer escalations from misassigned engineers drop. The dispatch ops team owns this workflow, with service ops adjusting rules as the business changes.

    Field service performance becomes reportable Salesforce data.

    Every routing decision logs on the work order with the inputs that drove it. Service leaders see first-time fix rates, travel time, and reassignment patterns from standard Salesforce reports.

    CertificationSkillLocationTravel timeCapacityEquipmentCustomer tierJob durationSLA window

    Signals the work order workflow evaluates

    Components of work order routing

    Four elements every work order assignment workflow needs to cover.

    Ortoo Orchestrator provides the engine. Certification mappings and travel-time inputs are configured by service ops.

    Match work orders to engineers with current, valid certifications for the job.

    // RULE CONFIG

    Regulated field service, certification-gated

    object
    Work Order + Service Appointment
    certifications
    Live, expiry-checked
    location
    Travel time API
    capacity
    Daily hours remaining
    fallback
    Next-best in territory
    audit
    Inputs + outcome logged

    IF engineer holds valid cert AND travel ≤ threshold AND capacity > 0 THEN assign; ELSE next-best in pool.

    Case studies

    Teams running work order routing as a workflow.

    Related use cases

    Adjacent assignment workflows in Ortoo Orchestrator.

    FAQ

    Common questions

    How does this work with Salesforce Field Service?+

    Native Salesforce Field Service handles scheduling and service resource management. The workflow inside Ortoo Orchestrator handles the assignment decision, applying multi-factor logic that goes beyond what Field Service does natively. Both run alongside each other.

    Can the workflow respect certification expiry?+

    Yes. Certification status is one of the routing inputs. If an engineer's certification expires, the workflow stops assigning the relevant work orders to them until the certification is renewed.

    How is travel time calculated?+

    Travel time can be calculated from the engineer's current location and the work order address, or pulled from a configured travel-time API. The workflow uses whichever source the team has configured.

    What happens when an engineer calls in sick?+

    The workflow reassigns affected work orders to the next-best-fit available engineer, respecting certification, location, and capacity. Every reassignment is logged for the dispatcher to review.

    Can the workflow handle multi-day or multi-engineer jobs?+

    Yes. Multi-engineer jobs are configured as work order types with their own routing rules. The workflow assigns each engineer slot independently, respecting the same multi-factor logic.

    Does this work for custom Field Service objects?+

    Yes. The routing engine extends to any Salesforce object, including custom Field Service objects the team has defined for industry-specific workflows.

    Can operations teams adjust the routing rules without code?+

    Yes. All routing logic, certification mapping, and travel-time inputs are configured declaratively inside Salesforce setup. Service ops adjusts the workflow as the business changes.

    Match engineers to jobs

    Map the work order routing your field team should be running.

    Book a 30-minute conversation. We will walk through your current dispatch flow and where multi-factor routing removes the reconciliation work.

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