<!-- Voice-of-customer report · from Chapter 09 of The Product 360 Handbook -->

# Voice-of-customer report · [Product] · [Period]

**Owner:** [PM]   **Sources:** [surveys, tickets, calls, community, CSM notes, churn interviews]   **Items analyzed:** [n]   **Codebook version:** [v]

## Headline
[Two or three sentences: the themes that matter most and what they cost or could earn]

## Themes
| Theme | Share of items | Trend vs last period | Accounts raising it | ARR of those accounts | GRR of those accounts | Owner |
|---|---|---|---|---|---|---|
| | | | | | | |

## For each top theme
**[Theme name]**
- What customers say (three verbatims with source references):
  1. "[Quote]" ([source, date])
  2.
  3.
- Who raises it: [segments, roles]
- Link to retention or revenue: [evidence]
- Root cause (if known):
- Action and owner:

## New themes proposed this period (pending approval)
| Proposed theme | Example items | Approve / merge / reject |
|---|---|---|
| | | |

## Sentiment scores (context only)
| Measure | This period | Last period | Responses | By role |
|---|---|---|---|---|
| NPS | | | | |
| CSAT | | | | |
| Effort score | | | | |

## Closing the loop
- Individual follow-ups completed: [n of n]
- Root-cause fixes shipped since last report:

## Method and quality
- Human-labeled validation sample: [n] items; agreement: [measure]
- Theme shares, human vs machine: [comparison]
- Known weaknesses: [for example negation, sarcasm, a theme undercounted]
- Personal data removed before analysis: Yes / No; approved tool used: [tool]