Loading
Because each signal is small on its own. Three reopened tickets, one breach and a quiet quarter look unremarkable individually and obvious together — but nobody assembles them until the renewal is lost.
Account health summarises the support relationship for one customer: volume, reopen rate, breaches, satisfaction and the trend across them.
It aggregates the customer's own ticket history against their own baseline rather than a global average, so a normally quiet account getting busy is as visible as a busy one getting busier.
An account's reopen rate doubles and CSAT drops over two months while ticket volume stays flat. That pattern surfaces before the renewal conversation in Flow rather than during it.
It will not predict churn. It reports what the support relationship looks like; a customer leaving for a reason nobody raised a ticket about is invisible to it.
Tickets, SLA outcomes, CSAT and reopens from Desk; renewal date and value from Flow; overdue invoices from Books.
It shows the component signals. A single score hides which one moved.
Yes, on the account before a renewal conversation.
Yes, on a signal crossing a threshold you choose.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.