Outcome. A lead from a company on the strategic account list goes straight to the dedicated senior AE assigned to that account, never into the standard round-robin.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-011
flowchart TD
A[Contact created / strategic flag set] --> B{Strategic account match?}
B -->|Yes| C[Assign to mapped strategic AE]
C --> D[Set routed date, notify AE, create alignment call task]
D --> E[Delay 4 business hours]
E --> F{AE engaged yet?}
F -->|No| G[Notify sales director]
F -->|Yes| H[End, no action]
B -->|No| I[End, no action - standard routing handles it]
When to use it, when not to
- UseUse it when a defined set of named accounts (existing target accounts, key logos, or accounts a strategic AE is already working) should never route through generic assignment logic.
- UseUse it as the suppression layer referenced by lead-routing-001 and lead-routing-006, so those workflows correctly skip these leads.
- SkipDo not use it for every enterprise-sized company, only for accounts explicitly designated strategic. Use lead-routing-007 for size-based segmentation without a named-account list.
- SkipDo not use it if the strategic AE roster changes often without updating the account-to-AE mapping; a stale mapping routes a hot lead to someone who no longer owns that account.
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.10 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.
