Skip to main content
    SupportContact
    Custom orchestration

    Salesforce custom object assignment.

    Native Salesforce assignment rules cover leads and cases. Everything else falls back to manual ownership or developer-built logic. Custom records, claims, work orders, applications, partner submissions, all need routing too. Ortoo Orchestrator handles Salesforce custom object assignment as one workflow, on any object the team has defined.

    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

    Custom object assignment, in plain terms.

    Salesforce custom object assignment is the workflow that routes any standard or custom Salesforce object to the right owner based on multi-factor rules. The routing engine that handles leads and cases extends to claims, applications, work orders, partner submissions, or any record the team defined.

    Custom object routing sits inside Ortoo Orchestrator. The routing capability inside Ortoo Orchestrator works on any Salesforce object, not just leads and cases, with the same skills, capacity, and rule logic available to every record type.

    The problem

    Salesforce custom object assignment is where native rules stop

    Native Salesforce assignment does not factor in skills, capacity, and territory together as one decision. Salesforce custom object assignment is the workflow most teams build by hand. Native assignment rules cover leads and cases; everything else needs Apex or Flow logic. Custom industry records, partner submissions, work orders, application forms, and intake objects all get owner-assigned manually or through one-off code.

    Manual assignment scales badly. Code-built logic drifts as the business changes. When the team needs to update the rule, an engineering ticket opens and the change waits for a release. Operations cannot tune the routing without going through engineering.

    The routing engine that handles leads and cases should handle every record the business creates.

    Ortoo Orchestrator runs custom object assignment as one workflow. The same routing capability that handles leads and cases works on any Salesforce object, configured declaratively by ops without code.

    // HOW IT WORKS

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

    1. 01

      // STEP 01

      Pick the object and define the rule.

      Choose any standard or custom Salesforce object. Configure the routing matrix in setup: skills, capacity, territory, and any custom criteria the team needs.

      1. Record created

        Any object

      2. Apply rule

        Configured matrix

      3. Custom criteria

        Per-object fields

      Step 01 — Read
      01
    2. 02

      // STEP 02

      The workflow assigns on intake and on update.

      When records are created or updated, the workflow evaluates them against the rule and assigns the best-fit owner. Real-time execution; no batch window.

      1. Skills + capacity

        Same engine

      2. Territory or custom

        Per-object rule

      3. Next best match

        If top is full

      Step 02 — Match
      02
    3. 03

      // STEP 03

      Email-to-Anything captures records from outside Salesforce.

      Inbound email creates the custom-object record directly through Email-to-Anything, the email orchestration capability inside Ortoo Orchestrator. The routing workflow then runs on the new record.

      1. Set owner

        Salesforce record

      2. Log decision

        Inputs recorded

      3. Real-time update

        No batch wait

      Step 03 — Assign
      03

    What good custom object assignment needs

    Three things separate working custom object routing from a developer queue.

    Custom object routing usually means a Flow or Apex class that nobody on the ops team can change. Three things keep the workflow ops-owned and the records moving. The path is operationally realistic: start with one workflow at a time, expand step by step as the team is ready.

    Book a demo

    Object-agnostic engine

    The routing logic that handles leads and cases works on any object without rebuild.

    Declarative configuration

    Ops configures rules in Salesforce setup; no Apex, no Flow rewrite, no release cycle.

    Intake to assignment in one workflow

    Email or form intake creates the record, and routing runs in the same step.

    Before vs after

    What changes when custom object routing runs as a workflow.

    The records do not change. What changes is who owns the routing logic.

    Before

    Before

    1. 01Apex or Flow logic
    2. 02Engineering-owned
    3. 03Manual assignment
    4. 04Batch updates

    Custom object routing depends on engineering bandwidth. Changes wait for releases.

    After

    With Ortoo Orchestrator

    1. 01Workflow logic
    2. 02Ops-owned
    3. 03Auto-assigned on intake
    4. 04Real-time updates

    Custom object routing runs as a workflow. Ops adjusts the rules as the business changes.

    Where it fits

    Works with the Salesforce tools you already use.

    Salesforce custom object assignment for industry verticals

    InsuranceHealthcare

    Industries with custom records (insurance claims, healthcare cases, applications) need routing that respects industry-specific rules. The workflow handles licensing, certification, and regulatory routing on the same engine that handles leads and cases.

    Custom object assignment for partner and channel records

    PartnerChannel

    Partner-led businesses use custom objects for partner submissions, joint deals, and channel coordination. The workflow routes each record to the right partner manager, internal owner, or channel team based on configurable rules.

    Custom object intake through Email-to-Anything

    Email-to-AnythingIntake

    Inbound email creates the custom-object record directly through Email-to-Anything, the email orchestration capability inside Ortoo Orchestrator. The routing workflow then runs on the new record without manual intervention.

    Built for operations

    One routing engine for every record the business creates.

    Ops owns the routing logic, not engineering.

    Configuration is declarative inside Salesforce setup. When the business changes how it wants custom records routed, the team that owns operations adjusts the workflow directly. No release cycle, no developer ticket.

    Every record gets the same routing engine.

    Leads, cases, opportunities, claims, work orders, applications, custom partner records: all routed by the same engine, configured differently. The team stops maintaining parallel assignment logic for each object type.

    Intake and routing happen in one workflow.

    Email or form intake creates the record; routing assigns the owner; both run in the same step. The handoff between intake and assignment that used to be a manual checkpoint becomes invisible.

    Object typeSkillCapacityTerritoryLicensingCustom fieldSourcePriorityPartner

    Signals the routing workflow evaluates

    Components of custom object assignment

    Four elements every custom object workflow needs to cover.

    Ortoo Orchestrator provides the engine. Per-object rules and intake mappings are configured by operations.

    Routing engine works on any standard or custom Salesforce object.

    // RULE CONFIG

    Insurance claim, licensed adjuster routing

    object
    Claim__c custom object
    intake
    Email-to-Anything
    skill
    State licence + line of business
    capacity
    Active caseload < 30
    territory
    Stamped on intake
    fallback
    Hold pool for review

    IF state licence matches AND caseload < 30 THEN assign; ELSE queue to hold pool for supervisor review.

    Case studies

    Teams running custom object routing as a workflow.

    Related use cases

    Adjacent workflows in Ortoo Orchestrator.

    FAQ

    Common questions

    Which Salesforce objects can this route?+

    Any standard or custom Salesforce object. Leads, cases, opportunities, work orders, applications, claims, partner submissions, and any team-defined object are all supported through declarative configuration.

    How is this different from native assignment rules?+

    Native assignment rules cover leads and cases only, with single-criterion routing. The workflow inside Ortoo Orchestrator runs on any object, applies multi-factor logic in one step, and considers real-time capacity.

    Do we still need Apex or Flow for custom routing?+

    Not for the routing decision itself. The workflow handles routing logic declaratively. Apex and Flow remain useful for downstream side-effects, but the assignment decision is configured by ops in Salesforce setup.

    How does this work with Email-to-Anything?+

    Email-to-Anything captures inbound email as a Salesforce record on any object. The routing workflow then assigns the new record to the right owner based on the configured rules, all in the same intake-to-assignment step.

    Can operations teams adjust rules per object without code?+

    Yes. Each object has its own routing configuration inside Salesforce setup. Ops adjusts the rule for any object without engineering involvement and without affecting other objects' routing.

    What happens when no owner matches the criteria?+

    The workflow defines the fallback explicitly. Common patterns are queueing to a holding pool, escalating to a manager, or relaxing one criterion at a time until a match is found.

    Is routing data reportable in standard Salesforce reporting?+

    Yes. Every routing decision is logged with the inputs that drove it, the matched owner, and the timestamp. Standard reports and dashboards pick it up automatically across every object the workflow handles.

    Route any object as a workflow

    Map the custom object workflow your team should be running.

    Book a 30-minute conversation. We will walk through your custom routing logic and where workflow execution removes the engineering dependency.

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