The Workflow Library

Library / Customer onboarding / customer-onboarding-017

Branch onboarding path by product or plan tier purchased

Customer onboardingDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A closed-won deal is routed to the onboarding checklist and cadence that matches the plan tier the customer actually bought, instead of one generic process for every plan.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-017
flowchart TD
    A[Deal stage = Closed Won, Plan Tier known] --> B{Plan Tier}
    B -->|Starter| C[Self-serve checklist task + resource list]
    B -->|Growth| D[Book kickoff call task]
    B -->|Enterprise| E[Assign dedicated specialist task]
    B -->|Else/unmapped| F[Alert CS manager: unrecognized plan]
    C --> G[Set Onboarding Path = Plan Tier]
    D --> G
    E --> G
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when you sell two or more distinct plan tiers (for example Starter, Growth, Enterprise) and each one needs a different onboarding checklist, kickoff format, or resource set.
  • UseUse it when the plan tier is captured as a deal property before or at close, either manually or from the primary line item.
  • SkipDo not use it if deal amount alone predicts onboarding complexity better than the plan label, use customer-onboarding-016 instead.
  • SkipDo not use it if you only sell one plan, there is nothing to branch on.
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.3 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.5 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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 customer onboarding 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.