Home / Guides / Churn, health scores and retention

A voice of the customer report that product teams actually read

By Draft First. Updated October 2026

Customer feedback is everywhere: tickets, survey comments, call notes, renewal conversations, angry emails. Product teams hear a fraction of it, usually the loudest customer from last week. A short monthly voice of the customer report fixes that, as long as it's built on evidence and not anecdotes.

What to collect

• Ticket tags and the text of tickets about product gaps.
• Survey comments, especially from low scores.
• Call notes and QBR feedback.
• Reasons given for churn or downgrades.
• Feature requests, with who asked and what the account is worth.

How to structure it

1. Top themes, ranked by how many accounts raised them, not how loudly.
2. For each theme: count of accounts, revenue affected, two short quotes, and links to the sources.
3. What changed since last month: new themes, rising ones, ones that went quiet after a fix.
4. One ask for the product team.

A sample report section

VOC October | Sources: 412 tickets, 63 survey comments, 18 call notes
1. Report exports time out (14 accounts, about $410K ARR, up from 6)
   "We export by hand every Friday now." (Coastline, ticket #5512)
   "The one thing that would make us renew happily." (Halden, QBR Oct 3)
2. SSO setup confusing for new admins (9 accounts, new this month)
Quiet: mobile login issues (0 mentions since the Sep 12 fix)
Ask: a date for the export fix before Q4 renewals.
Skipped: call notes from 2 CSMs (not shared to the notes folder).

Keep it honest

• Count accounts, not mentions. One customer filing ten tickets is one voice.
• Quote real words with a source. Paraphrase invites argument.
• Include praise too. It tells product what not to break.

Drafting it with AI

Reading 400 tickets is exactly the job an agent does well, as long as it shows its work.

On the first business day of each month, read last month's [tickets,
survey comments, call notes]. Group feedback into themes. For each theme:
number of distinct accounts, total ARR from [CRM], two verbatim quotes with
source links, and the change from last month. Count accounts, not
mentions. Never invent quotes. List sources you couldn't read.

This is the Voice of the Customer Monthly play in The CS Agent Playbook. Survey comments come from your low score follow-ups.

Questions

What is a voice of the customer report?

A regular summary of customer feedback from tickets, surveys and calls, grouped into themes for product and leadership.

How often should we share VOC feedback?

Monthly works for most teams. It's often enough to spot trends without becoming noise.

How do you rank feedback themes?

By the number of distinct accounts and the revenue affected, not by how many times one customer raised it.