Outcome. A trial signup lands with an AE if the plan tier justifies a sales conversation, or with customer success onboarding if it does not, instead of every signup hitting the same generic queue.
Workflow map
Enrollment, branches and actions at a glance
lead-routing-017
flowchart TD
A[Trial started date set] --> B{Existing customer?}
B -->|Yes| C[Notify current owner + create task]
B -->|No| D{Plan tier?}
D -->|professional / enterprise| E[Rotate to AE pool]
D -->|free / starter| F[Rotate to CS onboarding pool]
E --> G[Set routed date, notify, qualify-call task]
F --> H[Set routed date, notify, onboarding-email task]
When to use it, when not to
- UseUse it when the product has a self-serve trial and the trial tier (free, starter, professional, enterprise) already predicts whether the account needs a sales-assisted close or a self-serve onboarding nudge.
- UseUse it when the app can write the plan tier onto the HubSpot contact record at signup time, either through a form or an integration.
- SkipDo not use it if every trial tier goes through the same sales-assisted process; a single rotation pool (lead-routing-002) is simpler.
- SkipDo not use it for an existing customer starting a second trial on a different product; route that 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.12 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.
