Feature Request Form

A user with an idea gets a fair hearing: space to describe the feature, say which part of the product it touches, and flag how urgent it feels. You get the other half of the deal: every request arrives in the same shape, so comparing fifty of them takes minutes instead of an afternoon.

The template has eight fields on a single content page, followed by an ending page that thanks the requester. Uplup recommends running it in conversational mode, which shows one field at a time and suits the 3 to 5 minutes it takes to complete. It's free to use, and everything below can be edited before you publish.

Eight fields that separate a wish from a plan

The form opens with name and email so you can follow up when a request ships or needs clarification. A Product Area dropdown routes the idea to Dashboard, Forms, Analytics, Integrations, or Other, and you should swap those options for your own product's map before launch. Then the request itself: a short Feature Title and a longer Feature Description, both required.

The last three fields do the prioritization work for you. A Priority scale runs from Critical down to Nice to have, and a workflow impact question makes requesters commit to a major, moderate, or minor improvement. An optional Use Case box invites the story behind the ask, which is often the most useful part of a submission.

Turning submissions into a ranked backlog

Every submission lands in your Uplup dashboard, where per-question breakdowns show patterns a single request can't: which product area draws the most asks, how often Critical actually gets picked, whether self-reported priority matches claimed workflow impact. A request marked Critical but only a minor improvement reads very differently from a Medium request promising a major one.

When it's time to plan, export the whole set as a CSV and sort it in a spreadsheet, or connect webhooks or Zapier to push each new request into the tracker your team already works in. The form does the collecting; your existing tools keep doing the managing.

Collecting requests wherever your users talk to you

A feature request channel only works if people can find it. Share the form as a direct link in your changelog, help docs, or support replies, or post it to social channels when you announce a release. A QR code works for user conferences and printed material. If you'd rather keep requesters on your own site, drop in the embed snippet, and WordPress sites can place it with a shortcode through the Uplup plugin. Add your logo and brand colors first so the form reads as yours, not ours.