Feature request form
A feature request form gathers ideas from your users in a structured way — what they want, why they need it, how urgent it is. Instead of scattered emails or random suggestions, you get prioritised ideas your team can evaluate together.
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.
Priority sorting shows high-impact ideas first
When a requester rates their request "critical" instead of guessing, you can sort the CSV by priority and tackle the highest-impact ideas first.
Use-case text prevents building the wrong thing
A requester might ask for feature X, but the real problem is Y. A "what problem does this solve" field surfaces that gap so your team can suggest a better solution.
No card required.
Feature Request
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add text fields for the requester's name and email so you can ask clarifying questions.
- Add a textarea for the feature description — what exactly the user wants to build or change.
- Add a second textarea for the use case: what problem does this solve or what does it enable.
- Add a select dropdown for priority so you can sort by impact.
- Export to CSV and share with your team weekly, or post each new request to Slack in real-time.
Fields in this form
5 fields, using 4 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Your name | Short text | Yes |
| Yes | ||
| What feature or change would you like? | Long text | Yes |
| What problem does this solve? | Long text | Yes |
| Priority for you | Select | Yes |
What goes wrong with this form
Specific to a feature request form, not general advice about forms.
Asking "how long would this take to build"
Users cannot know your architecture. They will guess wildly or leave it blank. Your team estimates effort during roadmap planning, not in the form.
Ignoring duplicate requests
If several users request the same feature separately, that is your strongest signal. Track request frequency so duplicates drive priority.
Never closing the loop with requesters
If a user's request makes it into your roadmap, tell them. It takes thirty seconds and builds loyalty; silence makes them think their feedback disappeared.
Questions about this form
How do I handle feature requests that my team disagrees with?
Collect them all in the form regardless. A CSV export shows which ideas multiple users are asking for — duplicates are your signal that a request matters.
Should I promise to build every feature request?
No. Make it clear the form is a suggestion channel, not a commitment. Your team reviews and decides what fits your roadmap.
Can I use this form for bug reports too?
You can, but a separate bug report form is better. Features and bugs need different fields — bugs need reproduction steps, features need use cases.