Outcome. A marketing-generated lead and a rep-sourced prospect land in the queue built for how they actually arrived, instead of one flat pool that treats a form fill and a cold outbound reply identically.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-044
flowchart TD
A[Contact created] --> B{Original Source = sales activity?}
B -->|Yes| C{Owner already set?}
C -->|Yes| D[End, stays with creator]
C -->|No| E[Set owner to contact creator]
B -->|No, marketing-sourced| F[Rotate to SDR pool]
F --> G[Set routed date, notify owner, create qualification task]
When to use it, when not to
- UseUse it when marketing-sourced leads need a qualification step (SDR pool) while sales-sourced leads (referrals, a rep's own prospecting, a partner introduction logged manually) should go straight back to the rep who sourced them or into a dedicated pool.
- UseUse it when the standard
Original Sourceproperty reliably distinguishes the two paths for your business (organic search, paid, email, direct traffic as marketing-sourced; sales activity or manually created as sales-sourced). - SkipDo not use it if the team does not actually treat these two paths differently downstream; if both end up in the same follow-up process, the split adds complexity without changing outcomes.
- SkipDo not use it as a substitute for tracking a rep's own sourced pipeline for commission or credit purposes; that is a reporting need, this fiche only handles first-touch routing.
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.7 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.
