An NPS detractor scored 0-6 and wrote a verbatim explaining why. The follow-up workflow that turns that comment into a save call, in five steps.
An NPS detractor is a customer who scored 0 through 6 — and wrote a verbatim explaining why. Most detractor handling stops at the score: an alert fires, a generic apology email goes out, the dashboard reports the detractor count, and the verbatim sits unread in an export. Sopact routes every detractor verbatim to a named owner on arrival, with the prior-wave verbatim and any attached document already there — so the conversation opens informed and the loop closes on a specific person.
By Unmesh Sheth · Founder & CEO, Sopact · Updated May 2026
An NPS detractor is a respondent who answered 0 through 6 on the 0-to-10 Net Promoter Score question. Detractors are typically unhappy customers and an active churn risk. The score is the trigger; the verbatim is the content. The customer's open-ended comment is where the failure mode is named in their own words, on the date the response submits.
The boundary is the score of 6. A 7 is a passive, not a detractor. The cutoff was set by Fred Reichheld and Bain in the early 2000s and has been the standard ever since. The range is the trigger, not the analysis.
Most detractors are at near-term churn risk — the score is itself a stated lack of recommendation. The exception is the converted detractor (was a promoter last wave), which is the strongest single signal in any NPS dataset.
The score is a number; the verbatim is the customer's description of what is broken — the integration that failed, the workflow that slowed down, the lost champion. The verbatim is the only strand the team can act on directly.
A real detractor record carries five things: the score, the verbatim, the prior wave, the contact's history, and any attached document. The dashboard shows the first. The work happens on the other four.
This is one record, not a row in a spreadsheet. The score is one line; the rest is the context that turns the score into an action.
For twenty years detractor handling was a metric. The team reported a detractor count, a detractor percentage, a rate of decline. The verbatim got exported. A canned email went out. The dashboard updated. Someone tracked the metric quarterly.
The reading was the bottleneck. With 200 detractors a quarter and one analyst, hand-coding was not happening. So the program shifted to the score and the count. The detractor became a number on a chart.
The reading bottleneck is gone. A modern language model classifies every detractor verbatim against the team's codebook in seconds. The work moved — from counting detractors, to routing each one's verbatim to a named owner with the prior context already in hand, and tracking whether the loop closed on that specific person. The detractor became a record again.
The score is the trigger. The verbatim is the action. The prior wave is the trajectory. The routing is the workflow. The logged resolution is the proof. A detractor program that tracks only the count is reporting on the trigger and ignoring everything that matters after.
This is the same locked argument that anchors /use-case/nps-analysis — expressed here through the workflow frame. The pillar covers analysis broadly; this page focuses on what to do with the one detractor in front of you.
Done well, detractor follow-up is five steps and a closed loop. Done badly, it is one canned email and an open record that the next wave reads against. These are the five steps that actually do the work.
The verbatim is read against the team's codebook on response-submit. Themes (named failure modes, lost-champion signals, integration breakage) attach to the record. The original wording stays. No quarterly batch.
The prior wave's score and verbatim. Recent support cases. The last QBR notes. The contract document, the renewal date, the relationship history. One record per customer, all in one place, before the conversation starts.
A relationship issue goes to the CS lead. A feature gap goes to the product team's customer rep. A service breakdown goes to the support manager. The owner is chosen by the failure named in the verbatim, not by the score threshold alone.
The owner arrives already having read what the customer wrote — not a sentiment label and not a chart. The conversation opens by acknowledging the specific failure named in the verbatim. The customer notices. The save rate moves.
What was promised, what was delivered, what the customer's response was. All on the same record that holds the score, the verbatim, the prior history. The next wave reads against this closed loop. From the next wave's perspective, the loop closed.
The dividing line between programs that close the detractor loop and programs that do not is step 5. Most programs do steps 1 through 4 and never confirm closure on the record. The next wave reads the new score against a blank prior — and the team starts over.
Each of these is reported as detractor follow-up in board decks. None of them is. They all share one trait: they treat the detractor as a number, not a record.
An automated "we are sorry to hear about your experience, we would love to learn more" reply goes to every detractor. It ignores the actual verbatim. The customer named a specific failure; the team responded with a template. The renewal call later opens with the same template energy, and the customer can tell.
FixThe first sentence of the follow-up references the specific failure the customer named in their verbatim. The template stays templated up to that one sentence.
A score below 6 triggers a Slack alert with the customer's name. The CS lead opens the alert, sees a name and a 4. The verbatim is not in the alert. The prior wave is not in the alert. The save call opens cold.
FixThe alert carries the verbatim text and the prior-wave score in the same message. No CS lead should ever see a detractor name without the comment the customer wrote alongside it.
A first-time 4 from a brand-new customer is routed the same way as a 4 from a customer who was a 9 two waves ago. The converted detractor is the strongest signal in the dataset — the relationship moved in a bad direction on a known customer — and threshold routing flattens it into the same bucket.
FixThe four sub-types (new, converted, chronic, silent) route on different paths. The converted detractor gets the senior account owner. The silent detractor gets a follow-up question. The chronic detractor gets renewal triage.
The CS lead has the conversation, takes notes in their inbox or a personal doc, makes the fix, moves on. The NPS record never learns that the loop closed. The next wave reads the new score against a blank prior, and the team has no view of which detractors got resolution and which did not.
FixThe follow-up call result is logged on the same contact ID that holds the original score and verbatim. The next wave reads the response against the closed loop, not against a memory.
The board sees "27 detractors this quarter, down from 31." It does not see how many were contacted, what was promised, what was delivered, what the customer's response was. Detractor count is a trigger metric, not an outcome metric. A program that reports only the trigger is reporting the easy half.
FixReport two numbers per board cycle: detractor count, and detractor resolution rate (the share where the loop actually closed on the record). The second is the one the program is being run for.
A 4 from a brand-new customer and a 4 from a customer who scored 9 two quarters ago are not the same data point. The trajectory tells the story the score cannot.
First-time response, score 0-6. Usually an onboarding or early-relationship failure. The verbatim is the team's first signal. Useful for product and onboarding fixes.
Was a promoter or passive last wave, now a detractor. The strongest single signal in any NPS dataset. The relationship moved in a bad direction on a known customer.
Low score across multiple consecutive waves. The renewal is at structural risk and the verbatim usually names something the team has not been able to fix. Different problem than the converted detractor.
Low score, no verbatim — or a verbatim of "no comment" or two words. The score is a trigger; the team has no reason attached. Cannot be acted on without a follow-up question.
Routing by these four types instead of by score threshold alone is the most reliable upgrade a detractor program can make. The converted detractor especially — the customer whose relationship just moved — is the conversation the team should have first, before anything else on the list.
This page covers the detractor specifically — the customer, the verbatim, the follow-up. Three adjacent reads in the NPS cluster handle the broader methodology, the closed-loop hub, and the buying decision.
What NPS analysis means in 2026, the methodology, the AI-era thesis. The broader treatment above this page.
Read the pillar →The detractor specifically — the anatomy of a record, the four sub-types, the follow-up workflow, the anti-patterns.
This pageThe full feedback signal — rating, verbatim, prior history, attached context — and the broader closed-loop workflow this page sits inside.
Read the hub →If you came here to handle a specific detractor better, stay on this page. If you came for the broader feedback loop, the informational hub is the right next read. If you came for the methodology, the pillar is.
Same detractor instrument, three different teams. The cost of a detractor follow-up that never closed is different in each context — and the workflow that does close is the same.
A relational NPS at quarterly cadence. A converted detractor (was a 9, now a 4) routes to the senior account owner within hours. The save call opens with the exact sentence the customer wrote, alongside the prior wave's verbatim. The customer can tell the team read what they wrote.
An end-of-module NPS reveals a 3 from a participant who scored 9 in the prior module. Their verbatim names the part of the curriculum that broke. The program team has a real-time window to retain that participant in the cohort instead of reading the dropout note three weeks later.
A scholarship program with NPS-style feedback mid-cycle. A 2 arrives from an awardee whose original application essay reads ambitiously. The verbatim names the mismatch between what the program promised and what landed. The program team has the awardee's own application to read the comment against.
Your scores, your verbatims, your contacts. Sixty minutes. No demo accounts.
An NPS detractor is a respondent who answered 0 through 6 on the Net Promoter Score question — a 0 to 10 scale where 0 is "extremely unlikely to recommend" and 10 is "extremely likely to recommend." Detractors are typically unhappy customers and an active churn risk. Their verbatim comment is where the failure mode is named, in their own words, on the date the response submits.
Detractors are customers who score 0 through 6 on the 0 to 10 NPS question. The boundary is 6 — a 7 is a passive, not a detractor. The range was set by Bain and Fred Reichheld in the early 2000s and has been the standard ever since. The score range is the trigger; the verbatim is the content of the response.
The score is a number from 0 to 6. The verbatim is the customer's own description of what is broken — the integration that failed, the support experience that disappointed, the missing capability, the lost champion. A CS lead cannot make a save call from "score: 4." They can make a save call from the sentence the customer actually wrote. The verbatim is the only strand the team can act on directly.
Detractor follow-up is the workflow that closes the loop on a specific detractor response: the verbatim is read on arrival, a named owner is assigned, the conversation happens with the customer's prior context in hand, the action is logged on the same record, and the next wave reads against the closed loop. Detractor follow-up that stops at a generic apology email is the most common failure mode of "closed-loop NPS" programs.
Five things have to happen. Read the verbatim in full, not as a sentiment label. Pull the customer's prior submissions on the same record so the conversation opens informed. Assign a named owner appropriate to the named failure — the CS lead for a relationship issue, the product team for a feature gap, the support manager for a service breakdown. Have the conversation with the verbatim wording in front of you. Log the result on the record so the next wave reads against a closed loop, not an open one.
Four useful sub-types. The new detractor (first-time response, score 0-6) — usually an onboarding or early-relationship failure. The converted detractor (was a promoter or passive last wave, now a detractor) — the highest-priority signal in the dataset, because the relationship moved in a bad direction on the same customer. The chronic detractor (low score across multiple waves) — the renewal is at stake and the verbatim usually names a structural issue. The silent detractor (low score, no verbatim) — the team has to follow up to understand the reason, because nothing was named.
A converted detractor is a customer whose NPS score moved from promoter (9-10) or passive (7-8) in a prior wave to detractor (0-6) in the current wave. This is the most important signal in an NPS program. Their verbatim names what changed, and the same customer's prior verbatim explains what they used to value. A converted detractor on a relationship the team has invested in is a near-term churn risk that named itself, on the same record, with the reason attached.
Five recurring ones. Sending a generic "we're sorry, we'd love to hear more" email that ignores the actual verbatim. Routing by score threshold without the verbatim or the prior context attached. Treating every detractor the same instead of distinguishing the four sub-types. Logging the follow-up call outside the NPS record so the next wave starts blind. Reporting detractor count as a metric without per-detractor resolution status.
Within days, ideally hours. The verbatim is most actionable while the experience is fresh in the customer's memory. A follow-up that arrives a month later, after the team has read the quarterly memo, is reading a customer who has already moved on. Reading-on-arrival is what makes detractor follow-up timely; quarterly batch reporting is what makes it useless.
Every detractor whose verbatim names an actionable failure. Programs that follow up only with the lowest scorers miss the converted detractors — customers who scored a 5 this wave after a 9 last wave are a stronger signal than first-time 1s, because the change names the failure. The right criterion is the verbatim and the trajectory together, not the score alone.
Detractor follow-up is the load-bearing stage of any closed-loop NPS program. A program that does not close the loop on detractors is not closed-loop. The loop closes when the verbatim is read, the owner takes the action, the result is logged on the record, and the next wave reads against the closed loop. See /use-case/nps-feedback for the broader closed-loop workflow this page sits inside.
This page covers the detractor specifically — the customer, the verbatim, the follow-up. NPS analysis is the broader methodology. NPS verbatim analysis is the commercial sub-hub for teams shopping for a tool that reads any verbatim, not just detractor verbatims. NPS feedback is the informational hub for the full feedback signal.
The detractor is one room. The cluster covers the methodology, the closed-loop frame, and the buying decision.
The pillar above this page — what NPS analysis means in the AI era, the workflow, the methodology, the locked thesis behind the cluster.
The full feedback signal and the broader closed-loop workflow this page sits inside — how to think about NPS feedback as a system, not a chart.
For teams shopping a tool that reads the open-ended comment specifically — six buyer-checklist criteria and a category-by-category comparison.
Your scores, your verbatims, your contacts. Sixty minutes. We classify each detractor verbatim on arrival, attach the prior-wave verbatim and any case notes from the same contact, and walk through what routing-with-context would have changed about the last quarter's save calls. No demo accounts. No slideware. Your own detractors, read live.
No slideware. No demo accounts. Your own detractors, read live.
