Customer satisfaction survey form
A satisfaction survey pairs a score with the reason behind it — two questions that need two fields. A slider gives you a number to average, and open text fields capture the context that explains what the number means. This form collects feedback; it does not score automatically or generate reports. The responses export to CSV for you to read and trend yourself.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
A slider produces real numbers, not text to parse
A satisfaction slider is a real field type, so responses arrive as numbers (0–10) that a spreadsheet can average. Free text produces "8/10", "eight", "very satisfied" — none of which have an average, and parsing them is the opposite of automated feedback.
Ask what went right, even from someone dissatisfied
A required field asking "what went well" ensures dissatisfied customers still name something positive. A form that only asks for complaints loses the signal of what to keep doing — you learn what to fix, but not what to replicate.
No card required.
Customer Satisfaction Survey
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add a slider field for satisfaction on a scale the respondent can understand — 0 to 10 is common, set in both validation and settings.
- Add a required text field asking what went well, so even dissatisfied customers name what worked.
- Add an optional text field for what could improve, left optional so a happy customer can submit without suggestions.
- Add an optional email field for follow-up, but mark it optional so respondents are not forced to identify themselves.
- Export to CSV when ready to review the month's feedback.
Fields in this form
4 fields, using 3 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| How satisfied are you? | Slider | Yes |
| What went well? | Long text | Yes |
| What could we improve? | Long text | Optional |
| Email, if you'd like a reply | Optional |
What goes wrong with this form
Specific to a customer satisfaction survey form, not general advice about forms.
Asking improvement suggestions as required
Leave improvement suggestions optional. A satisfied customer has nothing to improve and should not have to type "nothing" to get through the form — that fills the feedback with noise and costs completion rate.
Using a text field for the satisfaction score
A text field produces "8/10", "eight", "pretty good" — none comparable. A slider is the field type here; it arrives as a number a spreadsheet can work with.
Putting the score at the end instead of the start
Lead with the score. A respondent who stops partway through still contributes a number to your average. End with optional open questions so you capture the score even from someone who rushes.
Questions about this form
What should a satisfaction survey ask?
A satisfaction score on a slider (0–10 is standard, set the range in settings), a required field asking what went well, and an optional field for improvements. Three fields is usually the ceiling — every extra one costs completions, and on a feedback form the people you lose are disproportionately ones with mild opinions.
How do I trend feedback over time?
Export to CSV each month and keep the files. Over time, you can stack the satisfaction scores and see whether the trend is moving. That signal — whether customers are more satisfied month to month — matters more than any single number.
Can I see the satisfaction score without reading the feedback?
Yes — export to CSV and the score is a column you can sort or filter on without opening the text. The open feedback is in the same row, so you can read the detail for responses that interest you — a critical score, or a very high one.