A useful customer satisfaction survey is short enough to finish, specific enough to diagnose an experience, and structured well enough to guide follow-up. This reusable customer satisfaction survey template covers CSAT, NPS, effort, open-ended feedback, product or service details, and service recovery so you can adapt the right questions to each customer touchpoint.
Overview
Start with the decision you want the survey to support. A post-purchase survey may help you improve checkout, delivery, or product quality. A support survey may focus on resolution, clarity, and agent helpfulness. A product survey may explore usability and missing features. The questions should follow that purpose rather than attempting to measure every part of the customer relationship at once.
Most customer feedback surveys work best with one primary rating question, a small number of diagnostic questions, and one optional open-text prompt. Longer surveys can be appropriate for structured research, but they should explain why the extra detail is necessary and make the expected completion time clear.
Core customer satisfaction survey template
- Overall satisfaction: “How satisfied were you with your overall experience?” Use a clearly labeled 1–5 or 1–7 scale, from very dissatisfied to very satisfied.
- Recommendation: “How likely are you to recommend [company, product, or service] to a friend or colleague?” Use the familiar 0–10 NPS format if relationship or loyalty is the goal.
- Effort: “How easy was it to complete [task]?” Use a consistent scale such as very difficult to very easy.
- Specific outcome: “Did [product or service] meet your expectations?” Offer an appropriate response set, such as exceeded expectations, met expectations, or fell short.
- Open feedback: “What is the main reason for your rating?” Keep this prompt neutral and allow enough space for a useful answer.
- Improvement prompt: “What is one change that would improve your experience?” This encourages actionable suggestions without asking the customer to solve every problem.
Replace bracketed text with the exact product, interaction, or task being evaluated. Avoid combining unrelated experiences in one question. For example, “How satisfied were you with our product, delivery, and support?” produces a rating that is difficult to interpret because a customer may feel differently about each part.
Checklist by scenario
Post-purchase survey template
Send this survey after the customer has had a reasonable opportunity to receive or use the purchase. Keep the questions tied to that transaction:
- How satisfied were you with the purchasing experience?
- How easy was it to find the information you needed?
- How satisfied were you with the ordering and delivery process?
- Did the product meet your expectations?
- What could we improve about this purchase?
If the product requires setup or ongoing use, consider sending a second, separate survey later. Asking about expectations immediately and asking about real-world usefulness later are different research tasks.
Customer support CSAT survey questions
Send these questions soon after a support interaction is marked complete, while the details are still clear:
- How satisfied were you with the support you received?
- Was your issue resolved?
- How easy was it to get the help you needed?
- How clear was the explanation or solution?
- What could we have done differently?
Include a “not applicable” option when a question may not fit every interaction. For instance, a customer may not be able to judge resolution if the case remains open. Do not treat unanswered or inapplicable responses as dissatisfied responses.
Product or feature feedback survey
Use this version when you need to understand adoption and usability rather than only general satisfaction:
- How often do you use [feature]?
- How easy is it to complete [specific task]?
- How valuable is [feature] to your work or goals?
- What, if anything, makes this feature difficult to use?
- Which improvement would be most valuable to you?
Ask about observed behavior before asking for preferences. “How often did you use this feature?” is generally easier to interpret than “Do you like this feature?” because it separates usage from opinion.
Relationship survey with an NPS question
An NPS survey template can begin with the 0–10 recommendation question and then ask:
- What is the primary reason for your score?
- What could we do to improve your experience?
- Which area should we prioritize: product quality, support, value, ease of use, or something else?
Use NPS when you want a broad relationship or loyalty signal. Do not substitute it for a task-specific CSAT or effort question when the goal is to improve a particular interaction. A customer can recommend a company while still finding one support process difficult.
Service-recovery follow-up
When a customer gives a low rating or reports an unresolved issue, ask for permission to follow up and collect only the information needed by the responsible team:
- Would you like someone to contact you about this experience?
- What would a satisfactory resolution look like?
- What is the best approved channel and time for follow-up?
Route these responses to a defined owner rather than promising personal contact unless your team can fulfill that promise. For a broader workflow, review guidance on how to analyze survey responses.
What to double-check
Choose one scale and label it clearly
A 1–5 scale is compact and familiar; a 1–7 scale offers more room for distinction. Either can work if the endpoints, direction, and meaning are clear. Do not switch from “very dissatisfied to very satisfied” to “poor to excellent” halfway through a survey unless the change is intentional and explained. For an NPS question, keep the 0–10 numbering and label the relevant ends.
Keep the direction consistent where possible. If higher numbers mean more satisfaction in one question but more difficulty in the next, add clear labels and account for the difference during analysis.
Use neutral, single-purpose wording
Avoid leading questions such as “How helpful was our excellent support team?” Avoid double-barreled questions such as “How satisfied were you with the speed and quality of delivery?” Split them into separate questions if both dimensions matter. Define unfamiliar terms and refer to a specific time period, interaction, or product version.
Make the survey accessible and privacy-conscious
Use readable text, sufficient contrast, keyboard-friendly controls, descriptive labels, and a logical order. Do not rely on color alone to communicate meaning. Test the survey on a phone as well as a desktop device, particularly if customers will access it through a QR code or email.
Explain why feedback is being collected, what is optional, and how contact details will be used when you request them. Collect only information needed for the stated purpose. If responses may contain personal or sensitive information, review your organization’s consent, retention, access, and regional privacy requirements before launch.
Plan the analysis before publishing
Decide how you will report ratings, handle “not applicable” answers, compare channels, and review open-ended comments. A simple plan might group results by product, support queue, customer segment, or survey channel while avoiding comparisons based on very small or visibly different groups. For text responses, create a small coding framework for recurring themes and record representative comments without exposing unnecessary personal details.
Common mistakes
- Asking too many questions: Remove questions that will not change a decision. A shorter survey with a clear purpose is often easier to complete and analyze.
- Mixing timeframes: Do not ask about “your recent experience” when some respondents may be thinking about different transactions. Include a date, order, case, or feature where relevant.
- Forcing an answer: Provide “not applicable,” “not sure,” or “prefer not to answer” where those choices are legitimate. Forced guesses weaken the data.
- Using satisfaction as a diagnosis: A low CSAT score identifies a problem but does not explain its cause. Pair it with an open-text question or a focused diagnostic question.
- Ignoring negative feedback: A survey should connect to an owner, priority rule, and response process. Otherwise, collecting complaints can increase frustration rather than improve the experience.
- Changing the instrument without a record: Keep the wording, scale, audience, channel, and launch date for each version. This makes later comparisons more meaningful.
- Overpromising confidentiality or follow-up: State only what your process can support, and separate anonymous feedback from contact-request data when appropriate.
When to revisit
Review this customer satisfaction survey template before each seasonal planning cycle, product release, major service change, or support-workflow update. Recheck the survey whenever the customer journey changes: a new checkout flow, pricing model, delivery process, product interface, or contact channel can make old questions less relevant.
Set a regular review point to examine completion, missing answers, rating distributions, recurring themes, and the percentage of low ratings that receive an appropriate response. Compare versions carefully when wording or scales change. If you distribute surveys through a QR code, email, app, or point-of-service screen, test each route again after a tool or workflow change; the link, form behavior, permissions, and mobile layout should all be verified.
Before your next launch, use this final checklist:
- Write the decision the survey will inform.
- Select one primary measure: CSAT, NPS, effort, or another clearly defined outcome.
- Add only the diagnostic and open-ended questions needed for that decision.
- Check wording, scale labels, accessibility, consent language, and mobile presentation.
- Define who reviews low ratings, how quickly, and what information they receive.
- Save the final questionnaire and launch details so future results can be compared responsibly.
When distribution is the main challenge, pair this checklist with a QR-code survey workflow. When response levels need improvement, review practical guidance on survey response-rate benchmarks and adjust the audience, timing, invitation, or incentive rather than adding more questions.