What should a product feedback form ask?

What they were trying to do and where it went wrong, before anything about features. People describe solutions fluently and problems badly, and the solution they name is rarely the cheapest fix.

How do I prioritise feature requests from a form?

Ask what the request would save them and how they handle it today. A request that saves someone four hours a week and one they mention in passing look identical in a list of votes, and completely different once you ask.

Should I let people vote on features?

Voting tells you what is popular among people who found your feedback form, which is not the same as what matters. It is useful as one input, misleading as a roadmap.

How do I follow up on product feedback?

Ask for an email and permission to use it, then actually write back when you ship. The second part is what turns a feedback form into a channel people keep using.

Is this product feedback form template free?

Yes. Use it, publish it and collect answers on the free plan with no card. Paid plans add things like payments, scheduling, removing our badge and your own domain, but none of them are needed to run this form.

Do I need an account to use it?

You need one to edit and publish, because the form has to live somewhere and the answers have to come back to you. Signing up takes about a minute and does not ask for a card. The people filling your form in never need an account.

Can I change the questions?

All of them. The template is a starting point, not a fixed form: add, remove, reword and reorder anything, change the look, and use logic so people only see the questions that apply to them.

Can I put it on my own website?

Yes. Embed it in a page you already have, or share the link. On a paid plan you can serve it from your own domain so the address says your name rather than ours.

Where do the answers go?

Into your dashboard, where you can read, search and export them as CSV. You can also have each response emailed to you, pushed to another tool with a webhook, or sent to a connected integration.

How long does this form take to fill in?

About 2 minutes as it stands, across 4 questions. Every question you cut brings that down, and shorter forms get finished more often.

Feedback

Product feedback

Aimed at people already using the product. The last question is the one that matters — the thing that nearly made them stop is usually the thing worth fixing.

Use this template Browse all templates

Questions: 4
Takes about: 2 min
Style: One page
Scoring: None

Free, no card. It lands in your workspace as an editable draft.

Worth knowing

The welcome screen and the intro text above the first question carry example turnaround times, policies and promises. Rewrite them as yours before you publish — they are the part respondents take literally.

What's in it

Tell us what's working
Welcome screen
Your answers go to the people who build the product, not to sales. The last question is th…
Rich text
1
Which parts do you use?
Building forms · Responses and exports · Analytics · Integrations · +1
Multiple choice
2
How easy is it to use?
Opinion scale
3
What's missing?
Long text
4
Has anything nearly made you stop using it?
Long text
Thank you
Ending

How to use this template

Open it as a draft
Press "Use this template" and it lands in your workspace as an editable form with all 4 questions already in it. No card, and nothing is published until you say so.
Cut what you do not need
Every question you remove is one fewer reason to abandon the form. It takes about 2 minutes to fill in as it stands, and that is the number worth protecting.
Add from the question bank
Pick what you are missing from the questions below. Drag any of them in, change the wording, and use conditional logic so people only see the ones that apply to them.
Share it, or put it on your own site
Publish to get a link, or embed it in a page you already have. Answers arrive in your dashboard, and you can send them on to anywhere else with a webhook or an integration.

32 product feedback form questions to choose from

The hard part of product feedback is not collecting it. It is getting past 'please add dark mode' to the problem underneath, which is usually something you can solve three other ways.

These questions are built to surface the problem rather than the proposed solution.

How they use it

What do you mainly use it for?
How often do you use it?
Which part do you use most?
Which part do you never touch?
What were you using before this?
How long have you been using it?
Who else on your team uses it?
What does a typical session look like for you?

What is not working

What is the most frustrating part?
Where do you lose the most time?
What takes more clicks than it should?
What do you have to do outside the product to finish a job?
Is there anything you have built a workaround for?
What have you given up trying to do?
What breaks most often?
What would you warn a new user about?

What is missing

What is the one thing you wish it did?
What problem would that solve for you?
How do you handle that today?
How much time would it save you per week?
Is there a competitor that does it well?
What would you be willing to pay for it?
If we could only build one thing this quarter, what should it be?
What would you happily give up to get it?

Context for weighting it

What is your role?
How big is your company?
Which plan are you on?
How technical would you say you are?
Is this blocking you, or just annoying?
How urgent is it?
Would you like to test an early version?
Can we contact you to talk about this?

Start from this template See all templates