Overview

Client health gives every account a score from 0 to 100 and a status: Healthy, Watch, or At risk. The score blends three axes - Relationship (communication rhythm and reciprocity), Delivery (projects, overdue work, and tickets), and Commercial (margin, collections, and scope creep). If the number disagrees with what you know, an owner can set a human override with a required reason, and automated alerts pause while an override is active.

The status appears on the client's Overview pulse tiles, and a full Health detail page on the record breaks down each axis with trends.

Who can do this

  • Required access: an access level that includes Entities - Standard Access or Entities - Full Access.
  • Default access levels that include it: Team Member, Accountant, and System Administrator.
  • Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
  • Personal accounts: Not available. This is a work feature, so it is hidden in personal (family) spaces.

Owners and admins review and change access levels in Settings → Administration → Members → Access levels.

Work the Health triage view

  1. Open Clients > Health triage.
  2. Read the summary: total value at risk across active clients, how many were evaluated, alert candidates, and the critical-plus-high count.
  3. Work the ranked list. Each client shows a priority (Critical, High, Medium, or Low), its lifecycle stage, the specific risk drivers, its relationship score, and the value at risk - annual revenue weighted by relationship risk.
  4. Click a client to open its Health detail page and dig into the drivers.
  5. Use Sync Alerts to create or refresh alerts for the riskiest clients. Alerts resolve automatically once a client leaves triage risk.

Alerts and lifecycle sync

When a client's health band changes, the client's team is notified: dropping to At risk raises a high-priority alert, sliding from Healthy to Watch flags the decline, and recoveries are announced too. First-time computations do not alert, so you are never paged for a brand-new score.

Health also syncs with the lifecycle: when an active customer drops to At risk, Scrambl moves its lifecycle stage to At Risk automatically, and moves it back when health recovers - but only if the automation made the original move. A stage set by a person is never reverted, and a client is never churned automatically.

Best practice: Triage by value at risk, not by score alone. A mid-score account with large annual revenue usually deserves attention before a low-score account with little at stake.


Troubleshooting

IssueWhat to check
A new client shows a middling score.Relationship scoring needs a few weeks of interaction history before it is confident.
No alerts are firing.Run Sync Alerts from Health triage, and check whether a human override is active on the record.

Next steps

  • Review lifecycle stages so at-risk syncing lands on the right accounts.
  • Read how deal health scores flag at-risk deals for the sales-side view of risk.