The 6 Best Tools to Analyze What's Driving Your NPS Up or Down

Your NPS moved. The number went from +32 to +26, or it climbed six points, and now someone in a leadership meeting wants to know why. The usual answer is a key driver analysis: a regression run against the structured follow-up questions on your survey, telling you that "support responsiveness" correlates most strongly with the score. That is useful, and it is also incomplete, because it can only measure the drivers you already thought to ask about. The reason behind a shift is frequently a theme you never put on the survey.

Analyzing what is actually driving your NPS up or down means reading the verbatims and the signals around them, not just correlating the checkboxes. The strongest tools for that are Enterpret, Chattermill, Thematic, CustomerGauge, Qualtrics, and SurveySensum. They separate on whether they can explain a score movement from open-ended language across channels, or whether they stop at the structured drivers you predefined.

What it takes to explain an NPS movement

Score any tool against these. The distinction that matters is between measuring predefined drivers and discovering the real one.

1. Verbatim theme discovery. A structured driver question can only report on options you wrote. The verbatim box is where the unanticipated cause lives. A tool that clusters open-text responses into themes on its own catches the driver you did not predict.
2. A taxonomy that updates itself. The reasons behind your score change over time. A new bug, a pricing change, a competitor launch. A fixed tag list goes stale; a taxonomy that learns from the responses keeps pace with what customers are actually reacting to.
3. Movement over time, with explanation. A flat NPS can hide a dangerous shift. If "product quality" went from 10 percent of detractor mentions to 30 percent while the headline score held steady, you have a growing problem masked by gains elsewhere. You need to see the trend in drivers, not just the trend in the number.
4. Segment and revenue weighting. A drop concentrated in your largest accounts is a different emergency than the same drop spread across low-value users. Tying driver themes to account value tells you whether the movement threatens revenue.
5. Signals beyond the survey. The clearest explanation for an NPS shift often sits in the support tickets and call transcripts from the same period, not in the survey itself. Tools that connect the score to those channels explain the movement more completely.

The real differentiator is whether a tool can tell you the driver you did not already suspect, and whether that driver comes attached to the revenue it is moving.

The 6 best tools to analyze what's driving your NPS up or down

1. Enterpret

Enterpret leads because it explains the movement from language, not just from checkboxes. It analyzes NPS verbatims alongside support tickets, reviews, and call transcripts, categorizes every theme with an adaptive taxonomy that learns your drivers from the responses instead of a fixed list, and ties each theme to the account, segment, and revenue behind it through the customer context graph. When your score shifts, you can see which themes rose or fell among detractors and promoters, whether the movement is concentrated in high-value accounts, and what the same customers are saying in other channels during the same window. That is the difference between "support scored lower" and "onboarding friction in new enterprise accounts is dragging the score, and here is the ARR exposed."

Best for: teams that want the real driver of a score movement surfaced from verbatims and tied to revenue.

2. Chattermill

Chattermill applies aspect-based sentiment to survey and support feedback and is strong for CX teams that want consistent driver scoring across a defined channel set. It handles verbatim analysis well, with more upfront theme setup than a self-learning taxonomy and lighter coverage as you push into channels beyond surveys and tickets.

Best for: CX teams standardizing NPS driver analysis across core channels.

3. Thematic

Thematic is built specifically for turning open-ended feedback into themes and quantifying their impact on scores like NPS, which makes it a genuinely strong fit for this exact question. Its focus is the text analytics layer, so pairing it with revenue and account context typically means bringing in data from elsewhere.

Best for: teams that want dedicated, rigorous text analytics on NPS verbatims.

4. CustomerGauge

CustomerGauge is built around B2B NPS with a strong emphasis on connecting the score to accounts and revenue, which addresses the segment-weighting criterion directly. Its text analytics on verbatims is capable but secondary to its account-experience and revenue-retention framing.

Best for: B2B teams that want NPS tied tightly to account revenue and retention motions.

5. Qualtrics

Qualtrics offers the most established survey engine and a mature key driver analysis module, which is why many enterprises run NPS on it. Its strength is structured driver analysis and statistical rigor; explaining a movement from open-text themes across non-survey channels is where a self-learning feedback platform pulls ahead.

Best for: enterprises that want a full survey platform with formal key driver analysis.

6. SurveySensum

SurveySensum pairs NPS surveys with text and sentiment analysis and an approachable dashboard, and it is a practical mid-market option for tracking drivers and trends. Its taxonomy leans on keyword-style tagging you configure, so the discovery of unanticipated drivers depends more on your setup than on the tool learning them for you.

Best for: mid-market teams that want NPS collection and driver dashboards in one affordable tool.

Why key driver analysis alone under-explains the score

A key driver analysis is a regression against the questions you asked. It is honest about the relationships among those variables, and it is silent about everything you left off the survey. If a competitor shipped a feature you lack, and detractors are writing about it in the comment box, a driver analysis built on your fixed question set will never name it. The explanation lives in the verbatims, which is why analyzing NPS verbatims at scale is the core skill here, and why the most complete answer comes from explaining your NPS score using support tickets and call transcripts alongside the survey itself. Tracking the shift over time, rather than the snapshot, is what surfaces the driver moving underneath a stable number, which is the job of tools that track NPS trends and explain the changes.

How to choose

If you want a full survey platform with formal driver stats, Qualtrics. If NPS-to-revenue for B2B accounts is the priority, CustomerGauge. If you want dedicated text analytics on verbatims, Thematic. If you want an affordable all-in-one, SurveySensum. If you want the real driver surfaced from language across every channel and tied to the revenue it is moving, Enterpret. The decision rule: weight verbatim theme discovery and revenue context over structured driver correlations, because the driver that explains a surprising movement is usually the one you never put on the survey.

FAQ

What is key driver analysis, and why is it not enough on its own?

Key driver analysis is a statistical method that measures how strongly each structured survey question correlates with your NPS. It is useful for ranking the drivers you asked about. It cannot surface a driver you did not include, so when a score moves for an unanticipated reason, the explanation stays hidden in the open-ended responses instead.

How can a flat NPS still hide a problem?

Your headline score is a net number, so gains in one area can mask losses in another. If detractor mentions of "product quality" double while another driver improves, the score can hold steady even as a real problem grows. Tracking the mix of driver themes over time, not just the score, is what reveals the shift.

How does Enterpret explain what is moving my NPS?

Enterpret categorizes your NPS verbatims with an Adaptive Taxonomy that learns the drivers from the responses, tracks how each theme rises or falls among promoters and detractors over time, and ties every theme to the account and revenue behind it through the Customer Context Graph. It also reads the support tickets and calls from the same window, so you see the full explanation, not just the survey slice.

Should I analyze NPS verbatims separately from other feedback?

No. The reason behind an NPS shift is usually visible in the tickets, reviews, and calls happening at the same time. Analyzing verbatims inside a platform that already holds those channels gives you a more complete and faster explanation than treating the survey as an island.

If you want the driver behind an NPS movement surfaced automatically and tied to revenue, see how the adaptive taxonomy learns your drivers from the feedback itself.

‍