Revenue workflow orchestration

Lead routing in Salesforce

Lead routing is not the moment a lead gets assigned. It is the full sequence from the moment a record is created to the moment a qualified prospect is in an active sales conversation with the right representative. That sequence includes enrichment, scoring, assignment, outreach initiation, and the handoff from SDR to AE. Most Salesforce environments handle some of these steps. Few govern the sequence as a single defined workflow.

Salesforce provides assignment rules that match leads to queues or users based on field values. They fire once, at creation or on update. They do not adapt to what is happening in the team at the moment of assignment: who is at capacity, which territory was restructured last week, which lead source has an agreed two-hour SLA. That context lives outside the rule, and someone has to apply it manually when the rule gets it wrong.

A practical test: can your team answer three questions about any open lead right now? Who owns it. What stage of the routing workflow it is in. What should happen next and when. If any of those answers require checking with a person rather than reading a record, the coordination layer is missing.

Lead routing degrades between steps, not within them. The assignment rule fires correctly. The problem is what happens when the assignment is wrong, when the rep does not respond, when the territory no longer reflects the team structure, or when qualification context does not transfer with the record.

Assignment rules that fire but do not adapt

Rules match against field values at the moment of assignment. They cannot reflect capacity: a rep at 100% workload receives the same volume as one with open slots. When a territory changes, the rule reflects the old structure until someone updates it. The result is a steady flow of misroutes that SDRs and managers redistribute manually, without measuring the cost.

Ownership drift between SDR and AE

Routing gets the lead to an SDR. Nothing governs the handoff from SDR to AE. The qualification conversation is not attached to the record in a structured form. If the SDR who owned the lead moves on, or the lead goes cold and reactivates, the context that existed at first contact is gone. Ownership drifts because the workflow does not define what a completed handoff looks like.

Speed-to-lead that degrades as volume grows

When lead volume is low and the team is small, manual coordination keeps pace. As volume increases, the manual steps compound. High-intent and low-intent leads enter the same queue with the same priority. First response time rises. The team adds headcount or asks managers to triage, both absorb cost that a governed routing layer would eliminate.

Territory logic that lags the business

Territory structures change. Regions are split, accounts are reassigned, new verticals open. Updating assignment rules to reflect those changes requires a platform owner or admin. Until the update ships, routing reflects last quarter's structure. High-value accounts reach the wrong rep, and someone in RevOps corrects it after the lead has already aged.

A lead is handled when every stage from capture to qualified handoff is owned by the workflow, not by the person monitoring the queue. Ortoo Orchestrator governs five stages. The same coordination model applies to case management, claims intake, and other operational workflows running on the same platform.

Capture

The lead record is created with source attribution, campaign context, and deduplication applied before routing fires. Missing required fields are requested or appended before the record enters the qualification step. The capture stage ensures the routing layer works with clean data rather than compensating for gaps downstream.

Enrichment and scoring

Data is appended and qualification signals are assessed before the assignment runs. ICP tier, intent signals, and firmographic fit are evaluated at this stage. Routing criteria can reflect lead quality: high-intent enterprise leads route differently from low-intent SMB leads, based on the scoring model the team defines.

Routing and assignment

The lead is matched to the right representative by territory, capacity, qualification tier, and response SLA. Not based on a static assignment rule. A rep at full capacity is skipped. A territory change takes effect without a platform redeploy. Round-robin, skills-based, and capacity-aware assignment are configured options, not custom Apex. Every routing decision is logged.

SDR outreach and handoff

Outreach is initiated with full context: lead source, enrichment data, prior interactions. If the lead does not receive a response within the SLA window, the workflow escalates without waiting for someone to notice. The SDR-to-AE handoff is defined in the workflow: what context transfers, what the acceptance criteria are, what triggers the handoff.

Qualification and close

MQL-to-SQL conversion is governed by the workflow, not by informal agreement between SDR and AE. Context transfers with the record. Leads that do not qualify are archived with a reason code and a complete audit trail. The workflow knows when the lead lifecycle is complete.

1. 01

   Capture

   Clean record, source attributed

2. 02

   Enrichment

   ICP tier and intent assessed

3. 03

   Routing

   Territory, capacity, SLA matched

4. 04

   Outreach

   Context transferred, SLA clock running

5. 05

   Qualification

   MQL to SQL governed, audit complete

Existing assignment rules, Flows, and queue structures remain in place. Ortoo Orchestrator coordinates above those layers. The boundary is precise.

What stays in Salesforce

• Assignment rules and queue structures already configured.
• Flows and process automations running today.
• Territory hierarchy, account ownership, and CRM data model.
• Existing reports, dashboards, and revenue attribution.
• Agentforce agents and enrichment tools already in the stack.

What Ortoo Orchestrator owns

• Routing decisions based on real-time capacity, territory, and qualification tier.
• SDR-to-AE handoff definition: context transfer, acceptance criteria, escalation path.
• SLA enforcement: response time, follow-up cadence, escalation on no-response.
• AI steps applied at enrichment and scoring stages, within defined boundaries.
• Audit trail across the full lead lifecycle, from capture to conversion or disqualification.
• Visibility into where every lead is in the workflow, in real time.

The net result: routing reflects how the team actually works today, not how it worked when the assignment rules were last updated. RevOps changes routing logic in the Ortoo UI without a platform deploy cycle. Territory changes propagate to routing immediately. Every routing decision is auditable.

1. Map the current routing path for your highest-volume lead source. Identify every point where a human steps in to reassign, qualify, or escalate manually.
2. Define the routing criteria for that lead type: territory, capacity threshold, qualification tier, and response SLA. Write down how routing actually works today, not how the rule was written.
3. Configure the routing workflow in Ortoo Orchestrator above the existing assignment rules. The existing rules remain in place. Ortoo adds the coordination layer above them.
4. Run the new routing layer in parallel for one week. Compare first-touch assignment accuracy against the manual correction log from the same period.
5. Enable the full routing workflow once accuracy is confirmed. Shift additional lead types from the same foundation, one at a time.
6. Add the next routing condition as a new Function Instance: a second territory tier, a new qualification signal, a capacity threshold for a growing team.

Most teams have one lead type routing accurately within a few weeks. Assignment rules have not changed. The coordination layer above them is now handling what manual practice was handling before.