Organize your NPS detractor comments into themes and root causes so you can prioritize fixes that actually reduce churn.
The template
Detractor Comment
Paste the raw verbatim feedback exactly as the respondent wrote it, including their NPS score.
Example: Score: 4 — "The reporting dashboard is confusing and I can never find the export button. Support took 3 days to respond when I asked for help."
Theme / Category
Assign one primary theme that best describes the core problem the respondent is expressing.
Example: UX / Navigation — the user cannot locate key features without assistance, indicating a discoverability problem in the UI.
Root Cause Hypothesis
Write your best explanation of why this problem is happening based on what the respondent described.
Example: The export function is buried three levels deep in a sub-menu with no search or shortcut, and onboarding does not surface it during setup.
Recommended Action
Describe one specific, owner-assigned action your team should take to address this root cause.
Example: Product team to move export button to the top-level toolbar by Q3; CS team to add export walkthrough to onboarding email sequence by end of month.
How to use it
Export your detractor responses Pull all responses with an NPS score of 0–6 from your survey tool and paste the verbatim comments into column one of the template.
Group comments into themes Read through every comment and assign each one a category such as Pricing, Onboarding, Performance, or Support — aim for 5–8 themes maximum to keep patterns clear.
Write a root cause hypothesis for each theme For the most common themes, write one sentence explaining the underlying reason customers are frustrated, not just restating what they said.
Assign a specific action to each theme For every root cause, write one concrete next step with a named owner and a target date so the analysis leads directly to change.
What it looks like filled in
Onboarding Complexity
"I signed up two weeks ago and still don't know how to connect my data sources. The setup docs assume you already know the product."
→ Rewrite the getting-started guide with a step-by-step data connection wizard and assign a CSM to all new accounts in the first 14 days.
Pricing Transparency
"I was charged for an extra seat I didn't know I'd added. The billing page doesn't show you what triggers an upgrade until after it happens."
→ Add an in-app warning modal that shows the cost impact before any action that would trigger a seat or tier upgrade.
Slow Support Response
"Every time I submit a ticket I wait at least two days. For a paid plan that feels unacceptable — I end up just stopping using the feature instead."
→ Set an SLA of under 8 business hours for paid plan tickets and add a live chat option during business hours to reduce ticket volume.
Why teams skip the template
Manual tagging takes hours at scale Reading and categorizing hundreds of detractor comments by hand is slow, inconsistent across team members, and rarely gets done before the next NPS cycle starts.
Human themes miss subtle patterns When you manually group feedback, you tend to create the categories you already expect, which means emerging issues or niche but high-churn complaints stay buried in the data.
Analysis sits in a spreadsheet nobody revisits Without automated surfacing, the insights from your last NPS round are usually forgotten by the time the next round of detractor comments arrives and needs the same work done again.
Analyze your NPS detractor comments automatically — no template needed
