Product feedback form template

A product feedback form is not a feature request box. A request box collects solutions ("add a dark mode"), mostly from your loudest users. This template collects the problem behind the request, tied to the feature where it happened and a score you can compare month to month. That is the difference between a wish list and something a product team can prioritize. Product research covers the wider program this form fits into.

Anchor every answer to one feature

Question 1 does the sorting for you. When someone picks the reporting screen, every answer after it is about the reporting screen, so the responses table splits cleanly by feature and nobody has to guess what "it's slow" referred to. Keep the list to four to six of your most used areas plus "Something else". If you have twenty features, run one form per area.

Use a 1 to 5 rating, and keep NPS for the relationship

Question 2 is a Rating question set to five points. Five is enough to separate "works for me" from "gets in my way" without asking people to choose between a 6 and a 7. NPS asks something different, how likely someone is to recommend the whole product on a 0 to 10 scale, and it belongs on a quarterly cycle; the NPS survey template is built for that. Run both, just not in the same form. Rating scale questions goes deeper on picking a scale.

Ask what is missing, not what to build

Question 4 reads "What is missing that you expected to find?" on purpose. "What should we build next?" invites people to design your product for you, and the answers come back as features. "What did you expect to find" gets you the job they were trying to do when they hit the wall, which is the part you can use. Read twenty of these and the same three or four gaps start to repeat. Those are your roadmap candidates, each one with a feature and a score attached.

Keep the screenshot optional

A screenshot shows in two seconds what a paragraph takes a minute to describe: the error message, the broken table, the setting someone could not find. It is also the question most likely to stall someone on a phone, so it is optional and says so. Set the allowed file types and a maximum file size in the question settings, so a long screen recording does not arrive where you wanted a screenshot. Uploads count toward the 100 MB of file storage on the free plan; Pro has no storage limit. More on file uploads.

Ask permission before you follow up

The most useful product feedback turns into a fifteen-minute call. Question 6 asks for permission first, and only a yes opens the email field, so you hold contact details for the people who agreed to hear from you and nobody else. It also makes consent easier to show; the GDPR-compliant forms guide covers the rest.

Send it where people use the product

Feedback about a feature is best collected near the feature. Put the link in your in-app help menu, in the email that announces a release, or at the end of onboarding once someone has had a week with the product. Share the public link or embed the form on a page from the share and embed panel. Ask each person once a quarter at most: a survey that turns up every week teaches people to ignore it.