Five pages, one for each step: finding the risk, scoring the account, acting on it, measuring what the outreach changed, and reporting retention to the board. If you have 5 minutes, read renewal risk signals and the customer health score; they explain where the evidence comes from and how the number is built. The other three show what your team does with it.
Start here: renewal risk signals, then the customer health score.
How the pieces fit
- Pull risk signals. Horizon reads calls, support tickets, Jira bugs, email and product usage, and raises a signal whenever an account changes for the worse (or the better).
- Score every account. The signals roll up into a customer health score from 0 to 100 across product, adoption, relationship and commercial.
- Act. Each risk comes with a playbook for the account owner. When it needs an email, Horizon drafts one from the evidence and your CSM sends it from their own Gmail.
- Measure. Saved renewals are compared with a holdout group that stayed on your normal process, and lost revenue is split by reason for the board.
Questions
Where does Horizon get its evidence?
From Salesforce, Gong and Google Meet calls, Zendesk tickets, ServiceNow incidents, Jira bugs, Gmail and product usage. Every risk signal cites the call, ticket, email or usage report it came from, with the date and a link to open it in the source system.
Does AI decide the health score?
No. AI finds the evidence, and the score is plain rules you can read: four areas, each set by its worst open problem, with the total capped at 25 points above the weakest area.
Does Horizon email our customers on its own?
No. Horizon drafts the email from the account's evidence, and a CSM reviews it and sends it from their own Gmail. Nothing sends on its own.
How long before we see it on our own accounts?
A 30-minute call starts on a demo book or your own top 25 accounts. The free 30-day pilot then runs on your real accounts, set up with you on a call. See pricing.
Updated November 4, 2026