Outcome. A company gets a numeric health score during the onboarding window, built from onboarding-specific signals rather than the steady-state usage metrics a mature health score usually relies on, so CS can flag risk before the customer has any product history.
flowchart TD
A[Initial Health Score recalculates] --> B{Score >= 80?}
B -->|Yes| C[Set Health Score Status = Healthy]
B -->|No| D{Score >= 50?}
D -->|Yes| E[Set Health Score Status = At Risk]
D -->|No| F[Set Health Score Status = Critical]
C --> G{Status = Critical?}
E --> G
F --> G
G -->|Yes| H[Alert Onboarding Owner]
G -->|No| I[End]

When to use it, when not to
- UseUse it when you want an early-warning number during onboarding, before there is enough product usage data for a full lifecycle health score.
- UseUse it when the signals feeding the score already exist as properties on the company or its associated tickets and deals (overdue tasks, escalations, CSAT).
- SkipDo not use it as a replacement for a full post-onboarding health score, this fiche is deliberately narrow and should be retired or superseded once the customer graduates from onboarding, see the renewal-expansion category for ongoing health scoring.
- SkipDo not use it if calculated properties are not available on your subscription, use the workflow-only fallback in Known pitfalls instead.
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.





