ooligo
EN
English en Español es Português (Brasil) pt-BR
Subscribe
Tools Comparisons Workflows Learn
Verticals
RevOps Legal Ops Recruiting & TA
Language
English Español Português (Brasil)
GitHub Subscribe
ENTRY TYPE · how-to

Lead routing

Last updated 2026-05-02 RevOps

Lead routing is the automated process of assigning incoming leads to the right rep, queue, or system based on rules that match the lead’s attributes to the rep’s territory, capacity, or specialization. Done right, it shaves hours off lead response time and prevents the worst RevOps failure mode: a hot inbound lead sitting in nobody’s queue.

The five rule types

Every lead routing system uses some combination of these:

  1. Geographic. US-East to AE A, US-West to AE B, EMEA to AE C. Simple, common, often the first rule.
  2. Account-based. Existing customers route to the named account owner; net-new prospects route by territory.
  3. Vertical / segment. Healthcare leads to the healthcare AE; finance leads to the finance AE. Requires accurate firmographic enrichment.
  4. Round-robin within territory. Within US-West, rotate fairly across AEs B, D, E. Capacity-aware variants skip AEs at threshold.
  5. Lead score / fit. High-fit leads route directly to AEs; low-fit leads route to nurture or SDR pre-qualification.

Most B2B SaaS teams stack rules: geographic + segment + score, with round-robin as the tiebreaker.

How to set it up (HubSpot or Salesforce)

  1. Define the rep coverage map. Spreadsheet of who covers what. Get it signed off before you encode it in software.
  2. Wire enrichment. Inbound leads must be enriched (industry, employee count, country) before routing. Use Clay, ZoomInfo, or HubSpot’s own enrichment.
  3. Build the rules in workflow form. HubSpot Workflows or Salesforce Flow handle this natively. For complex rules, n8n or a third-party (Distribution Engine, LeanData, RingLead) is more flexible.
  4. Add a fallback queue. Leads that don’t match any rule route here. Audit it weekly.
  5. Set SLAs. Inbound demo requests should route in under 60 seconds. Anything longer than 5 minutes loses velocity.

Common pitfalls

  • Stale rep coverage maps. AEs leave, territories shift, the rules don’t update. Audit quarterly.
  • Round-robin without capacity awareness. AE on PTO still gets leads. Build capacity flags.
  • No fallback path. A lead that doesn’t match any rule gets lost. The fallback queue is non-negotiable.
  • Routing to a rep instead of a queue. When AE moves on, all their open leads need re-routing manually. Route to a queue with the AE as the default owner.