"Send customers a feedback survey" is easy advice to give and surprisingly easy to get wrong — the wrong questions at the wrong moment produce a low response rate and data nobody ends up using. Here's how to think about it by stage, with concrete question examples.
Right after a purchase or onboarding
This is a moment-in-time measurement, not a relationship measurement — you want CSAT-style questions, not NPS.
- "How would you rate your overall experience with [the purchase / setup process]?" (star rating)
- "What almost stopped you from completing this?" (open text, optional)
Keep it to two or three questions. This moment has a narrow window — ask too late and you're measuring memory, not experience — and it's usually a small, low-effort ask, so don't pad it with unrelated questions about the broader relationship.
After a support interaction
Same logic as above, plus effort. A support interaction can leave someone satisfied with the outcome while still frustrated by the process (three transfers, repeating the same explanation twice), which is exactly what Customer Effort Score is built to catch.
- "How satisfied were you with how this was resolved?" (star rating)
- "How easy was it to get this resolved?" (Likert agreement: "This was easy to resolve")
We cover the CSAT-vs-CES distinction in more depth in NPS vs. CSAT vs. CES.
Quarterly or after major changes: relationship health
This is where NPS earns its keep — a single trackable number for overall loyalty, measured consistently over time rather than after every interaction.
- "On a scale of 0–10, how likely are you to recommend us to a friend or colleague?"
- "What's the primary reason for your score?" (always pair NPS with this — the number alone doesn't tell you why)
Ongoing: product feedback
Different goal entirely — not "are you happy," but "what should we build or fix next."
- "Which features do you use most frequently?" (multiple choice)
- "What features are you missing that would make this more useful for you?" (open text)
- "How satisfied are you with the product overall?" (Likert)
Our Product Feedback template bundles this exact combination.
Common mistakes
Asking everything in one survey. A single form that tries to cover satisfaction, loyalty, effort, and feature requests all at once is long, unfocused, and gets a lower completion rate than four shorter, purpose-built surveys sent at the right moments.
Sending it at the wrong time. A relationship-health NPS survey sent the day after a bad support ticket will read as noise — you're capturing a bad moment, not the overall relationship. Match the survey to the moment it's actually measuring.
No open-ended follow-up on scale questions. A number without a reason is hard to act on. Every rating or NPS question should have an optional "why" attached.
Ignoring response rate mechanics. The same principles that apply to any survey — keep it short, mobile-friendly, and clearly worth the respondent's time — apply here too. See how to increase survey response rates for the full list.
Anonymity is worth considering here too
Customers are often more candid about frustrations — pricing complaints, a feature they hate, a competitor they're evaluating — if they're not worried the feedback will be tied back to their account in a way that affects how they're treated afterward. Whether to collect identifying information depends on whether you need to follow up individually; if you don't, an anonymous option removes one more reason for a respondent to hold back or skip the survey.
Surveyee has ready-built templates for each stage above — Customer Satisfaction, NPS Survey, and Product Feedback — free to use and adjust, no account required until you're ready to publish and start collecting responses.