NPS Response Writing

Parent: Writing and Documentation · researched 2026-05-29T19:09:48.098Z· 5 sources · 9 concepts · skill nps-response-writing

This skill covers how to write replies to customer feedback collected at scale — NPS verbatim comments, CSAT free-text, post-support survey replies, and public app-store reviews.

Overview

This skill covers how to write replies to customer feedback collected at scale - NPS verbatim comments, CSAT free-text, post-support survey replies, and public app-store reviews. [source]
Three things make these responses different from support replies: [source]
The customer did not ask for help. They volunteered feedback. [source]
The score is the spine. Detractor (0–6), passive (7–8), and promoter (9–10) responses calibrate differently. [source]
Cadence is short. Under 48 hours for detractors, under 72 hours for app-store replies. [source]

1. The thank/acknowledge/route/commit template

Thank - one line, specific to the act of giving feedback, not the score. [source]
Acknowledge - quote or paraphrase the specific point. Proves you read it. [source]
Route - name what happens next internally. Be specific: "I'm sending this to our billing team's weekly review on Thursday" beats "I'll route this to the right team." [source]
Commit - one concrete next step you (the responder) own, with a date or trigger. [source]

3. The "I'll route this to engineering" anti-pattern

"I'll pass this along to the team" signals that the responder has no agency. Replace with: [source]
A named destination: "I'll add this to our March platform-stability review." [source]
A named owner: "Our billing PM, Priya, will see this on Monday." [source]
An explicit decline: "I can't promise this gets prioritized - we're locked on Q2 commitments - but I've logged it under [theme]." [source]

4. Closed-loop response cadence

Detractor first response: within 24–48 hours. [source]
Passive reply: within 1 week. [source]
Promoter reply: within 2 weeks. [source]
App-store reply: within 72 hours. [source]
Loop close-out (confirming resolution back to the customer): within 30 days. [source]

5. When an NPS verbatim becomes a save call

Escalate to a live conversation when any of these appear: [source]
Explicit churn language: "evaluating alternatives," "renewal is up" [source]
A specific named individual who is angry [source]
A claim of broken commitment ("you promised us X") [source]
Compounding issues ("this is the third time…") [source]
Legal/compliance language: "data breach," "GDPR," "lawsuit" [source]

6. The honest-decline reply

Acknowledge the specific point. [source]
State the trade-off plainly: "We deliberately chose X over Y because [reason]." [source]
Offer the closest workaround you can. [source]
Leave the door open: "If this stays a blocker for you, I want to know." [source]

Detractor (NPS 3, verbatim: "Support takes forever and your billing portal is broken")

> Thanks for being direct in the survey - that's more useful to us than a polite 7. [source]
> Two specific things you flagged: support response time, and the billing portal. On support: I pulled your last four tickets and the median first-response was 19 hours, which is outside our SLA for your plan. That's on us. On billing: the portal had a known issue with invoice downloads through last Tuesday; it's fixed now, but you would have hit it. [source]
> I'm doing two things. First, I've flagged your account to our support lead, who will personally route your next three tickets. Second, I'd like 20 minutes with you this week to hear what "fast enough" looks like for your team. [source]
> Tuesday or Thursday afternoon work? [source]

Passive (NPS 8, verbatim: "It's good, just nothing exciting")

> Thanks for the note - "good but not exciting" is genuinely useful for us, more than a 10 with no comment would be. [source]
> If you don't mind a quick question: what would have made it a 9 or 10 for you? One thing, off the top of your head, is enough. [source]

App-store 1-star reply (consumer iOS)

> Sorry the import flow blocked you on a 200MB file - that's a real bug, not the experience we want. We shipped a fix in v4.7.2 last week that raises the limit to 2GB and adds a progress indicator. If it's still failing for you, email support@[app].com. [source]

Anti-Patterns

The form-letter thank-you. "Thank you for your valuable feedback." Reads as bot output. [source]
The unprompted apology. Saying "I'm sorry" to a passive (NPS 8) signals you read them as a detractor. [source]
The route-to-the-void. "I've passed this along to the team" with no named destination. [source]
The re-survey ask before resolution. Asking a detractor to re-rate before you have fixed anything. [source]
The marketing voice. "we're committed to delivering delight" to a frustrated customer. [source]
The upsell smuggled into a promoter reply. [source]

References

Introducing the Net Promoter System | Bain & Company [source]
Net Promoter 3.0 | Bain & Company [source]
How to respond to app store reviews | MobileAction [source]

Children

No children recorded.

← the whole tree · 3D view· how to read this page