The Workflow Library

Library / Lead routing / lead-routing-032

Round-robin across multiple pipelines (SMB pipeline vs Enterprise pipeline)

Lead routingDealSales Hub ProfessionalAdvanced~50 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. A deal lands in the right pipeline based on its segment, then rotates only among the reps who actually work that pipeline, instead of one flat rotation ignoring pipeline structure.

Workflow map Enrollment, branches and actions at a glance lead-routing-032
flowchart TD
    A[Deal created, owner unknown] --> B{Pipeline?}
    B -->|SMB Pipeline| C[Rotate to SMB AE pool]
    B -->|Enterprise Pipeline| D[Rotate to Enterprise AE pool]
    B -->|other pipeline| E[Notify sales ops, add to Needs manual routing]
    C --> F[Set routed date, notify owner, create call task]
    D --> F
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the team runs two or more separate deal pipelines (for example SMB and Enterprise) with different reps, stages, and sales motions.
  • UseUse it when a deal's segment (company size, deal amount, or product) is known at creation and reliably determines which pipeline it belongs to.
  • SkipDo not use it if all deals share a single pipeline; a flat round-robin (lead-routing-009) is simpler.
  • SkipDo not use it if pipeline assignment itself is manual and inconsistent; fix that classification step first, this workflow only routes once the pipeline is already correct.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.5 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.11 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the lead routing pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.