Outcome. The moment an account's health score drops enough to matter, the CSM gets a flagged account and a task, instead of the drop only being visible on a dashboard someone might not check that week.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-015
flowchart TD
A[Health Score Decline Flag set to true] --> B[Set Churn Risk Flag = true]
B --> C[Create task for owner]
C --> D[Notify owner and CSM]
D --> E[Reset Health Score Decline Flag to false]
When to use it, when not to
- UseUse it once a customer health score already exists on the company record, whatever computes it: a native health scoring tool, a CS platform synced into HubSpot, or a manually maintained number.
- UseUse it as the reactive alert layer; the score's calculation itself, including what counts as a meaningful decline, is decided outside this workflow by whoever maintains the score.
- SkipDo not use it if health score is not yet reliable or is still being calibrated; an alert workflow on top of a noisy score creates alert fatigue faster than it creates useful signal.
- SkipDo not use this as your only churn detection. Pair it with more specific signals like NPS detractor (renewal-expansion-003) or ticket volume spike (renewal-expansion-013) for a fuller picture.
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.4 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 renewal and expansion 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.
