The Workflow Library

Library / Lead routing / lead-routing-010

Assign leads by industry vertical

Lead routingContactSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A lead lands with the rep who specializes in their industry, so the first call already speaks the right language instead of a generalist relaying it later.

Workflow map Enrollment, branches and actions at a glance lead-routing-010
flowchart TD
    A[Contact created / Industry set on company] --> B{Industry grouping?}
    B -->|Healthcare| C[Rotate to Healthcare pool]
    B -->|Financial services| D[Rotate to Financial services pool]
    B -->|Retail| E[Rotate to Retail pool]
    B -->|unmapped / blank| F[Rotate to Generalist pool + notify sales ops]
    C --> G[Set routed date, notify owner, create call task]
    D --> G
    E --> G
    F --> G
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when reps are organized by vertical (for example healthcare, financial services, retail) rather than by territory or size, and each vertical has its own rep pool.
  • UseUse it alongside lead-routing-006 or lead-routing-007 when the org splits by both geography/size AND vertical; chain the branches, vertical first or territory first depending on which dimension has fewer, cleaner pools.
  • SkipDo not use it if industry data on the associated company is largely unpopulated or unreliable. Add an enrichment step, or fall back to a self-reported form field, see Variants.
  • SkipDo not use it for named/strategic accounts with a fixed owner regardless of vertical; exclude those first, see lead-routing-011.
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.15 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.