Ready-to-Use Templates
Copy these templates and customize them for your needs. Each includes HTML and plain text versions.
Quick question about {{productName}}, {{firstName}}
One click, takes 10 seconds.
We hear you, {{firstName}} - how can we do better?
Your feedback matters to us.
Thanks for the love, {{firstName}} - one more thing?
Would you share that feedback publicly?
How's {{featureName}} working for you?
2-minute survey about your experience.
What would make {{productName}} a 10 for you?
You're close to loving us. Help us get there.
Your first month with {{productName}} - how's it going?
Quick check-in after 30 days.
How did we handle your request, {{firstName}}?
Rate your support experience.
{{firstName}}, we fixed it
You asked, we built it.
Know someone who'd love {{productName}}?
Share the love - and earn a reward.
{{firstName}}, your year with {{productName}} in review
Help us plan what we build next year.
Still want your opinion, {{firstName}}
One click. That's all it takes.
What you told us - and what we're doing about it
Your feedback in action.
Best Practices
Keep surveys to one question. Response rates drop with every additional question.
Follow up differently based on the score - detractors need help, promoters need a channel.
Send from a real person and make replies easy (no survey links for open-ended feedback).
Wait 90 days between NPS surveys to avoid survey fatigue.
Common Mistakes
Sending NPS surveys too frequently - quarterly is the maximum.
Not following up on responses - collecting data without acting on it wastes trust.
Using the NPS score alone without the qualitative follow-up.
Surveying customers during known issues or outages.
Subject Line Examples
Timing & Performance
Personalization Tips
One Question Gets More Answers
NPS works because it's one question with one click. The moment you add a second question, response rates drop by half. Collect the score first, then follow up with the qualitative question separately.
Detractors Are a Gift
Customers who give low scores and explain why are giving you a roadmap. Every piece of critical feedback is a product improvement waiting to happen. Follow up personally within 48 hours.
Turn Promoters Into Advocates
A customer who scores 9-10 is your most powerful marketing channel. Don't waste the moment - ask for a public review, a testimonial, or a referral while the positive feeling is fresh.
How to adapt SaaS NPS & Customer Feedback Templates without flattening them
A good SaaS NPS & Customer Feedback Templates draft answers one practical question fast: what happened, why now, and what should the reader do? NPS survey and customer feedback email templates for SaaS. Measure satisfaction, identify promoters, gather product insights, and close the feedback loop with your customers. Start with NPS Survey only when that question matches core nps question - how likely to recommend.
Start by mapping the templates to real customer moments. Use NPS Survey when the reader needs core nps question - how likely to recommend, and rewrite the first paragraph around the exact trigger that made the email relevant. Use Detractor Follow-Up when follow up with customers who scored 0-6 is the real job, not because the template sounds polished. Promoter Thank You should carry the strongest practical detail. Feature Feedback Request can usually be shorter if the reader already understands the context, while Passive Follow-Up should only exist if it gives the reader a genuinely different reason to act.
The most important triggers on this page are customer reaches 30/60/90 day milestone, after major feature usage or project completion, quarterly satisfaction check, after support ticket resolution. Use those as the opening context instead of starting with a generic greeting. Write with SaaS companies tracking customer health, Products with customer success teams, B2B software seeking product feedback in mind, because those audiences have different tolerance for detail, urgency, and hand-holding. For this category, prioritize make the context specific, keep one clear CTA, and remove claims the reader cannot verify. The core problem is that most saas companies have no idea how their customers actually feel until they cancel. nps and feedback emails close this gap by measuring satisfaction before it becomes churn. Timing matters here too: Send NPS surveys 30 days after signup, then quarterly. Post-interaction surveys within 24 hours of the event. Avoid Mondays and Fridays.
Use merge fields like {{productName}}, {{firstName}}, {{surveyUrl}}, {{companyAddress}}, {{recentImprovement}}, {{senderName}} only where they make the email more useful. If {{productName}} or {{firstName}} can be missing, write the sentence so it still reads naturally without the field. The search intent behind "nps email templates", "customer feedback email", "saas survey email", "nps survey template" is practical. Readers want copy they can adapt quickly, so keep the on-page guidance direct and keep the sent email free of SEO phrasing.
| Template | Use it when | Customization that improves it |
|---|---|---|
| NPS Survey | Core NPS question - how likely to recommend | Open with the real trigger behind core nps question - how likely to recommend. |
| Detractor Follow-Up | Follow up with customers who scored 0-6 | Add one detail that proves this is not a batch blast. |
| Promoter Thank You | Thank promoters (9-10) and ask for a review | Make the CTA match the reader's current task. |
| Feature Feedback Request | Targeted feedback on a specific feature or workflow | Cut background copy if the reader already knows the situation. |
| Passive Follow-Up | Follow up with passives (7-8) to understand what's holding them back | Send a follow-up only if silence tells you something useful. |
The benefit language should stay concrete: Identify promoters who will refer others; Catch detractors before they cancel; Gather specific product improvement ideas. If a draft cannot support one of those outcomes, it probably needs a sharper CTA or a stronger proof point. Use the best-practice list as a QA checklist: Keep surveys to one question. Response rates drop with every additional question; Follow up differently based on the score - detractors need help, promoters need a channel; Send from a real person and make replies easy (no survey links for open-ended feedback). Those checks are more useful than another round of generic polishing. The easiest ways to weaken these emails are sending nps surveys too frequently - quarterly is the maximum.; not following up on responses - collecting data without acting on it wastes trust.; using the nps score alone without the qualitative follow-up.. Fix those issues before adjusting tone.
The last edit should make the email easier to act on, not more impressive. Cut anything that delays the point of NPS Survey.
For NPS specifically, separate score collection from recovery work. The first email should make the rating effortless, but the follow-up should branch: promoters can be asked for a quote or review, passives need one concrete improvement, and detractors need a real owner, not a generic survey thank-you.
Build Beautiful Email Sequences for Your SaaS
Sequenzy helps SaaS founders create automated email sequences that convert. From onboarding to retention - all in one platform.