- Industry
- IT Company
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Investigator
- Approver
- Account Manager
- Code
- CUS-13
It scores each client account's health from SaaS usage and seat utilisation, SLA attainment and ticket volume, QBR and survey sentiment, and billing status using the weighted health model, and explains which signals moved the score and the likeliest cause. It writes the score, band and drivers to the CRM and alerts the account manager on a sharp drop. **The problem it solves:** Why each account's health moved: which usage, service, sentiment and billing signals changed, and whether the cause lies with our delivery or the client's situation.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: each account's ARR, previous score, contacts and renewal date, with usage and SLA figures synced from the product and service management system..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Account Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CRM: it updates each account's health score, band and drivers and alerts the account manager on a sharp drop. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The account health model: signal weights, band thresholds, what each signal means for SaaS and managed-services accounts, and known data gaps.
Reads from
the CRM: each account's ARR, previous score, contacts and renewal date, with usage and SLA figures synced from the product and service management system.
Acts in
the CRM: it updates each account's health score, band and drivers and alerts the account manager on a sharp drop.
Hands back
A list with one entry per account, each with account_id, score, band (green, amber, red), change, drivers (a ranked list with signal, effect and evidence), likely_cause and confidence.
Asks a person when
An account at or above 250000 USD ARR turns red, or a drop of 15 points is blamed on our service.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Usage weight (%) | 35 | Weight of usage and seat utilisation. |
| Service weight (%) | 25 | Weight of SLA attainment and P1/P2 tickets. |
| Sentiment weight (%) | 25 | Weight of survey and QBR sentiment. |
| Billing weight (%) | 15 | Weight of payment status. |
| Red below | 50 | Scores below this are red. |
| Amber below | 75 | Scores below this and at or above red are amber. |
| Alert on a drop of (points) | 15 | A drop of this many points since the last score alerts the account manager. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Weight usage 35, service 25, sentiment 25 and billing 15 percent.
- Band red below 50, amber below 75, otherwise green.
- Explain the score by the signals that moved most, and separate a cause on our side (SLA misses, outages) from one on the client's (reorganisation, champion left).
- Alert the Account Manager when a score drops 15 points or more.
- Score a missing signal as unknown, not zero, and say so.
See the Account Health Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.