What does a negative NPS mean?
A negative Net Promoter Score means the percentage of detractors exceeds the percentage of promoters among the valid responses. It is a signal to investigate the customer experience and the way the survey was conducted. It does not tell you, by itself, which customers will leave, what caused the result or how quickly it can improve.
Start with the calculation, then review who responded, what they experienced and what the comments actually say. A useful response plan addresses specific problems and checks whether the changes helped. Chasing a positive number without that work can produce a better-looking report while leaving the experience unchanged.
How a score becomes negative
The standard NPS calculation groups 0–6 responses as detractors, 7–8 as passives and 9–10 as promoters. Subtract the detractor percentage from the promoter percentage. Passives remain in the total response denominator. See Bain’s NPS measurement explanation.
Example: among 100 valid responses, 25 are promoters, 30 passives and 45 detractors. NPS = 25% − 45% = −20. This is a score of minus 20, not a statement that 20% of customers are dissatisfied.
A negative score does not require a majority of detractors. If 20% are promoters, 50% passives and 30% detractors, NPS is −10. The result describes the balance of the two categories, not everyone’s complete experience.
Likewise, −100 means every valid response was in the detractor category. It does not mean every customer was surveyed or that all respondents intend to cancel. Report the response count and survey audience with the score.
What should you check first?
Scroll horizontally to see all columns →
| Check | What to inspect | Why it matters |
|---|---|---|
| Calculation | Rating boundaries, valid responses, duplicates and missing answers | An incorrect denominator or reversed formula can produce a misleading result. |
| Audience | Who was invited and who responded | A support-only sample is different from the whole customer base. |
| Timing | When the invitation arrived relative to onboarding, support or renewal | Different moments can produce different accounts of the experience. |
| Question | Exact wording, scale and language versions | A changed question is not automatically comparable with an earlier one. |
| Coverage | Counts by customer type, tenure and relevant service group | A changed respondent mix can move the total score. |
| Operational context | Known outages, policy changes or delivery problems | These provide leads to investigate alongside the feedback. |
A methodology change and a real service problem can occur together. Comments alone cannot reliably separate them. Check the invitation and response records as well as the customer accounts of what happened.
Is a negative NPS always bad?
It warrants attention: detractor responses outnumber promoter responses. The scale of the concern depends on the survey’s purpose, coverage, history and the experiences described. Avoid dismissing the result because a benchmark is lower, or declaring a business crisis from a small or unusual response set.
A change from −30 to −10 is an improvement in the observed score, even though it remains negative. A change from +40 to −5 deserves investigation even if another company also reports −5. Your own comparable history and relevant NPS benchmarks answer different questions.
Small samples can move sharply. With ten responses, changing one person’s category from detractor to promoter changes NPS by 20 points. Show the counts so readers can judge the result’s stability. Do not call a small movement statistically meaningful without analysis suited to the sampling design.
Read the feedback before deciding what to fix
Group comments into clearly defined topics, retain their source text and review examples. Separate a billing dispute from difficulty understanding the bill, even if both initially fall under “billing.” The remedy may be different.
Include passives and promoters where they provided feedback. They may describe the same problem with different consequences or identify practices worth preserving. A low recommendation rating is not itself a complete description of the person’s needs.
If only 20 of 45 detractors leave comments, state that coverage. A theme found in ten comments occurs in half of the detractor comments; it does not establish that half of all detractors experienced it. For the coding process, see analyzing open-ended responses.
Look for both recurring issues and less frequent serious concerns. Frequency alone should not decide priority. Nor should a vivid quotation outweigh all other evidence. Read the context, confirm what can be checked and identify the team responsible for the next step.
Build a practical recovery plan
The following is a fictional planning example. Its purpose is to show how feedback becomes work, not to promise a score improvement.
Scroll horizontally to see all columns →
| Reported concern | Evidence to check | Action and owner | Follow-up measure |
|---|---|---|---|
| No confirmation after registration | Comments, delivery logs and a test submission | Operations tests the message and clarifies completion status. | Confirmation delivery and later reports of uncertainty |
| Unexpected billing amount | Account details, terms shown and support records | Billing reviews the discrepancy and explains the outcome. | Resolved cases and recurrence of the same issue |
| Repeated support handoffs | Request history and responsibility changes | Service lead assigns an accountable owner and reviews handoffs. | Time to resolution and customer-reported effort |
Prioritize using severity, reach, evidence strength, feasibility and responsibility. There is no universal rule that the two or three most common themes will restore a positive score. Some problems involve several processes; some require a decision about the service itself.
Set a review date and record what was changed. Avoid a generic discount campaign unless it addresses the actual issue and makes sense for the customer. A price complaint could concern value, an error or affordability; those call for different responses.
Respond to customers without pressuring the score
Where contact is appropriate and permission exists, acknowledge the issue, clarify what remains unresolved and explain the next step. Keep the response focused on the experience. Do not ask someone to raise a rating in exchange for help or remove their original feedback after a resolution.
For anonymous surveys, return a summary of findings and actions through the appropriate shared channel. Anonymous responses can still support service improvement even when personal follow-up is impossible.
Keep source access limited to the people who need it. An executive summary can show themes and action status without circulating every identifiable comment. If the feedback raises a concern requiring a separate response process, use that process rather than leaving it in an NPS dashboard.
How do you know whether the changes helped?
Track the operational change and the later experience, as well as NPS. If the problem was failed confirmations, check delivery and reported uncertainty. If the issue was repeated handoffs, check whether requests now reach a responsible owner. These measures help you understand what actually changed.
Keep the survey approach sufficiently consistent for comparison. Where authorized matching is available, examine the same customers across waves and report how many returned. Also show the overall result, since a matched subset may not represent everyone.
A higher next-wave score from the same customers does not by itself prove your action caused it. Other changes, timing, selective return and ordinary variation can contribute. Describe the observed improvement and the supporting evidence without claiming more than the design supports.
Do not set a promised recovery deadline from a generic article. Choose a follow-up interval that gives customers a reasonable opportunity to experience the change. Continue tracking unresolved issues even if the headline score has already improved.
Keep feedback and follow-through connected
A growing team needs to connect the survey response, relevant service context, reviewed theme and action status. Otherwise the next report may repeat the same concern without showing what happened to it.
Sopact’s relevant approach brings collection, analysis and governance into a workflow an operational team can maintain. Test it using a real feedback cycle: find the source behind a theme, review an ambiguous answer, assign an action and compare later evidence. Confirm permissions and any account or service-data connections required.
NPS tools can already collect ratings and comments. The buying question is whether your team can maintain the complete process at a reasonable cost as data sources and responsibility grow. Use the NPS software checklist to evaluate that work.
Watch the feedback companion
See Sopact’s discussion of reading feedback alongside its context.
Frequently asked questions
Can NPS be below zero?
Yes. The score ranges from −100 to +100. It is negative when the percentage of detractor responses exceeds the percentage of promoter responses.
Does negative NPS predict churn?
It can indicate experiences worth investigating, but the score alone does not predict which customer will cancel. Compare feedback with appropriate service and retention evidence before drawing that conclusion.
How quickly can a negative score improve?
There is no universal timeline. It depends on the issue, the action, when customers experience the change and who responds to the next survey.
Should I remove passives from the calculation?
No. Passives are included in the total valid responses used to calculate promoter and detractor percentages, although they are not added or subtracted as a separate category.
Does a higher score prove the recovery plan worked?
No. It shows improvement in the observed result. Check comparable coverage, operational changes and other explanations before attributing the movement to a particular action.
