What an NPS detractor is and how to turn low scores into a prioritized fix list: read the reason, rank the drivers, close the loop.
An NPS detractor is any respondent who scores 0 to 6 on the 0-to-10 Net Promoter question: a customer or stakeholder at risk of leaving and, worse, of discouraging others. In the Net Promoter formula, detractors are subtracted from promoters, so a detractor does not just fail to help the score — it actively pulls it down. The count is the alarm; the comment beside it is the diagnosis.
The trap teams fall into is treating detractors as a percentage to shrink rather than people to answer. “Our detractor rate went up three points” is a number; “fourteen detractors this month all named the same broken onboarding step” is a task. Getting from the first sentence to the second means reading the detractor comments, and that reading is usually what never happens.
Key takeaways
The Net Promoter math makes detractors easy to think about as arithmetic: subtract them from promoters, divide, get a score. That framing quietly turns a customer telling you what is wrong into a decimal you want to move. The most valuable thing a detractor gives you is not the low score; it is the sentence explaining it, offered for free by someone motivated enough to complain.
Most feedback tools lose that sentence. The score lands in a bucket and the comment lands in a column, and there is no mechanism to read the comment against a codebook or to keep it attached to the person for the next survey. Sopact calls the alternative the Verbatim Thread: every detractor’s comment read on arrival, themed and cited, and kept on the same persistent contact record as the score and the follow-up. A detractor becomes a named reason you can route, act on, and check back against — the model behind Sopact’s feedback tools.
Handling detractors moved through three eras. First, a monthly export where the detractor rate was tallied and the comments skimmed. Then the NPS dashboard — Delighted, AskNicely, and peers — which trended the detractor percentage and, in better versions, triggered an alert email when a low score arrived. The current era reads the detractor comment itself, themes it, and keeps it on the person so the loop can actually be closed and verified.
The one test that separates the eras: ask a tool to show you a detractor’s score, the sentence that explains it, the theme it belongs to, who owns the fix, and whether that person scored higher at the next wave. A dashboard can raise an alert; it cannot show the reason, the owner, and the follow-through on one record. If the tool stops at an alert, the loop is open by design.
Closing the loop means four things in order: read the detractor’s reason, route it to whoever owns that fix, act, and confirm at the next wave that the same person’s score moved. Skipping the read makes the routing guesswork; skipping the confirmation makes the whole exercise unfalsifiable. The persistent record is what makes step four possible, because you can find the same detractor again instead of hoping the aggregate drifts up.
There are two kinds of loop to close. The individual loop answers one detractor: reach out, fix their issue, and watch their next score. The systemic loop answers the pattern: when fourteen detractors name the same onboarding step, the fix is not fourteen phone calls but one process change. Reading and ranking the drivers is what tells you which loop you are in, and a themed read makes both visible where a detractor rate makes neither.
Pull every detractor comment, theme each against a fixed codebook, then rank the themes by how many detractors raised them and by their average score — the lowest-scoring, most-frequent driver is the first fix. Frequency alone over-weights common minor gripes; score alone over-weights a single furious outlier. Ranking on both surfaces the driver doing the most damage to the most at-risk customers.
The output is a short list a team can own: driver, detractor count, example quote, average score, and suggested owner. Because Sopact themes detractor comments on arrival and keeps them on the Verbatim Thread, that list is live — a new detractor naming the same driver updates the ranking the day the comment lands, and the follow-up wave shows whether the fix is working. This is the same discipline that NPS verbatim analysis applies across the whole scale.
A detractor rate tells you the trend is bad; a themed read tells you which driver to fix first and for whom. Both start from the same low scores and comments and end in very different places.
| The question | Detractor rate | Themed read (Verbatim Thread) |
|---|---|---|
| What do you learn? | The percentage of 0–6 scores, over time | The ranked reasons behind them, with quotes |
| Can you prioritize a fix? | No: a rate is not a cause | Yes: drivers ranked by frequency and score |
| Does it name who to call? | No: scores are detached from people | Yes: each detractor is a record with a reason |
| Can you prove the fix worked? | Only if the aggregate happens to move | Yes: the same detractor’s next-wave score |
Reading detractors is one cut of the broader read on every comment in survey analysis, and the ongoing version lives on continuous feedback.
An NPS number is a lagging summary; the reason a customer gave it is in the comment, and only if someone reads the comment while it still matters. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, analyze the moment a response arrives, improve while there is still time to act. On a feedback program that means a detractor’s reason is themed the day it lands and routed to someone who can close the loop, not filed for a quarterly readout.
The Loop is also what makes an NPS finding defensible: every driver and theme traces to the exact comment it came from, the standard detailed in Loop traceability, so “price is the top detractor driver” is backed by the sentences, not a hunch.
One method, three moves that never stop
Then the cycle runs again, a little sharper each time. Read the method: the Loop methodology →
The fastest way to feel the difference is to work your own detractors. Export the 0-to-6 scores and their comments, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Analyze open-ended survey responses
Here are our NPS comments with each respondent's score: [ATTACH]. Theme every comment against our codebook, cite the sentence behind each theme, and show the top five themes among detractors, passives, and promoters separately.
Academy walkthrough → Analyze sentiment and its drivers
For these NPS verbatims: [ATTACH], score sentiment per comment, then show the specific drivers behind the detractor comments — the recurring reasons, each with a quoted example — so I know what to fix, not just the score.
Academy walkthrough → Connect quant and qual data
Here are our NPS scores and open-ended comments on the same respondent IDs: [ATTACH]. Show which themes explain the detractor scores, quote a comment for each, and list the specific respondents worth a personal follow-up.
Academy walkthrough → Analyze NPS across waves
Here are two waves of NPS from the same respondents on the same IDs: [ATTACH]. Track each respondent's movement between waves, show who moved from detractor to promoter and who slipped, and surface the comments that explain the biggest moves.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: reading feedback on arrival and tying every comment to the person who gave it.
An NPS detractor is a respondent who scores 0 to 6 on the 0-to-10 Net Promoter question, at risk of leaving and of discouraging others. Detractors are subtracted from promoters in the NPS formula. Sopact keeps each detractor on the Verbatim Thread, so the score, the stated reason, and the follow-up all live on one record.
Because the Net Promoter formula subtracts detractors from promoters, a detractor pulls the score down twice as hard as a passive, which is simply ignored. But the bigger reason is qualitative: a detractor is a customer telling you, unprompted, exactly why they might leave. Sopact reads that reason on arrival instead of letting it sit in a column.
Read every detractor comment, theme it against a fixed codebook, rank the themes by frequency and by average score, and route the top driver to an owner. Then confirm at the next wave that the same detractors scored higher. Sopact runs the theming on arrival and keeps the detractors on a persistent record so step four is possible.
The individual loop answers one detractor: reach out, fix their issue, and watch their next score. The systemic loop answers a pattern: when many detractors name the same driver, the fix is one process change, not many calls. Sopact’s ranked driver read tells you which loop you are in.
Rank drivers by both how many detractors raised them and their average score. The most frequent, lowest-scoring driver is doing the most damage to the most at-risk customers, so it comes first. Sopact updates that ranking on arrival as new detractor comments land on the Verbatim Thread.
Yes, if identity persists. Because Sopact keeps each detractor on a persistent contact record, you can check whether the same person scored higher at the next wave, rather than hoping the aggregate drifts up. That closes the loop in a way a detractor rate alone never can.
Contact the ones whose issue is individual and recoverable, and fix the process behind the ones who share a driver. A themed read separates the two, so you spend outreach where it changes a relationship and spend engineering where it changes the pattern. Sopact surfaces both from the same comments.
A detractor scores 0 to 6 and is subtracted from your NPS; a passive scores 7 to 8 and is ignored by the formula. Detractors name what is broken; passives name the cheapest path to loyalty. Sopact themes each segment for its own question rather than pooling them.
Next: read the whole scale, not just the bottom, in NPS verbatim analysis, or keep the loop running with continuous feedback.
