Run an NPS survey and close the loop on every response

Net Promoter Score asks customers one question: how likely are they to recommend you, on a scale from 0 to 10. Many companies collect the score, put it on a dashboard and stop there. Closing the loop means someone reads every response, replies to the customer and acts on what they said. It fits any business with enough customers to survey and a team that can follow up within a few days.

Why it works

An unhappy customer who bothers to answer a survey is giving you a final warning. A quick, personal reply shows them they were heard, and often uncovers a fixable problem such as a billing error or a missing setting. Many will stay once it is solved. Without a reply, the survey confirms their belief that nobody is listening.

Promoters are the other half. A customer who just gave you a 9 or 10 is in the right frame of mind to leave a review, join a case study or refer a friend. Asking at that moment costs nothing and turns goodwill into growth.

How to do it

1. Add a follow-up question. After the score, ask “What is the main reason for your score?” in a free-text box. The reason is more useful than the number.
2. Pick the moment and audience. Survey customers who have used the product long enough to judge it. In B2B, include users and the account’s decision maker. In D2C, send after delivery and first use.
3. Route responses automatically. Send detractors (0 to 6) to the account owner or a senior support agent, passives (7 and 8) to customer success, and promoters (9 and 10) to a marketing queue.
4. Reply to every detractor quickly. Aim for a personal reply within two working days. Thank them, restate their issue in your words, and propose a fix or a call.
5. Ask passives one question. A short note asking “What would make this a 10?” often surfaces the gap between fine and great.
6. Make one ask of promoters. Ask for a review on a named site, a referral, or a quote, and pick only one per person.
7. Tag every reason. Tag comments with themes such as onboarding, price, bugs, speed or support. Review the counts monthly with product and leadership.
8. Report back. When you fix a common complaint, tell the customers who raised it. A short email naming the fix can win back a detractor for good.

Example

A hypothetical B2B HR platform surveys admins every six months. Responses flow into its CRM, where each detractor creates a task for the account’s customer success manager. One admin scores a 3 and writes that payroll exports keep failing. The manager replies the next morning, books a call, finds a misconfigured integration and fixes it that week. In the monthly review, the team sees the same export complaint in many detractor comments, prioritises a fix, and emails everyone who mentioned it once it ships.

A hypothetical D2C coffee subscription runs the same process at a smaller scale. Detractors get a reply from a support lead offering a different roast or a pause option. Promoters get a link to leave a review on the product page.

Metrics to track

• Response coverage. The share of detractor and passive responses that got a personal reply. Aim for all of them, and track time to first reply.
• Retention of detractors who got a reply. Compare renewal or repeat-purchase rates for detractors you followed up with against those from before the process existed.
• Theme counts over time. The number of comments per tag each month. A theme should shrink after you ship a fix for it.
• Promoter asks converted. Reviews, referrals or case studies obtained from promoter follow-ups.
• Score trend by segment. NPS by plan, cohort or region, watched over several survey rounds.

When it backfires

• Collecting without replying. Surveying people and then ignoring them makes detractors angrier than not asking at all.
• Defensive replies. Arguing with a customer about their score, or explaining why they are wrong, ends the conversation.
• Gaming the score. Asking customers to “please give us a 10” or surveying only happy accounts makes the number useless.
• Over-surveying. Sending the survey after every interaction leads to fatigue and lower response rates.
• Themes that go nowhere. If the same complaint tops the list every month and nothing changes, the team stops reading comments.

Questions people ask

Who should reply to detractors?

In B2B, the account owner or customer success manager should reply, because they can act on the account. In D2C, a senior support agent with the authority to offer a refund or replacement works well.

How often should we send the survey?

Survey each customer at most once or twice a year, and never in their first days. Many teams also send it after a key moment, such as 30 days after purchase or before a renewal.

Does the score itself matter?

The trend over time is useful. The written reasons and what you do about them matter more, because that is what changes retention.