Outcome. New leads are routed straight to the correct territory pool based on the country or region on the record, with no separate territory field to keep in sync.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-006
flowchart TD
A[Contact created / Country set] --> B{Country/Region?}
B -->|NA countries| C[Rotate to NA pool]
B -->|EMEA countries| D[Rotate to EMEA pool]
B -->|APAC countries| E[Rotate to APAC pool]
B -->|blank / unmapped| F[Notify sales ops + add to Needs manual routing list]
C --> G[Set routed date, notify owner, create call task]
D --> G
E --> G
When to use it, when not to
- UseUse it when territory lines follow country or region and the record already has a reliable country value (from a form, an import, or an enrichment tool).
- UseUse it instead of lead-routing-001 when maintaining a separate
Territorydropdown feels like extra data-entry for a mapping that country already gives you. - SkipDo not use it if territory splits do not follow national borders (postal code slices within a single country, or account-based assignment). See lead-routing-033 for a postal code lookup and lead-routing-011 for named-account routing.
- SkipDo not use it if the country property is unreliable (free-text field, no validation). Clean it up first, see data-quality-002.
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.
