A customer satisfaction survey asks customers to rate one specific experience, usually on a 1 to 5 scale, and to explain their score. The strongest version has one rating question such as “How satisfied were you with this support conversation?” and one optional open question such as “What is the main reason for your score?”
Customer satisfaction surveys help you understand whether users are happy with a specific experience and why. For SaaS teams, they are especially useful after support conversations, onboarding steps, feature launches, and other moments where a customer forms an opinion quickly.
The best surveys are not long forms that try to answer every question at once. They are short, timed well, and connected to a workflow where someone will review and act on the responses.
Gleap’s customer feedback surveys make it possible to ask customers for feedback directly inside your app or website, while the context is still fresh.
Customer Satisfaction Survey Questions to Use
Pick one rating question for the experience you want to measure and add one open follow-up.
Support (CSAT)
- How satisfied were you with this support conversation?
- Did we solve your problem today?
- How satisfied were you with the speed of our reply?
Product and onboarding (CES)
- How easy was it to complete [task]?
- How easy was it to set up [product]?
- Did you find what you were looking for?
Relationship (NPS)
- How likely are you to recommend [product] to a friend or colleague?
- How would you feel if you could no longer use [product]?
Features and documentation
- How useful is [feature] for your work?
- Did this help article answer your question?
Open follow-ups
- What is the main reason for your score?
- What is one thing we could do better?
- What almost stopped you from completing [task]?
Best Practice 1: Keep the Survey Short
Most satisfaction surveys should start with one rating question and one optional open-text question.
For example:
- “How satisfied were you with this support experience?”
- “What could we have done better?”
Short surveys respect the customer’s time and usually produce clearer responses. If you need a longer research survey, explain why and send it to a smaller, relevant audience.
Best Practice 2: Ask One Thing at a Time
Avoid combining multiple ideas in one question. “How satisfied are you with our support and product quality?” is hard to answer because the customer may feel differently about each.
Ask about the exact experience you want to measure:
- Support resolution.
- Onboarding setup.
- A new feature.
- Documentation usefulness.
- Overall product satisfaction.
This makes the response easier to interpret and act on.
Best Practice 3: Avoid Loaded Questions
Loaded questions push users toward the answer you want. They may feel friendly, but they weaken the data.
Instead of “How much did you love our new dashboard?” ask “How satisfied are you with the new dashboard?”
Neutral wording gives customers permission to be honest, which is the whole point of the survey.
Best Practice 4: Keep Rating Scales Consistent
If a score of 5 means “very satisfied” in one question, do not make it mean “very difficult” in the next. Inconsistent scales create confusion and unreliable data.
Use the same direction and labels throughout a survey. If you track CSAT, NPS, and CES together, explain what each scale means and keep the question format familiar. For a comparison of those metrics, see CSAT vs NPS vs CES.
Best Practice 5: Include Open Text Feedback
Ratings tell you where to look. Comments tell you what to fix.
Always give users a chance to explain their score, but make the follow-up optional when possible. Required long-text fields can reduce completion and may frustrate users who only wanted to give a quick rating.
Open responses are also useful for identifying knowledge gaps. If many users say they could not find an answer, the fix may be a clearer knowledge base article rather than a product change.
Best Practice 6: Time the Survey Carefully
Survey timing should match the question.
Send CSAT right after a support ticket is resolved. Ask about onboarding after the user completes the setup journey. Ask broader relationship questions like NPS after the user has had enough time to experience value.
Poor timing creates poor answers. If you ask too early, customers may not know yet. If you ask too late, they may not remember the details.
- TriggerEvent
onboarding_completed - AudienceSigned up more than 7 days ago
- PagesURL contains
/app/ - How oftenSent once
Best Practice 7: Close the Loop
Collecting survey responses is only half the work of closing the feedback loop. Assign an owner to review results, tag themes, follow up on important comments, and share patterns with product, support, or customer success.
When a customer leaves a frustrated comment, a quick response through live chat or email can turn a weak experience into a recovery moment.
Simple Customer Satisfaction Survey Template
Use this when you want fast feedback after a support or product experience.
Question 1: How satisfied were you with [experience]?
Scale: 1 = very dissatisfied, 5 = very satisfied
Question 2: What is the main reason for your score?
Open text, optional
Question 3: Can we contact you about your feedback?
Yes or no
This template is simple enough for frequent use and specific enough to guide follow-up.
Product Experience Survey Template
Use this after a customer tries a new workflow or feature.
Question 1: How easy was it to complete [task]?
Scale: very difficult to very easy
Question 2: What, if anything, made the task harder than expected?
Open text, optional
Question 3: What would make this experience better?
Open text, optional
This template is closer to CES than CSAT and is useful when your goal is reducing friction.
Final Thoughts
Customer satisfaction surveys should help your team make better decisions, not only produce a score. Keep them short, ask neutral questions, use consistent scales, and review the comments behind the ratings.
For a complete measurement system, connect satisfaction surveys to the broader customer experience metrics your team uses to understand retention, effort, loyalty, and product quality.
