How to Turn NPS Detractors Into Promoters (And Get Them to Leave Good Reviews)
A customer who scores you 3 out of 10 has done something most unhappy customers won't: they told you. That low score is a private signal sent before they've posted anything publicly. Handle it well and you have a real shot at converting a critic into one of your most credible advocates.
TL;DR — Key Takeaways
- •A detractor is a pre-complaint. They scored you 0-6 privately before leaving any public review — that window is your opportunity.
- •The recovery framework has four sequential steps: respond within 24 hours, resolve the actual issue, send a follow-up check-in to confirm recovery, then ask for a review.
- •Step 3 is the one most businesses skip. The follow-up check-in confirms the resolution worked from the customer's perspective, not just yours.
- •The review ask belongs at the end — only after confirmed resolution, with no hint about which score to leave. The FTC's Endorsement Guides and every major review platform prohibit incentivized or directed review requests.
- •Detractors who don't respond get no review request. Non-engagement means you have no basis to assume the issue resolved itself.
There's a pattern in customer experience research that surprises most business owners when they hear it: a customer whose complaint gets a fast, genuine response sometimes ends up more loyal than a customer who never had a problem at all. Customer experience researchers call this the service recovery paradox. It doesn't happen automatically and it doesn't happen every time, but the conditions that produce it are learnable and repeatable.
NPS detractors — anyone who scored you between 0 and 6 on a Net Promoter Survey — are exactly the kind of customer where this recovery is possible. They haven't walked away silently. They haven't opened Yelp or Google yet. They told you, through a structured survey, that something went wrong. That choice to respond, even negatively, is a form of engagement. Build a process around it.
A Detractor Is Not the Same as a 1-Star Reviewer
The clearest way to understand why detractors deserve a dedicated recovery process is to contrast them with what they haven't yet become.
A 1-star reviewer has told the world. A detractor has told you. That distinction is the entire point. When someone leaves a public negative review, the interaction is already documented, already visible to future customers, and already partially outside your control. Your response matters, but the damage to your profile is done. For guidance on handling that situation, our guide on responding to negative reviews covers the public-facing side of that conversation.
A detractor is earlier in the sequence. They scored you 0-6 on a survey that came directly to you, and that survey response probably arrived within 24-48 hours of their experience. You know who they are. You know which service interaction produced the low score. You have their contact information. None of that is true once they've left an anonymous review.
The practical implication: detractors are pre-complaints. The low score is early warning, not a verdict. Leave it unaddressed for two weeks and two things tend to happen. The frustration solidifies into a fixed narrative. And the likelihood they'll take that narrative somewhere public increases considerably.
For context on how NPS scores and public reviews relate to each other as measurement tools, our comparison of how NPS scores connect to your public review profile covers that relationship in detail.
The 4-Step Detractor Recovery Framework
The framework works in sequence. Each step depends on the one before it. Skipping step 3 to rush to step 4 is the most common mistake, and it's the one that produces the kind of low-quality review requests that feel predatory to customers and look hollow on your profile.
Step 1 — Acknowledge Within 24 Hours
The first message does not need to contain a solution. Its job is to signal, clearly and specifically, that a real human read their survey response and that the complaint was taken seriously. That alone matters more than most business owners realize.
An unhappy customer's frustration is partly about the original issue and partly about the feeling that their experience didn't register with anyone. The 24-hour acknowledgment directly addresses the second part before you've even tackled the first. The message should reference the specific issue they raised, not a generic "we're sorry for any inconvenience." It should take clear ownership and commit to a follow-up by a specific time.
What to avoid: promising a resolution you haven't confirmed yet. "I'll look into this and get back to you by end of day Thursday" is more credible than "we'll get this sorted right away" followed by four days of silence.
Email Template 1 — Initial Acknowledgment
Subject: Your recent experience with [Business Name]
Hi [First Name],
I saw your survey response and wanted to reach out directly. I'm sorry your experience fell short of what you'd expect from us — specifically with [the issue they mentioned]. That's not the standard we hold ourselves to.
I want to make this right. I'm looking into exactly what happened and will follow up with you by [specific date]. If there's anything you'd like to add in the meantime, please just reply here.
[Your name]
[Title], [Business Name]
Keep this first message short. The customer isn't looking for a wall of text — they're looking for evidence that someone actually read what they wrote.
Step 2 — Resolve the Actual Problem
This is where most service recovery attempts fail. A warm tone in the first email buys goodwill. What converts that goodwill into genuine recovery is fixing whatever caused the low score.
"Resolving with empathy" is sometimes misread as "apologizing at length." Those are different things. A long apology that doesn't address what went wrong, offers a token discount, and promises that "your feedback has been shared with the team" lands as hollow. The customer can usually feel the difference between a scripted response and a genuine one.
Real resolution looks like: finding out specifically what happened, explaining it honestly (without shifting blame), taking a concrete corrective action, and communicating what changed. If a customer waited 45 minutes past their appointment time, a $10 coupon isn't a resolution. Rescheduling them at priority availability and explaining what caused the delay is closer.
The second email goes out after you've actually done the work.
Email Template 2 — Resolution Follow-Up
Subject: Following up — here's what we did
Hi [First Name],
I wanted to follow up on what happened. [Brief, direct explanation of what went wrong — no excuses.] Here's what we've done about it: [specific action taken].
We'd like the chance to make this right directly. [Specific offer: a replacement service, refund, or priority rescheduling — whatever fits your business and the situation.] No strings attached.
If you'd prefer we don't contact you again, just reply and we'll respect that completely. Otherwise, I'd welcome the chance to earn your trust back.
[Your name]
[Business Name]
The tone here is direct and human. Notice what it doesn't include: superlatives about your company's values, reassurances about how rare this situation is, or references to your commitment to excellence. Those read as stock language and they're the signal that nobody in your organization actually cares.
Step 3 — The Follow-Up Check-In (3-5 Days Later)
This is the step businesses skip most often, and it's the most important one for what comes next.
Sending a resolution email doesn't mean the customer feels resolved. It means you took action. Those are not the same thing. The follow-up check-in exists for one specific purpose: confirming that the resolution worked from the customer's side, not just from yours.
Qualtrics refers to this as closing the loop in their closed-loop feedback methodology. The principle is that a complaint isn't closed until the customer confirms it is, not until the team marks it complete internally. A three-to-five day gap after the resolution communication gives the customer time to process the interaction. Too short and you risk feeling impatient; too long and the context fades.
The check-in can be a simple two-question survey ("Did we address what you needed? Is there anything else you'd like us to know?") or a direct personal note. What matters is that it's asking, not assuming. If the customer confirms yes, you move to step 4. If they indicate the issue isn't resolved, you go back to step 2. If they don't respond at all, see the section below on non-engaging detractors.
Step 4 — The Review Request (Only After Genuine Resolution)
If the first three steps went well — the customer confirmed the issue was resolved, they responded positively, and several days have passed — a review request is both appropriate and likely to produce something useful.
The ethical framework here is worth spelling out clearly. The FTC's Endorsement Guides (16 CFR Part 255) prohibit offering any incentive in exchange for a review without disclosure. That applies to discounts, free services, gift cards, or anything of value. Google's review policies independently prohibit incentivizing or discouraging reviews. So does Yelp's content policy. The ask should be clean: you resolved their issue, you believe they feel good about the outcome, and you're asking whether they'd be willing to share that experience.
Never specify the score or the star rating you're hoping for. Never say "a positive review" or "if you had a good experience." Just ask if they'd be open to sharing their experience as it was. That framing stays within platform rules and it's also what produces reviews that read as genuine, because they are.
Email Template 3 — Post-Recovery Review Request
Subject: One quick ask
Hi [First Name],
I'm glad we were able to sort things out. If your experience ended somewhere you feel good about, and you're open to it, sharing it as a review would mean a lot to our team.
[Your Google Review Link]
Only if it genuinely reflects how things ended up — no pressure either way.
Thanks,
[Your name]
[Business Name]
Send this 5-7 days after the confirmed resolution. That spacing gives the positive feeling time to settle and removes any sense that the resolution was transactional. For more on timing and sequencing review requests across different customer types, our guide on follow-up sequence timing covers the full range of scenarios. And for the initial review ask sent to customers who never complained, the proven review request email templates guide has templates for every channel.
What This Looks Like in Practice
Two illustrative scenarios show how the same four steps apply across different business types.
A Dental Practice
Say a dental office sends an NPS survey one day after each appointment. A patient gives a 4 out of 10 and notes in the comments that the wait was too long and the hygienist seemed rushed. The office manager responds within two hours (step 1), acknowledges both complaints specifically, and commits to a callback by the next morning. The callback (step 2) covers what caused the scheduling backup that day, offers to rebook the patient at the first available opening with no charge for the next cleaning, and explains that the schedule was adjusted going forward. Four days later, the patient gets a short check-in email (step 3) asking if the follow-up was useful. The patient responds yes. Seven days after that, the office sends the review request (step 4).
The review that comes back acknowledges the initial wait but specifically mentions how quickly and genuinely the office handled it. That kind of review — one that reflects both a problem and a real recovery — is often more persuasive to prospective patients than a string of perfect 5-stars from people who never had an issue. It reads as credible because it is.
A Home Services Company
An HVAC company's technician arrives three hours outside the promised service window. The customer scores the company a 5 and doesn't elaborate. The office reaches out that afternoon (step 1), references the scheduling delay directly, apologizes without hedging, and offers to apply the diagnostic fee as a credit on the next service call (step 2). The customer replies the next day saying that's fair. The check-in (step 3) five days later confirms satisfaction. The review request follows (step 4).
The eventual review mentions the scheduling problem and how it was handled. A reader looking for an HVAC company sees a business that runs late sometimes but makes it right when they do. That's a realistic, trustworthy picture.
When a Detractor Won't Engage
Not every detractor will respond to your outreach. Some won't open the email. Some will read it and say nothing. A few will reply curtly and disengage.
The practical threshold: two outreach attempts separated by at least four days. After that, further contact crosses into unwanted persistence, and persistent contact from a business that already frustrated you is exactly the kind of thing that produces a negative review where there wasn't one before.
A non-responding detractor should not receive a review request. The reasoning is simple: there's no basis to assume the situation resolved itself just because you sent a resolution email. Asking someone who never acknowledged your follow-up to leave a public review is the exact kind of shortcut that produces reviews customers later flag as suspicious — or worse, prompts a second, angrier response.
What you can do is note them in your CRM for a natural re-engagement opportunity. If they come back and have a positive next experience, that moment is a legitimate foundation to rebuild from. Some detractors are simply done. Releasing them without a review request is the right call and not a failure of the process.
Building This Into Your Ongoing NPS Workflow
The four steps only work reliably when they're a process, not a project. Handled ad hoc, they get inconsistent attention and the critical timing windows get missed.
A basic detractor queue needs three things. First, a reliable way for your NPS tool to surface 0-6 responses in real time — most NPS platforms (Qualtrics, Medallia, Delighted, or a simple post-service email survey) can flag and route these automatically. Second, a single named owner for each detractor response, whether that's a customer success rep, a manager, or the business owner directly. Third, a tracking mechanism — even a shared spreadsheet with status fields works — so nothing slips through after step 1.
The status fields that matter: initial contact sent, resolution confirmed internally, check-in sent, check-in response received, review request sent. Those five fields tell you exactly where each detractor is in the sequence at any given time.
When a detractor reaches the review-request stage, ReviewGen.AI's Review Reply Generator helps you handle the language of each outreach carefully — particularly for step 4, where the phrasing needs to stay within platform guidelines while still feeling human. For customers who have already posted public reviews and need a response, the full library of review response templates covers both negative and positive replies at each stage of the customer relationship.
The whole system works only when the steps stay in their sequence. The review ask is at the end for a reason: a review earned before genuine recovery is hollow. A review earned after it is one of the most credible things on your profile.
ReviewGen.AI Editorial Team
We help local businesses collect and manage online reviews. This guide reflects patterns we see across the businesses we work with — particularly around what separates review programs that generate credible feedback from ones that produce nothing useful.
Frequently Asked Questions
How long does it take to turn an NPS detractor into a promoter?
The shortest realistic timeline is around two weeks. Steps 1 and 2 happen within the first 3-4 days. The follow-up check-in comes at day 7-8, and if the customer confirms the issue is resolved, the review request follows at day 12-14. Rushing any step reduces the credibility of the recovery.
Should I ask every resolved detractor for a review?
No. Only ask when the customer explicitly confirms (in step 3) that the issue was resolved. If a detractor never responds to your outreach, skip the review ask. Asking a customer who never acknowledged your resolution for a public review is the shortcut that produces suspicious-looking feedback.
Is it ethical or legal to ask a former detractor for a review?
Yes, with clear guardrails. The FTC's Endorsement Guides (16 CFR Part 255) permit review requests but prohibit offering incentives without disclosure. Google's and Yelp's policies similarly prohibit incentivized or directed reviews. Asking someone who genuinely felt their issue was resolved is legitimate. Telling them what score to leave is not.
What NPS score defines a detractor?
Any score from 0 to 6 on a standard Net Promoter Survey. The framework was developed by Fred Reichheld at Bain & Company and published in the Harvard Business Review in 2003. Detractors score 0-6, passives score 7-8, and promoters score 9-10.
What if a detractor already left a public 1-star review?
This framework applies to detractors identified through private NPS surveys before they post publicly. If someone has already left a 1-star review, the approach is different — the public response comes first, and the resolution attempt happens in a more visible context. Our guide on responding to negative reviews covers that workflow.