Customer feedback form

A score on its own tells you the temperature and nothing about the cause. This form pairs each number with the sentence that explains it, which is the part you can actually act on. It works as a customer satisfaction survey, a post-purchase product feedback form, or a standing feedback link in a footer — the fields are the same, only the audience changes.

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.

Rating and slider fields, not improvised scales

Stars and a 0–10 slider are real field types, so the numbers arrive as numbers. You can average a column of them instead of parsing "8/10" out of a paragraph.

Let the same person answer more than once

Turn on "allow multiple submissions" and a customer can come back after a later interaction, so you see how an opinion moves rather than only where it started.

No card required.

Feedback

Live preview

How to build this form

5 steps in the editor. Nothing here needs a paid plan.

  1. Add a rating field as the first question. Asking for the score first means you get one even from people who stop there.
  2. Add a required long text field asking what decided the score — the number tells you the temperature, this tells you the cause.
  3. Add a slider for the recommendation score, and set its range in the field's settings so it matches the scale in the label.
  4. Add an optional email field so anyone wanting a reply can leave one, without forcing everybody to identify themselves.
  5. Turn on "allow multiple submissions" in Advanced settings so the same customer can answer again after a later interaction.

Fields in this form

4 fields, using 4 of the 19 field types available.

QuestionField typeRequired
How was it?RatingYes
What decided that score?Long textYes
How likely are you to recommend us?SliderOptional
Email, if you would like a replyEmailOptional

What goes wrong with this form

Specific to a customer feedback form, not general advice about forms.

Asking too much

A rating, one open question and a recommendation score is usually the ceiling. Every additional field costs completions, and on a feedback form the people you lose are disproportionately the ones with mild opinions — which skews what you are left with toward the extremes.

Putting the rating in a text field

Keep the rating and the recommendation score as structured fields so they stay countable. A number you have to parse out of a sentence cannot be averaged, and averaging is the whole point of collecting it.

Leaving resubmission off when you want a trend

"Allow multiple submissions" is off by default, which is right for a one-off survey and wrong if you want to see an opinion move over time. Decide which of those you are running before you send the link, because you cannot recover the second data point later.

Questions about this form

What should a customer feedback form ask?

A rating you can average, one open question explaining it, and a recommendation score. Three fields is usually the ceiling — every extra one costs completions. Keep the rating and the score as structured fields so they stay countable, and let the open question carry the detail.

How do I analyse the responses?

Every response is stored in your dashboard and exports to CSV in one click, so the rating and recommendation score come out as columns you can average or chart in a spreadsheet. The open text arrives alongside, in the same row as the score it explains.

Can the same person leave feedback more than once?

Only if you allow it. "Allow multiple submissions" is off by default; turn it on and a customer can come back after a later interaction, which is what lets you see an opinion move rather than only where it started.