How to build a feedback form people actually fill out

The reason your feedback form has a 6% response rate is not the subject line. It's the form.

Specifically: it's that the form was built for the company's data team, not for the person being asked to fill it out. There's a 14-question intake. Three of them are required. The first one is "How would you rate your overall experience on a scale of 1 to 10" and the last one is "Anything else we should know" with no character limit.

Nobody wants to fill that out. I wouldn't fill that out.

Here's how to build a feedback form that the recipient actually finishes.

The structure that works

Six questions. In this order:

1. One opening question they can answer in two seconds. A 5-point happy/sad scale, or a single-tap NPS-style rating. Low cost, high commitment.
2. One follow-up that uses their first answer. "What was the main reason for that score?" — open-ended, but only one of them, and it's the one question that actually gives you signal.
3. One specific thing question. Not "how was your experience" — that's nothing. "What part of the product did you use most this week?" or "Which feature did you reach for first?" — specific, fact-based, easy.
4. One emotional question. "When did you last feel frustrated using this?" — most teams skip this and it's where the gold lives.
5. One forward-looking question. "If we could fix one thing in the next month, what would it be?" — gives you a roadmap.
6. One optional contact question. "Want us to follow up? Drop your email." Optional. Always optional.

That's it. Six questions, two minutes, you're done.

Why this works (and what most forms get wrong)

It opens with a low-cost commitment. Nobody wants to type a paragraph as their first action. Asking for a tap, a number, a tiny commitment — that's the door opening. The rest of the form follows because they've already started.

The second question is conditional on the first. Not technically (though it can be) — psychologically. "You gave us a 6, what's the main reason?" feels like a real conversation, not a script. Whether you actually use form logic to surface a different question depending on the rating is up to you, but you should at least write the second question as if it's responding to the first.

It's specific, not abstract. "How was your experience" is unanswerable. "What did you do first when you opened the app today" is answerable. People don't think in abstractions; they think in moments. Ask about a moment.

It asks about emotion, not just satisfaction. A 9/10 on satisfaction tells you almost nothing. "What was the most frustrating thing this week" tells you exactly what to fix. The hard truth is that customers can be satisfied and still about to churn — emotion is a leading indicator, satisfaction is a lagging one.

It ends with a roadmap question. Asking "what should we build next" is the most under-utilized feedback question on the internet. People love to answer it. They feel heard. Half their answers will be obviously wrong; the other half will give you your next quarter.

Email is optional. This is the easiest fix and almost nobody does it. The moment you require email, your response rate drops by half. Make it the last field, make it optional, and you'll still get most of the emails because they want a follow-up. Asking nicely beats requiring.

What to cut

Cut everything in this list, in this order:

1. Demographics. You don't need their job title to fix the bug they reported. Cut the demographic section unless you can name exactly what decision it changes.
2. Multi-part questions. "How easy was it to sign up and start using the product?" is two questions. Pick one, cut the other, or split them. Never both.
3. The "anything else" textarea with no prompt. It gets two responses: "no" and a five-paragraph rant. Replace it with a focused open-ended question.
4. Required fields. Default to optional. Only require the thing the form genuinely cannot work without.
5. The progress bar. A small "1 of 6" in the corner is fine. A giant blue bar telling them they're 14% done is a great way to get them to leave.

If your form has all five of these, you have a 12-question form that should be a 6-question form. Cutting in half will roughly double your completion rate. I have watched this happen so many times that I'd put real money on it.

Two more things that matter more than they should

One question per screen. I wrote a whole post about this — every form benchmark I've ever run shows the same thing. One-question-at-a-time forms convert roughly twice as well as all-on-one-page forms. If you're using a tool that only does the all-on-one-page format, the tool is the bottleneck.

Send it from a real person. "Quick question from Nikhil at coolform" outperforms "Customer Feedback Survey" by an embarrassing margin. Use a name, write a sentence, ask the question. The form is a tool — the message around it is what gets it opened.

The full template

If you want a starting point — copy this:

1. How was your last week using us? (Sad / Neutral / Happy)
2. What's the main reason for that?
3. Which feature did you reach for first?
4. When did you last feel frustrated using us?
5. If we could fix one thing in the next month, what would it be?
6. Want us to follow up? Drop your email. (Optional)

You can build this in any tool on the internet. You can build it in coolform by typing one sentence — "a 6-question customer feedback form for a SaaS product" — and the AI will produce something close to this in ten seconds, which you can then tweak. (The fifth question, in particular, is one I've added to almost every form I've ever shipped.)

The best feedback form is the one you actually send. Most teams over-engineer it and never ship. Six questions, send it tomorrow, read every response. That's the whole job.

— Nikhil