Structure your raw NPS responses into meaningful themes and actionable insights so you know exactly what to fix, keep, or double down on.
The template
Response Segment
Categorize each response by NPS score group — Promoter (9–10), Passive (7–8), or Detractor (0–6) — so you can analyze each audience separately.
Example: Detractor — Score: 4 — Submitted: March 2024 — Plan: Pro — Tenure: 3 months
Verbatim Feedback
Paste the exact open-ended comment the respondent left so you preserve their original language for quoting and pattern-matching.
Example: "The reports look great but exporting to CSV always breaks formatting. I've had to manually fix it every single time — it's costing us hours."
Theme Tag
Assign one primary theme label to each response so you can group and count recurring topics across your full dataset.
Example: Theme: Export & Reporting Bug — Sub-theme: CSV formatting — Frequency so far: 14 responses — Segment: Detractors
Recommended Action
Write one concrete next step tied to this theme — a product fix, a follow-up call, a support article, or a team to notify.
Example: File bug ticket with engineering for CSV export formatter; follow up personally with all 14 detractors who mentioned it; add workaround to help docs by Friday.
How to use it
Export and clean your responses Pull your NPS survey data into a spreadsheet and remove incomplete rows, duplicate submissions, and any responses with no open-ended comment.
Segment by score group Sort responses into three tabs or color-coded groups — Promoters, Passives, and Detractors — so you're comparing like with like when you spot patterns.
Tag each response with a theme Read every comment and assign one short theme label (e.g. "Onboarding Confusion" or "Price Concern") then tally how many responses share each tag.
Prioritize themes and write actions Rank your themes by frequency and segment impact, then write one specific action per theme and assign it to an owner with a deadline.
What it looks like filled in
Onboarding Complexity (Detractors — 23 responses)
"I never really understood how to set up my first project. The setup wizard disappeared and I was just left guessing. Gave up after 20 minutes."
→ Redesign the onboarding checklist to persist beyond day one and trigger a live chat prompt after 10 minutes of inactivity in setup.
"The dashboard takes forever to load when we have more than 500 records. We're paying for a tool that slows us down at scale."
→ Escalate dashboard query performance to engineering as P1; send proactive update email to affected Pro and Enterprise accounts this week.
Integrations Depth (Promoters — 31 responses)
"The Slack and HubSpot integrations are exactly what we needed. Everything just syncs without us thinking about it. That's why we renewed."
→ Use integration quality as a core retention message in renewal campaigns and prioritize Salesforce integration to expand this theme's reach.
Why teams skip the template
Tagging hundreds of responses by hand is exhausting and inconsistent When two people tag the same dataset they often use different labels, which makes it impossible to count themes accurately or trust your final numbers.
Spreadsheets don't scale past a few hundred responses Once your NPS volume grows, manually reading and categorizing every comment takes days — and by the time you finish, the insights are already stale.
You miss subtle patterns buried in long comments Manual review tends to surface the loudest complaints and ignore nuanced signals like churn intent hidden mid-paragraph or praise tied to a specific feature.
Analyze your NPS survey responses automatically — no template needed
