A customer satisfaction survey template is a reusable set of questions for learning how customers rate an interaction, product, or service. Use the blank template below to collect a simple overall rating, identify what went well or poorly, and invite specific suggestions you can act on.
What a customer satisfaction survey measures
Customer satisfaction is a customer’s reported evaluation of an experience. A survey records that opinion at a particular point in time; it does not, by itself, explain every reason behind the rating or represent every customer’s view. The most useful surveys therefore pair a focused rating question with an optional opportunity to explain the response.
The question should match the experience you want to understand. After a support conversation, for example, ask about that conversation rather than asking customers to judge the entire company. After a purchase, ask about the buying experience or the product, depending on which team will use the results. A clear subject makes answers easier to interpret and compare.
These surveys can help an organization spot recurring friction, recognize experiences customers value, and decide which issues merit closer attention. They are a feedback tool, not a substitute for support records, product research, or direct conversations. A rating without context can show that someone was dissatisfied but may not reveal whether the cause was a delay, unclear instructions, a product issue, or something else.
When to send the survey
Send a survey close enough to an experience that the customer can recall it, but not so frequently that requests become a nuisance. The right timing depends on the interaction and on how quickly a customer can meaningfully assess it. A brief service interaction may be evaluated soon afterward; a product may need to be used before a customer can give informed feedback about it.
Choose one event or period as the survey’s reference point and state it plainly. If the question concerns a recent support interaction, say so. If it concerns a product used over the past month, define that period. Ambiguous timing can lead different respondents to think about different experiences, making the results harder to compare.
Consider the full customer journey, not just the moment when it is easiest to send a message. A person who has just reported an unresolved issue may not be ready to assess the final outcome. In that situation, a survey after resolution may be more relevant. For ongoing relationships, a periodic survey can capture a broader view, but avoid repeatedly asking the same people without a clear reason.
How to choose useful questions
Keep the survey short and specific. Every question should help answer a real decision or provide context for interpreting the rating. A compact form is easier to complete and less likely to ask customers for information the organization will not use. Avoid combining several topics in one question: “How satisfied were you with the speed and helpfulness of the service?” asks about two different things, and a customer may have different opinions about each.
A practical survey often includes an overall satisfaction question, one or two questions about relevant details, and an optional open-ended prompt. Use a consistent response scale and label its endpoints. For example, a five-point scale can run from “Very dissatisfied” to “Very satisfied,” with a neutral middle choice. Explain the scale in the form so respondents do not have to guess what each number means.
Questions should be neutral and understandable without internal jargon. “How satisfied were you with the time it took to receive a response?” is more direct than a leading question such as “How pleased were you with our fast response?” If customers can choose “Not applicable,” include it where a question may not fit everyone. Do not treat that answer as a low rating.
Use open text sparingly and make it optional unless a written explanation is essential. An invitation such as “What is one change that would have improved this experience?” is easier to answer than a vague request for general feedback. Do not request sensitive personal details unless there is a clear, appropriate need and a suitable way to handle them.
Customer Satisfaction Survey Template
Copy or print this general-purpose form and tailor the bracketed topic descriptions before sending it. Keep only questions that fit the experience being evaluated. The response fields are intentionally blank.
| Field or question | Response |
|---|---|
| Experience being evaluated | |
| Date or period of experience | |
| Overall, how satisfied were you with this experience? (Very dissatisfied / Dissatisfied / Neither satisfied nor dissatisfied / Satisfied / Very satisfied) | |
| How satisfied were you with [one relevant detail, such as clarity, ease, or response time]? | |
| Was your main need or reason for contact addressed? (Yes / Partly / No / Not applicable) | |
| What went well or could have been better? (Optional) | |
| May we contact you to clarify your feedback? (Yes / No; contact details only if appropriate) |
Fictional sample: In a made-up example, a customer rates a bakery’s online ordering experience “Satisfied,” says the pickup instructions were clear, and suggests adding a visible place to request a later pickup time. This sample illustrates the format only; it is not real customer feedback.
How to adapt the template
Start by naming the decision the survey should inform. If the goal is to improve a delivery process, ask about delivery and the related communication, not unrelated product features. If the goal is to understand help interactions, ask whether the customer’s need was addressed and whether the explanation was clear. A focused purpose helps prevent the form from growing into a general questionnaire.
Next, identify who should answer and which experience counts. For example, a survey about an account-support conversation should go to people who took part in one, rather than to all customers. Decide whether responses should be anonymous or whether follow-up is useful. Explain any request for contact details and make it optional when possible; customers may be less comfortable sharing candid feedback if they do not understand how their information will be used.
Finally, test the wording with a small number of people who resemble the intended respondents. Ask them what they think each question means and whether any answer choices are missing. This is a way to catch confusing language before wider use, not a guarantee that every respondent will interpret a question identically. Make a dated copy when changing questions or scales so later comparisons have context.
Sending the survey and handling responses
Use a channel that makes sense for the interaction, such as a paper form at a service desk or a link provided after an online interaction. State why the person is receiving the request, what experience to think about, and whether a response is optional. If there is a closing date or an expected completion time, describe it accurately. Do not promise confidentiality or anonymity unless the collection process actually supports that promise.
Set practical limits on repeat requests. A customer who has had several interactions in a short period should not necessarily receive a separate survey after every one. Decide whether to invite feedback after selected events, set a quiet period between invitations, or use a periodic sample. The approach should be consistent enough to interpret while respecting customers’ attention.
When responses arrive, restrict access to people who need them and handle any identifying details according to the organization’s applicable privacy practices. Separate contact information from written comments where feasible if follow-up is optional. If feedback describes an urgent service problem, a survey channel should not be presented as a replacement for the normal way to request help.
Reading results and acting on feedback
Begin with the response count and the question wording, then summarize ratings in a consistent way. For a five-point satisfaction scale, an organization might report the distribution across all five choices or calculate an average, provided it explains the method. An average alone can conceal whether responses cluster at the middle or split between very satisfied and very dissatisfied. Keep “Not applicable” and unanswered questions separate from actual ratings.
Look for patterns by experience type, time period, or other relevant group, but avoid drawing strong conclusions from very small or unrepresentative groups. People who choose to answer may differ from people who do not. A survey can reveal useful signals without proving what all customers think or why a pattern occurred. Compare results only when the questions, scale, audience, and collection method are sufficiently similar.
Read written comments for recurring themes, and preserve the distinction between a direct observation and an interpretation. “The pickup instructions were hard to find” is a comment; “all customers find pickup difficult” is a broader claim that needs more evidence. Where possible, connect themes to operational information or follow up with customers who have agreed to be contacted. Then assign an owner, decide what change is practical, and review whether the issue improves over time.
Common survey problems to avoid
- Too many questions: Remove questions that do not inform a decision. A shorter form is easier to complete and simpler to maintain.
- Leading or double-barreled wording: Ask about one topic at a time and do not imply the preferred answer.
- Unclear scales: Label endpoints, keep the direction consistent, and explain what a number represents.
- Unusable open responses: Ask a focused prompt and make clear that a written answer is optional.
- Overinterpreting a score: A rating describes the response to that question, not necessarily loyalty, future buying behavior, or the cause of dissatisfaction.
- Collecting feedback without follow-through: Decide in advance who will review results and how customers will be told about relevant changes.
A common misconception is that one favorable overall score proves an experience is working well. A high rating can coexist with a specific recurring problem, while a low rating may reflect a circumstance outside the question’s scope. Review the wording, the distribution, the comments, and the context together before deciding what the results mean.
Related measures and alternatives
Customer satisfaction surveys are not the only way to learn about an experience. A brief rating after a particular interaction is useful when the question is about that interaction. A periodic relationship survey asks about the broader customer relationship and should not be treated as interchangeable with a transaction-level rating. A recommendation question measures a different stated response than satisfaction, so its results should be labeled and interpreted separately.
Other useful sources include support conversations, complaints, product-use observations, interviews, and feedback volunteered without a survey prompt. Each has limitations: a conversation may offer detail but involve few people, while a short rating may be easier to summarize but reveal little about causes. Combining sources can give a fuller picture, as long as the organization does not treat one method as proof of what every customer experiences.
Frequently Asked Questions
What should a customer satisfaction survey include?
A clear reference to the experience, one overall satisfaction rating, a small number of relevant follow-up questions, and an optional prompt for comments are a useful starting point. Include answer choices that fit the question and allow “Not applicable” where needed.
How many questions should a customer satisfaction survey have?
There is no single correct number. Include only questions that serve the survey’s purpose, and keep the form as short as practical. A few well-defined questions are often easier to answer and analyze than a long list of loosely related prompts.
What is a good satisfaction rating scale?
A clearly labeled scale with a consistent direction can work well. A five-point scale from “Very dissatisfied” to “Very satisfied” is one common format, but the best choice depends on the audience and how results will be compared. Keep the same scale when comparing results over time.
Should customer satisfaction surveys be anonymous?
That depends on whether follow-up is necessary and how responses will be handled. Anonymous responses may encourage candid feedback, while identified responses can make it possible to resolve an individual issue. Explain the arrangement honestly and avoid collecting identifying information that is not needed.
When should I send a customer satisfaction survey?
Send it after the customer has had enough time to experience the subject of the questions, while the event is still reasonably clear in memory. State which interaction or time period the survey covers, and avoid sending repeated requests without a clear purpose.