Sources
- Asked for: surveys such as NPS, CSAT and CES, interviews, advisory boards.
- Unprompted: calls, support tickets, email, community posts and reviews.
- Observed: what customers do in the product, which tests what they say.
Worked example
In a quarter, a team tags 160 pieces of feedback into three themes and adds the ARR of the accounts behind each. (Example numbers.)
| Theme | Mentions | Share of mentions | Accounts | ARR of those accounts |
|---|---|---|---|---|
| Mobile app | 72 | 45% | 30 | $0.6M |
| Reporting exports | 48 | 30% | 12 | $2.1M |
| Single sign-on | 40 | 25% | 25 | $0.9M |
By count, the mobile app leads. By revenue, reporting exports matter most: 12 accounts with $2,100,000 ARR between them. Both views belong in the summary you give the product team.
How CS leaders use it
Bring a short VoC summary to product each quarter, weighted by ARR and by renewal date, with a few direct quotes for each theme. Then close the loop: tell the customers who raised a theme what changed, which also gives the account owner a useful reason to get in touch before a renewal. Horizon reads calls, tickets and email for risk, and a signal from a call or ticket quotes the customer, with a link to the source; see renewal risk signals.
Common mistakes
- Counting mentions without weighting by revenue or renewal date.
- Relying on surveys alone. Quiet customers often don't answer them, and they're the ones at risk of silent churn.
- Collecting feedback and never telling customers what happened to it.
More on this topic: customer health, definitions, guides and tools.
Updated November 3, 2026