NPS Response Writing
Parent: Writing and Documentation · Published reference · snapshot 2026-09-08 · skill content-and-marketing-writing/references/nps-response-writing.md
↓ Facts as markdownall context files
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.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
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. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#overview]
- Three things make these responses different from support replies: [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#overview]
- The customer did not ask for help. They volunteered feedback. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#overview]
- The score is the spine. Detractor (0–6), passive (7–8), and promoter (9–10) responses calibrate differently. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#overview]
- Cadence is short. Under 48 hours for detractors, under 72 hours for app-store replies. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#overview]
1. The thank/acknowledge/route/commit template
- Thank - one line, specific to the act of giving feedback, not the score. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#1-the-thankacknowledgeroutecommit-template]
- Acknowledge - quote or paraphrase the specific point. Proves you read it. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#1-the-thankacknowledgeroutecommit-template]
- 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." [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#1-the-thankacknowledgeroutecommit-template]
- Commit - one concrete next step you (the responder) own, with a date or trigger. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#1-the-thankacknowledgeroutecommit-template]
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: [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#3-the-ill-route-this-to-engineering-anti-pattern]
- A named destination: "I'll add this to our March platform-stability review." [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#3-the-ill-route-this-to-engineering-anti-pattern]
- A named owner: "Our billing PM, Priya, will see this on Monday." [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#3-the-ill-route-this-to-engineering-anti-pattern]
- An explicit decline: "I can't promise this gets prioritized - we're locked on Q2 commitments - but I've logged it under [theme]." [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#3-the-ill-route-this-to-engineering-anti-pattern]
4. Closed-loop response cadence
- Detractor first response: within 24–48 hours. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#4-closed-loop-response-cadence]
- Passive reply: within 1 week. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#4-closed-loop-response-cadence]
- Promoter reply: within 2 weeks. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#4-closed-loop-response-cadence]
- App-store reply: within 72 hours. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#4-closed-loop-response-cadence]
- Loop close-out (confirming resolution back to the customer): within 30 days. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#4-closed-loop-response-cadence]
5. When an NPS verbatim becomes a save call
- Escalate to a live conversation when any of these appear: [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#5-when-an-nps-verbatim-becomes-a-save-call]
- Explicit churn language: "evaluating alternatives," "renewal is up" [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#5-when-an-nps-verbatim-becomes-a-save-call]
- A specific named individual who is angry [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#5-when-an-nps-verbatim-becomes-a-save-call]
- A claim of broken commitment ("you promised us X") [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#5-when-an-nps-verbatim-becomes-a-save-call]
- Compounding issues ("this is the third time…") [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#5-when-an-nps-verbatim-becomes-a-save-call]
- Legal/compliance language: "data breach," "GDPR," "lawsuit" [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#5-when-an-nps-verbatim-becomes-a-save-call]
6. The honest-decline reply
- Acknowledge the specific point. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#6-the-honest-decline-reply]
- State the trade-off plainly: "We deliberately chose X over Y because [reason]." [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#6-the-honest-decline-reply]
- Offer the closest workaround you can. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#6-the-honest-decline-reply]
- Leave the door open: "If this stays a blocker for you, I want to know." [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#6-the-honest-decline-reply]
Detractor (NPS 3, verbatim: "Support takes forever and your billing portal is broken")
- > Hi Sarah, > > Thanks for being direct in the survey - that's more useful to us than a polite 7. > > 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. > > 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. > > Tuesday or Thursday afternoon work? [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#detractor-nps-3-verbatim-support-takes-forever-and-your-billing-portal-is-broken]
Passive (NPS 8, verbatim: "It's good, just nothing exciting")
- > Hi Alex, > > Thanks for the note - "good but not exciting" is genuinely useful for us, more than a 10 with no comment would be. > > 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. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#passive-nps-8-verbatim-its-good-just-nothing-exciting]
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. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#app-store-1-star-reply-consumer-ios]
Anti-Patterns
- The form-letter thank-you. "Thank you for your valuable feedback." Reads as bot output. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#anti-patterns]
- The unprompted apology. Saying "I'm sorry" to a passive (NPS 8) signals you read them as a detractor. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#anti-patterns]
- The route-to-the-void. "I've passed this along to the team" with no named destination. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#anti-patterns]
- The re-survey ask before resolution. Asking a detractor to re-rate before you have fixed anything. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#anti-patterns]
- The marketing voice. "we're committed to delivering delight" to a frustrated customer. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#anti-patterns]
- The upsell smuggled into a promoter reply. [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#anti-patterns]
References
- Introducing the Net Promoter System | Bain & Company [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#references]
- Net Promoter 3.0 | Bain & Company [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#references]
- How to respond to app store reviews | MobileAction [archived source: https://llms-explorer.com/sources/mdb-context-hub/nps-response-writing/#references]
Where this helps
- A detractor's NPS verbatim mentions "evaluating alternatives" or a broken promise, and someone needs to decide within hours whether the reply escalates to a live save call or stays a written response. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A support or CS team's app-store rating has cratered and they need a reply that acknowledges a specific bug rather than a generic "thanks for your feedback" line. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A CSAT/NPS program has a backlog of passive (7-8) scores with short verbatims, and the team needs a low-effort, non-apologetic reply that still closes the loop. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Leadership wants proof that customer feedback drives action, and a response needs to name a specific internal destination, owner, or date instead of a vague "I'll pass this along." [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
How to apply this
- Build a decision checklist your team runs against every incoming detractor verbatim, checking for the five escalation triggers (churn language, a named angry individual, a broken-promise claim, compounding issues, legal/compliance language) before drafting a written reply. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Draft response templates per score band using the thank/acknowledge/route/commit structure, then review real replies against it to catch form-letter phrasing before it ships. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Set and track the closed-loop cadence (24-48h detractor, 1 week passive, 2 weeks promoter, 72h app-store, 30-day loop close-out) as an SLA dashboard so replies don't silently slip past the window that makes them credible. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Practice writing the honest-decline reply for a real unmet feature request — state the trade-off plainly, offer the closest workaround, and leave the door open — instead of defaulting to a vague apology. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Common mistakes
- Sending an unprompted apology to a passive (NPS 7-8) respondent — it signals you read a mildly positive score as a complaint. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Asking a detractor to re-rate the survey before anything has actually been fixed — the ask before resolution reads as gaming the score rather than closing the loop. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Naming "the team" instead of a specific destination, owner, or date when routing feedback internally — "I'll pass this along" reads as having no agency. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Smuggling an upsell into a reply to a promoter (NPS 9-10) — it turns a goodwill touchpoint into a sales pitch at the exact moment the customer is least expecting one. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Limitations
- The escalation triggers are pattern-matching heuristics on the verbatim text — they can miss a genuine risk phrased mildly, or over-trigger on hyperbole that isn't actually a save-call situation. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- The closed-loop cadence assumes a team has the operational capacity to track and hit per-score-band SLAs — without a routing and tracking system behind it, the cadence is aspirational rather than enforced. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- The honest-decline reply only works when the trade-off being stated is a real, deliberate product decision — using it to paper over an unplanned gap undercuts the credibility it depends on. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A named owner and date in a routed reply is a commitment the internal team then has to honor — writing it without confirming the named person will actually follow through creates a promise the response writer doesn't control. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Children
- No children recorded.