Outcome. A closed-won deal above your enterprise threshold routes to a dedicated onboarding specialist sub-team instead of the general customer success pool, using hierarchical teams to keep specialist capacity separate from everyday assignments.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-039
flowchart TD
A[Deal stage = Closed Won, Onboarding Owner unknown] --> B{Amount above enterprise threshold?}
B -->|Yes| C[Set Enterprise Onboarding Track = true]
C --> D[Rotate to Enterprise Onboarding Specialists]
B -->|No| E[Rotate to general CS team]
D --> F[Notify assigned owner]
E --> F
When to use it, when not to
- UseUse it when large accounts need a smaller, more experienced specialist group and mixing them into the general CS rotation from customer-onboarding-001 or customer-onboarding-006 dilutes that separation.
- UseUse it when your org chart already reflects this split, a hierarchical team structure with an "Enterprise Onboarding" sub-team under the main CS team.
- SkipDo not use it without Sales Hub Enterprise (or Service Hub Enterprise), hierarchical teams with parent-child relationships are an Enterprise-tier feature, Professional teams are flat with no sub-team structure (https://knowledge.hubspot.com/settings/hubspot-teams).
- SkipDo not use it if deal size is not actually the deciding factor for your specialist assignment, this fiche routes on amount alone, product complexity or industry may matter more in your business, adapt the branch condition.
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.5 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 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.
