How Do I Set Up Lead Routing in Outreach?

What Are the Prerequisites for Lead Routing in Outreach?

Before you open the routing panel, get four foundations solid or every rule you write will misfire in ways that are painful to debug. First, CRM sync must be genuinely bidirectional — ownership, status, and score all flowing both directions. One-way sync is the classic trap: leads route correctly but ownership changes made in Outreach never write back, and reps end up working accounts the CRM still thinks are unassigned. Second, lead scoring needs a single numeric score (0–100) living as a synced field in Outreach, ideally composed from a model that already folds in BANT or MEDDPICC signals rather than raw activity counts. If the score is just "opened three emails," your routing is rewarding noise.

Third, user groups must be built around how you actually sell — territory, product line, or segment (Enterprise West, SMB East, Commercial Renewals). Anything more sophisticated than round-robin is impossible without them, and retrofitting groups after rules exist means rewriting every rule. Fourth, queue definitions should separate inbound (forms, chat), outbound (imported lists), and recycled (returned) leads into distinct queues so each can carry its own logic. Recycled leads in particular need different handling than net-new, and blending them into one queue hides that difference. For a deeper look at building user groups, see How do I create user groups in Outreach for lead routing?.

How Do I Configure the Core Routing Settings in Outreach?

Open Settings > Lead Routing and choose your engine based on segment, not globally. Round Robin spreads leads evenly across a group — it's genuinely correct for high-volume SMB where every rep is interchangeable and speed beats specialization. Weighted Round Robin skews volume toward proven closers, say 50/30/20 across three reps, which is the honest way to protect a ramping rep from drowning while still keeping them in the rotation. Custom Routing Rules are where 2027 complexity actually lives. Model each condition as an if/then policy: Lead Source = Webinar and Lead Score > 70 routes to the Enterprise group; Account Tier = Strategic with a high intent signal routes to the named-account rep; anything under 30 drops to the SDR pool for qualification.

The non-negotiable habit: write the fallback rule *first*, before the clever ones. A catch-all like "route to SMB queue" is the difference between a lead that waits five minutes and a lead that disappears. Under Settings > Lead Assignment, set the method to Custom Routing Rules for anything B2B. Order rules from most to least specific, because Outreach evaluates top-down and stops at the first match — put "Strategic Account + High Intent" above the generic tier rules or it will never fire. Add a cooldown of 7–30 days so a lead can't bounce to a new rep the moment the first one is slow to respond; this is what kills "lead ping-pong." Cap max leads per rep (50/day is a sane starting point) so a volume spike queues for the next available rep instead of burying one person under leads they can't possibly work.

How Do I Map CRM Fields to Outreach Routing Conditions?

Routing reads from the CRM, so the mapping layer is where most "the rule didn't fire" tickets actually originate. In Outreach > Settings > CRM Mapping, confirm the fields your rules reference — Lead_Score__c, Account_Tier__c, Intent_Signal__c, Buying_Stage__c — are present, synced, and populated on real records, not just defined in the schema. The elegant pattern is to precompute routing decisions upstream: a Salesforce formula field or HubSpot calculated property named Route_To__c that concatenates territory and segment into a single token like West_Enterprise, which you then match to a user group by name. That collapses a dozen brittle conditions into one string comparison.

Always dry-run the mapping with a live sample record before trusting it — a field that's blank on 40% of leads will route them all to your fallback and you'll swear the engine is broken. For firmographic routing, ensure fields like Annual_Revenue__c or Employee_Count__c are mapped and numeric. A rule such as "if Employee_Count > 500 → route to Enterprise User Group" keeps large, complex accounts out of pools tuned for velocity. For more on field mapping best practices, see How do I map Salesforce fields to Outreach for routing?.

How Do I Integrate AI Scores from Clari and Gong into Routing?

This is where routing stops being static. Clari and Gong write real-time intent back to your CRM, and Outreach reads it on the next sync. The pattern in motion: a target-account contact hits your pricing page, 6sense flags the intent, Clari lifts the lead score to 85, and your rule "Lead Score > 80 → route to AE" fires within the sync window. Gong adds a relationship dimension — when a recorded call surfaces a new champion, Gong can write that back and let you route the lead to the rep who actually built rapport rather than a cold SDR.

The architecture is indirect: Outreach doesn't read Gong or Clari scores natively, so the CRM becomes the single source of truth. Have those tools write a custom field like Intent_Score__c back to the CRM, map that field into Outreach, and reference it in your rules. The guardrail here matters: AI scores oscillate, so set a floor (say 50) before a lead is allowed to reach a senior rep, and add a staleness rule that re-routes anything untouched for fourteen days so a momentarily hot lead doesn't rot in one queue. For a deeper dive, see How do I feed 6sense and Demandbase intent signals into my routing rules?.

Decision Tree: Lead Routing Logic

How Do I Handle Lead Recycling with AI Re-scoring?

Cold leads aren't dead; they're dormant, and treating them as trash wastes acquisition spend. When a lead goes quiet for fourteen days, recycle it and let Clari re-score against fresh signals — a new site visit, a funding event, a decision-maker changing jobs. If the score jumps past 60, route it to a *different* rep with a clean slate rather than the one who already gave up on it. That single move recovers a meaningful slice of pipeline that would otherwise sit as write-off in your CRM.

The recycling loop requires distinct queue definitions — separate inbound, outbound, and recycled leads — so each can carry its own logic. Use a staleness rule that re-routes anything untouched for fourteen days, and set the cooldown to prevent the same lead from bouncing between reps. For a full walkthrough, see How do I recycle cold and no-response leads back into the routing pool?.

Process Loop: Lead Reassignment and Recycling

What Are Common Pitfalls and How Do I Avoid Them?

• Pitfall 1: Rules so specific nothing matches them. Stack twenty conditions and a lead that satisfies nineteen still falls to the default queue. Fix: keep a catch-all at the bottom and actively watch the default queue — a rising default count is your early warning that the specific rules are too tight.
• Pitfall 2: Time-zone blindness. A 9 PM form fill routed to a same-zone rep can trigger a 10 PM outreach that reads as spam. Fix: use Outreach's Time Zone Routing (Pro and Enterprise) to hold assignment until business hours so first-touch always lands in a human moment. See How do I handle lead routing across multiple time zones in Outreach? for implementation details.
• Pitfall 3: Score changes that arrive too late. If the CRM syncs hourly, a lead whose score just spiked will spend up to an hour in the wrong queue. Fix: trigger an immediate sync on score change via Salesforce Platform Events or HubSpot Webhooks so routing reacts to intent, not to a clock.
• Pitfall 4: Reps on vacation without status updates. Outreach won't infer this on its own — it has no calendar awareness. Fix: set the rep's status to "Out of Office" manually in Outreach settings; while active, any lead that would have gone to them cascades to the next available rep in the same group.

Related questions

How do I route leads based on lead source in Outreach?

Build a custom rule keyed on Lead Source equals [value]. A "Demo Request" form can route straight to an SDR for fast follow-up, while a "Contact Us" form — often a later-stage or existing-buyer signal — routes to an AE. The prerequisite is mapping the Lead Source field from your CRM into Outreach under Settings > CRM Mapping; if that field isn't syncing, the condition silently never matches and every lead lands in your fallback.

What happens if a rep is on vacation or out of office?

Set the rep's status to "Out of Office" manually in Outreach settings. While that status is active, any lead that would have gone to them cascades to the next available rep in the same group per your method (round-robin or custom). Skip this step and leads pile up in an empty queue for the length of the vacation.

How do I prevent leads from being reassigned too quickly?

Use the cooldown period under Settings > Lead Assignment. It defaults to 0 days, which is why untuned instances suffer lead-hopping; set it to 7–30 days so a lead stays put even if the original rep is briefly slow. This removes the incentive for a rep to sit on a lead expecting the system to hand it off, and it keeps buyers from getting cold outreach from three different people in a week.

Does Outreach support AI-driven routing based on conversation intelligence?

Indirectly, through your CRM. Outreach doesn't read Gong or Clari scores natively, so the architecture is to have those tools write a custom field like Intent_Score__c back to the CRM, map that field into Outreach, and reference it in your rules. This is the canonical 2027 pattern — CRM as the single source of truth, AI tools as the score writers, Outreach as the router acting on their output.

Can I route leads to multiple reps at once for the same account?

Yes, and for committee deals you should. Create a group named for the account (for example "Acme Corp Team"), add the SDR, AE, and CS rep, and set the rule to "Route to All Members" rather than "Route to One Member." All three receive the lead simultaneously, which keeps the account team in sync instead of relying on one person to manually forward context to the others.

Can I route leads by company size or revenue?

Yes, as long as the data exists as a CRM field such as Annual_Revenue__c or Employee_Count__c. Map it into Outreach and write a numeric condition — "if Employee_Count > 500 → route to Enterprise User Group." Firmographic routing like this is one of the highest-leverage rules you can add, because it keeps large, complex accounts out of pools tuned for velocity and in front of reps built to work them.

FAQ

How do I set up lead scoring in Salesforce that Outreach can route on? Create a formula field or workflow rule that computes a 0–100 score based on BANT or MEDDPICC criteria — budget identified, authority confirmed, need documented, timeline explicit. Sync that field bidirectionally to Outreach under CRM Mapping, then reference it in your custom routing rules. A score above 70 can route to an AE, while anything below 30 drops to an SDR pool for qualification.

What's the difference between round-robin and weighted round-robin lead assignment? Round-robin distributes leads evenly across all reps in a group, making it ideal for high-volume SMB where every rep is interchangeable. Weighted round-robin skews volume toward proven closers (e.g., 50/30/20 split), which protects ramping reps from being overwhelmed while keeping them in the rotation. Choose weighted when rep performance varies significantly.

How do I handle lead routing across multiple time zones in Outreach? Use Outreach's Time Zone Routing feature (Pro and Enterprise plans) to hold assignment until business hours in the lead's time zone. This prevents a 9 PM form fill from triggering a 10 PM outreach that reads as spam. Configure the time zone field on the lead record or account, then enable the setting under Lead Routing > Time Zone Routing.

How do I recycle cold and no-response leads back into the routing pool? Set a staleness rule that re-routes any lead untouched for 14 days back to the pool. Use AI re-scoring from Clari or Gong to check for fresh signals — new site visit, funding event, job change — and if the score exceeds 50, assign it to a different rep with a clean slate. This recovers pipeline that would otherwise sit as write-off in your CRM.

How do I route leads to an entire buying committee instead of one rep? Create a per-account team group (e.g., "Acme Corp Team") holding the SDR, AE, and CS rep, and set the rule to "Route to All Members." All three receive the lead simultaneously, keeping the account team in sync. Later, use Gong's conversation scoring to decide who owns the next step based on which rep the buyer actually engaged.

How do I test lead routing rules before going live? Use Outreach's Test Lead feature to fabricate a record with exact field values and confirm it lands in the intended group — do this for every rule, including the fallback. Then run a parallel test for a week or two: route live under the new rules while copying leads to a shadow queue, and compare assignment accuracy before you fully cut over.

How do I monitor lead routing performance in Outreach? Watch routing lag as your health metric — leads should surface in a rep's queue inside one to five minutes. When lag creeps past fifteen, the culprit is almost always CRM sync cadence rather than the rules themselves. Also monitor the default queue count; a rising default count is your early warning that specific rules are too tight.

Sources

• Gartner: Buying Committee Size and Sales Cycle Trends
• Forrester: The Future of Lead Routing in B2B
• Outreach: Lead Routing Documentation
• Clari: AI-Powered Lead Scoring and Routing
• Gong: Conversation Intelligence for Lead Prioritization
• Salesforce: Lead Assignment Rules Best Practices
• HubSpot: Lead Routing with Workflows
• SaaStr: How to Scale Lead Routing Without Breaking Your Sales Team
• MEDDPICC: Framework for Lead Qualification and Routing

Related on PULSE

• [How Do I Set Up Lead Routing in Clari?](/knowledge/tl9348)
• [How do you handle lead routing in a multi-product RevOps setup in 2027?](/knowledge/tl21774)
• [How to set up automated lead scoring rules in a CRM without a dedicated RevOps team](/knowledge/tl9379)
• [Should I Hire a Fractional CRO If I Need to Fix Broken Lead Routing and Handoffs in 2027?](/knowledge/tl0396)