Skip to content

Customer health score decline triggers churn risk flag

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Service Hub Professional.

Company4 stepsUpdated for HubSpot seat pricing
OutcomeThe 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 maprenewal-expansion-015
Health Score Decline Flag set to true leads to Set Churn Risk Flag = true. Set Churn Risk Flag = true leads to Create task for owner. Create task for owner leads to Notify owner and CSM. Notify owner and CSM leads to Reset Health Score Decline Flag to false. Health Score Decline Flag set to true Set Churn Risk Flag = true Create task for owner Notify owner and CSM Reset Health Score Decline Flag to false
Health Score Decline Flag set to true leads to Set Churn Risk Flag = true. Set Churn Risk Flag = true leads to Create task for owner. Create task for owner leads to Notify owner and CSM. Notify owner and CSM leads to Reset Health Score Decline Flag to false. Health Score Decline Flag set to true Set Churn Risk Flag = true Create task for owner Notify owner and CSM Reset Health Score Decline Flag to false

When to use it, when not to

Use it

  • Use 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.
  • Use 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.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Renewal and expansion spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library