Outcome. A lead referred by a partner reaches the manager who owns that partner relationship directly, instead of getting mixed into the general round-robin where nobody knows the referral context.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-022
flowchart TD
A[Contact created / Partner name set] --> B{Lead source detail = partner-referral?}
B -->|No| C[Exit, handled by standard routing]
B -->|Yes| D{Partner name?}
D -->|mapped partner| E[Set owner = mapped partner manager]
D -->|blank / unmapped| F[Notify partner program owner + add to Needs manual routing]
E --> G[Set routed date, notify owner, create task]
When to use it, when not to
- UseUse it when the company runs a partner or referral program and each partner has a named internal manager responsible for that relationship.
- UseUse it when the referral source can be captured reliably, either through a partner-specific referral link parameter or a hidden form field.
- SkipDo not use it if there is only one partner manager for all partners; a single fixed-owner assignment (no rotation needed) is simpler, see the Variants section.
- SkipDo not use it for a named strategic account that happens to also be partner-referred; decide precedence with lead-routing-011 in a single document so the two workflows never fight over the same lead.
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.4 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.17 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.
