The Workflow Library

Library / Lead routing / lead-routing-007

Route inbound demo requests by company size (employee count)

Lead routingContactSales Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. A demo request lands with the rep who actually handles that size of account (SMB, mid-market, or enterprise) instead of a generalist who then has to hand it off.

Workflow map Enrollment, branches and actions at a glance lead-routing-007
flowchart TD
    A[Demo request form submitted] --> B{Company employee count?}
    B -->|under 50| C[Rotate to SMB pool]
    B -->|50 to 499| D[Rotate to mid-market pool]
    B -->|500+| E[Rotate to enterprise pool]
    B -->|unknown| F[Rotate to default pool + notify sales ops]
    C --> G[Set routed date, notify owner]
    D --> G
    E --> G
    F --> G
    G --> H[Delay 2 business hours]
    H --> I{Meeting booked?}
    I -->|Yes| J[End, no action]
    I -->|No| K[Notify owner's manager]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the sales org is segmented by company size rather than territory or product, and reps have different playbooks per segment.
  • UseUse it right after (or instead of) lead-routing-002 for demo-request forms specifically, since a generic new-lead workflow does not know which segment a lead belongs to.
  • SkipDo not use it if the associated company record has no employee count populated for most leads. Add an enrichment step first, or fall back to a self-reported "Company size" form field, see Variants.
  • SkipDo not use it for existing customers requesting an expansion demo; route those to their current owner instead, see lead-routing-019.
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.28 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 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.