Outcome. Partway through onboarding, the primary contact gets an NPS survey, and a low score routes straight to the CS manager instead of waiting for the standard quarterly relationship survey to catch a problem.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-042
flowchart TD
A[Onboarding Start Date on contact known] --> B[Delay 14 business days]
B --> C[Send NPS survey]
C --> D{Score received and <= 6?}
D -->|Yes| E[Escalate to CS manager]
E --> F[Set NPS Escalated, create follow-up task]
D -->|No| G[End, no escalation]
When to use it, when not to
- UseUse it when onboarding typically runs 3 to 6 weeks and you want an early read on sentiment before go-live, separate from the post-kickoff CSAT in customer-onboarding-009 and the post-completion survey in customer-onboarding-020.
- UseUse it alongside, not instead of, customer-onboarding-029 (low CSAT escalation on a ticket), the two catch feedback at different moments and on different objects.
- SkipDo not use it if onboarding runs less than 2 weeks end to end, a mid-point survey has no real gap from the final one and adds survey fatigue for no benefit.
- SkipDo not send this to a contact who has already left the company or changed role mid-onboarding, exclude contacts flagged inactive if your portal tracks that.
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.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 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.
