Outcome. At kickoff, customer success, support, and billing all get the same consolidated briefing in one notification, instead of three separate department-specific alerts each missing context the others have.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-050
flowchart TD
A[Deal stage = Closed Won, briefing not yet sent] --> B[Send consolidated notification to CS, support, billing]
B --> C[Create matching note on deal timeline]
C --> D[Set Kickoff Briefing Sent Date]
When to use it, when not to
- UseUse it when a new customer genuinely needs more than one department aware at kickoff, and today each department either finds out separately (see customer-onboarding-001 for CS, customer-onboarding-030 for finance, customer-onboarding-022 for delivery) or does not find out at all.
- UseUse it as the consolidated version of those single-department fiches, not a replacement for them, some teams want both a targeted alert and a shared briefing.
- SkipDo not use it if only one department actually needs to know at this point, use the specific fiche for that department instead (customer-onboarding-001, 022, or 030), a briefing to everyone when only one team needs to act creates noise.
- SkipDo not use it for deals below a certain size if the extra visibility is not worth the notification volume, add an amount filter to the enrollment criteria if that is the case.
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.6 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.3 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.
