Structure your NPS comments into actionable themes so you can identify what's driving promoters, passives, and detractors — and actually do something about it.
Template components
Response Segment
Record the NPS score group this comment belongs to — Promoter (9–10), Passive (7–8), or Detractor (0–6).
Example: Detractor — Score: 4
Verbatim Comment
Paste the exact customer comment here without editing so you preserve the original language and sentiment.
Example: "The onboarding took forever and I still don't know how to set up integrations — support wasn't very helpful either."
Theme / Category
Assign one primary theme that best captures the core issue or praise expressed in the comment.
Example: Onboarding Experience
Recommended Action
Write one specific, concrete next step your team should take based on what this comment reveals.
Example: Audit the integration setup flow and add a guided checklist to the onboarding sequence by end of quarter.
Full Copyable Template
<div class="tmpl-full-doc">
<div class="tmpl-full-header">
<div class="tmpl-full-title">NPS Analysis Template (free)</div>
<div class="tmpl-full-meta">Growth & Research Team · 2026-05-04 · In-app NPS survey (184 comments from 412 responses)</div>
</div>
<div class="tmpl-full-section">
<div class="tmpl-full-section-title">1. Analysis Setup</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Product / workspace analyzed</div>
<div class="tmpl-full-field-value">Usercall Team Workspace — Q2 analysis focused on call review, AI summaries, and CRM sync experience</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Analysis goal</div>
<div class="tmpl-full-field-value">Understand what is driving promoter and detractor sentiment in NPS comments, especially around adoption blockers, retention risk, and expansion opportunities.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Survey question wording</div>
<div class="tmpl-full-field-value">“How likely are you to recommend Usercall to a colleague?” followed by “What’s the main reason for your score?”</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Date range</div>
<div class="tmpl-full-field-value">2026-04-01 to 2026-04-30</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Segment in scope</div>
<div class="tmpl-full-field-value">Admin and manager respondents from B2B SaaS accounts with 10+ seats; exclude churned accounts and duplicate submissions.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Data source and volume</div>
<div class="tmpl-full-field-value">412 total NPS responses, 184 open-text comments coded, across 73 customer accounts</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Scoring split</div>
<div class="tmpl-full-field-value">Promoters: 96 · Passives: 171 · Detractors: 145</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Primary business decisions this analysis will inform</div>
<div class="tmpl-full-field-value">Q3 roadmap prioritization, onboarding improvements for new admins, and messaging for expansion in mid-market accounts.</div>
</div>
<div class="tmpl-full-tip">💡 Tip: Before coding, decide whether each comment can receive multiple themes. For NPS comments, multi-code is usually best because a single response often includes both a driver of satisfaction and a barrier to recommendation.</div>
</div>
<hr class="tmpl-full-divider">
<div class="tmpl-full-section">
<div class="tmpl-full-section-title">2. Coding Guide</div>
<div class="tmpl-full-q">
<div class="tmpl-full-q-text"><strong>Fast time-to-value / easy setup</strong> — Comments that mention getting useful insights quickly, low implementation effort, or smooth onboarding. Example: "We had our first customer calls tagged and summarized the same day we connected Zoom, which made the rollout an easy win."</div>
</div>
<div class="tmpl-full-q">
<div class="tmpl-full-q-text"><strong>AI summary quality and accuracy</strong> — Comments about whether summaries, action items, and sentiment labels feel trustworthy, complete, or too generic. Example: "The recap is usually solid, but sometimes the action items sound polished while missing the actual objection the customer raised."</div>
</div>
<div class="tmpl-full-q">
<div class="tmpl-full-q-text"><strong>Searchability and insight discovery</strong> — Mentions of finding calls, topics, objections, trends, or specific moments across conversations. Example: "Being able to search every mention of pricing pressure across 80 calls is the reason I recommend it."</div>
</div>
<div class="tmpl-full-q">
<div class="tmpl-full-q-text"><strong>Workflow integration friction</strong> — Feedback about CRM sync, Slack sharing, recording imports, permissions, or anything that interrupts the existing team workflow. Example: "I love the product itself, but the Salesforce sync breaks often enough that managers stopped trusting the notes."</div>
</div>
<div class="tmpl-full-q">
<div class="tmpl-full-q-text"><strong>Reporting depth for managers and leadership</strong> — Comments on dashboards, trend reports, exports, and whether leaders can act on the insights without manual work. Example: "The call-level view is great, but I still have to build my own weekly leadership report in Sheets."</div>
</div>
<div class="tmpl-full-q">
<div class="tmpl-full-q-text"><strong>Pricing and seat model fit</strong> — Mentions of cost, ROI, seat limits, feature gating, or friction expanding usage across teams. Example: "We want product and CS in the tool too, but the seat pricing makes wider rollout a harder sell."</div>
</div>
<div class="tmpl-full-q">
<div class="tmpl-full-q-text"><strong>Reliability, performance, and trust</strong> — Comments about slow processing, missing transcripts, outages, failed uploads, or confidence in the system. Example: "When a high-stakes customer call takes hours to process, the team just goes back to manual notes."</div>
</div>
<div class="tmpl-full-q">
<div class="tmpl-full-q-text"><strong>Customer support and partnership</strong> — Feedback about responsiveness, feature feedback loops, onboarding help, or feeling heard by the vendor. Example: "Your support team fixed our tagging issue in one day and even suggested a better workflow, which is rare."</div>
</div>
<div class="tmpl-full-tip">💡 Tip: Keep the code list tight. In NPS analysis, the goal is to identify recommendation drivers and blockers, not to catalogue every detail. If two codes always appear together, merge them.</div>
</div>
<hr class="tmpl-full-divider">
<div class="tmpl-full-section">
<div class="tmpl-full-section-title">3. Theme Log</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Theme: Workflow integration friction · <span style="font-weight:400;color:#888">41 mentions</span></div>
<div class="tmpl-full-field-value">The strongest detractor driver was broken trust in downstream workflows, especially Salesforce field mapping and delayed Slack alerts. Top quote: "The summaries are good, but if the Salesforce sync drops the next-step field again, my reps still have to update everything by hand." → Recommended action: prioritize sync reliability fixes, publish status transparency, and add admin-facing error logs for failed records.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Theme: Searchability and insight discovery · <span style="font-weight:400;color:#888">33 mentions</span></div>
<div class="tmpl-full-field-value">Promoters consistently cited cross-call search and theme discovery as the feature that makes the product recommendable to peers. Top quote: "I can pull every clip where enterprise prospects asked about security in five minutes instead of listening to a week of calls." → Recommended action: lean into search and trend analysis in positioning, and create saved-search templates for sales, product, and CS teams.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Theme: AI summary quality and accuracy · <span style="font-weight:400;color:#888">29 mentions</span></div>
<div class="tmpl-full-field-value">Users see AI summaries as valuable but uneven, especially on nuanced objections, competitor mentions, and multi-speaker calls. Top quote: "It gets the broad strokes right, but the summary sometimes misses the exact reason the deal stalled, which is the part my managers care about." → Recommended action: improve handling of objection extraction, let users flag low-quality summaries, and expose confidence cues for key fields.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Theme: Reporting depth for managers and leadership · <span style="font-weight:400;color:#888">24 mentions</span></div>
<div class="tmpl-full-field-value">Managers like the call review experience but want more roll-up reporting for coaching, weekly reviews, and executive visibility. Top quote: "My team uses the scorecards, but I still can’t easily show leadership which objections are trending month over month." → Recommended action: add team-level trend dashboards, scheduled email digests, and exportable summaries for leadership updates.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Theme: Pricing and seat model fit · <span style="font-weight:400;color:#888">18 mentions</span></div>
<div class="tmpl-full-field-value">Expansion intent exists, but several passives said pricing limits broader adoption beyond revenue teams. Top quote: "I’d recommend it faster if product and onboarding could join without us needing to justify another block of paid seats." → Recommended action: test lighter viewer seats or stakeholder access tiers to remove expansion friction.</div>
</div>
<div class="tmpl-full-tip">💡 Tip: Write each theme card as if a busy product leader will only read one sentence. Include volume, what it means, one verbatim quote, and the action it suggests.</div>
</div>
<hr class="tmpl-full-divider">
<div class="tmpl-full-section">
<div class="tmpl-full-section-title">4. Comment Interpretation Notes</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">How to treat promoter comments</div>
<div class="tmpl-full-field-value">Look for the concrete behavior behind advocacy, such as faster coaching, easier call review, or better cross-functional visibility. Do not code praise alone unless it names a specific driver.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">How to treat detractor comments</div>
<div class="tmpl-full-field-value">Separate product dissatisfaction from operational friction. A low score may come from one recurring trust breaker, such as failed CRM syncs, even when the core analysis features are valued.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">How to handle mixed comments</div>
<div class="tmpl-full-field-value">Apply multiple codes when a respondent says both why they like the tool and why they hesitate to recommend it. Example: “Search is incredible, but summary accuracy still isn’t dependable for leadership reporting.”</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Outlier handling rule</div>
<div class="tmpl-full-field-value">Flag unusual but severe feedback separately if it signals revenue or retention risk, such as security concerns, missing calls, or repeated transcript failures in large accounts.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Escalation threshold</div>
<div class="tmpl-full-field-value">Escalate any theme mentioned by 10%+ of detractors or tied to core workflow trust, even if total mention volume is lower than a broad positive theme.</div>
</div>
<div class="tmpl-full-tip">💡 Tip: In NPS work, urgency is not always the same as volume. A lower-volume theme tied to trust, renewals, or executive credibility can matter more than a high-volume nice-to-have.</div>
</div>
<hr class="tmpl-full-divider">
<div class="tmpl-full-section">
<div class="tmpl-full-section-title">5. Summary Findings</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Top 3 themes by volume</div>
<div class="tmpl-full-field-value">1) Workflow integration friction (41) 2) Searchability and insight discovery (33) 3) AI summary quality and accuracy (29)</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Key takeaway</div>
<div class="tmpl-full-field-value">Recommendation intent is strongest when users can quickly surface cross-call insights, but trust drops when integrations and AI outputs are not dependable enough to power downstream workflows.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Most urgent action</div>
<div class="tmpl-full-field-value">Fix Salesforce sync reliability and expose clearer admin diagnostics, because this issue is undermining trust even among otherwise satisfied teams.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Metric to track</div>
<div class="tmpl-full-field-value">Weekly rate of successful CRM sync jobs, plus detractor mention rate for “integration friction” in next month’s NPS comments</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Secondary opportunity</div>
<div class="tmpl-full-field-value">Package search and insight discovery as a stronger expansion story for product, CS, and enablement stakeholders.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Stakeholder notes</div>
<div class="tmpl-full-field-value">Product: prioritize sync reliability and reporting depth. Engineering: add failure logging and processing alerts. GTM: use searchability proof points in customer stories. CS: proactively review accounts with repeated sync complaints.</div>
</div>
<div class="tmpl-full-field">
<div class="tmpl-full-field-label">Share with</div>
<div class="tmpl-full-field-value">VP Product, Head of Customer Success, Revenue Operations lead, Engineering manager for integrations, and CEO weekly product review</div>
</div>
<div class="tmpl-full-tip">💡 Tip: End with decisions, not just observations. A strong NPS analysis should make it obvious what to fix, what to double down on, what to monitor, and who needs to act.</div>
</div>
</div>
How to use it
Export your NPS responses Pull your NPS survey results — including scores and open-ended comments — from your survey tool into a spreadsheet.
Fill in one row per response For each comment, complete all four template sections: segment, verbatim text, theme, and recommended action.
Group rows by theme Sort or filter your spreadsheet by the Theme column to see how many responses share the same underlying issue or praise.
Prioritize by volume and segment Focus first on themes that appear most often among Detractors, since these represent your highest-leverage opportunities to improve retention.
What it looks like filled in
Onboarding Complexity
"It took me two weeks to feel comfortable using the product — the setup process was really confusing."
→ Redesign the onboarding checklist and add contextual tooltips at the three highest drop-off steps.
Customer Support Speed
"I love the product itself but every time I have a question it takes 3–4 days to get a real answer."
→ Introduce live chat during business hours and set an internal SLA of 24-hour first response for all tickets.
Reporting & Insights Value
"The dashboards finally helped our team align on what customers actually care about — we use it every week now."
→ Feature the reporting workflow in renewal conversations and build a case study around this use case for marketing.
Why teams skip the template
Manually reading hundreds of comments takes hours When your NPS survey generates more than 50 responses, categorizing each one by hand becomes a half-day task that rarely gets done consistently across team members.
Human theming introduces bias and blind spots Different analysts group comments differently, so the themes you surface often reflect assumptions you already had rather than what customers are actually saying.
Insights go stale before anyone acts on them By the time you finish tagging, summarizing, and presenting findings in a doc or slide deck, another wave of responses has already come in and the window for action has narrowed.
Analyze your NPS comments automatically — no template needed