Setting tracks, holds and Recompute tracks
Last updated on
Where each track starts
A new account starts at Expansion None, Support Stable, and Risk & Health from its starting score. Lifecycle and Renewal are set by the first recompute, once there's data for them.

Setting a track yourself
- On the account page — the change applies at once, but the next recompute (within about 30 minutes) moves it again if the data disagrees.
- CSV import, Larry, or a mapped HubSpot field — the state is held for 14 days: automation leaves that track alone until then.
- Risk & Health is never held. It follows the health score and open signals and is refreshed with every score change. To move it for real, pin the health score or confirm a pending change.
Changes waiting for a person
Some moves always wait for a person: Risk & Health entering Escalation or leaving Recovery, and Expansion moving to Qualified. They appear on the account and in Today's Focus under Track changes waiting for confirmation, with Confirm and Dismiss.
An open Early credit exhaustion or Credits over allowance signal moves Expansion from None to Identified on its own.
Recompute tracks
In the account's health pop-up (click the Health ring), Recompute tracks recomputes all five tracks for that one account now, with the same rules as the 30-minute job, judged on the current (or pinned) score — it never changes the score itself. Held tracks are listed with their hold date and skipped, unless you choose Release hold & recompute. Lost accounts are read-only.
The journey stage is set for you
The journey stage shown on the account and in the Accounts list is the Lifecycle track's state — Onboarding, Adoption or Steady State — plus Churned, which overrides…
Onboarding milestones
While an account is onboarding, Clynto tracks its milestones in four steps: Kickoff → Integration setup → First value → Go live.