Feature Request Form

About this block

Feature Request Form is a split call to action that invites input and tells the reader exactly what happens to it. The left side pairs a heading and lede with three numbered triage steps, a person reads it, it gets merged and counted, and you hear the verdict. The right side is a labeled request form card with a one line summary, a context field, a work email, and a helper note under each input that steers toward a useful answer.

The steps are one array of number, title, and detail. The form leans on the shared Input, Textarea, Label, and Button primitives, with the helper lines carrying the guidance instead of placeholder text. Spelling out the triage before the form is the trust device, a request box feels like a black hole until you promise a written verdict for every entry.

When to use

Reach for this block on a roadmap or community page when you want requests and are willing to commit to answering them. The numbered steps set expectations so the form does not read as a suggestion box nobody checks. It pairs naturally with a public voting board where accepted requests go to earn votes, and closes the loop the roadmap opens.

A natural flow around it on a Marketing Pro page:

Before

• Roadmap board showing where accepted requests end up

After

• Community sections for the people who want to keep talking
• FAQs answering the questions the form invites

What you can display

One strong use is a product feature request intake. Other forms:

• Integration request. Ask which tools to connect next for the ecosystem page.
• Beta interest. Collect context from teams who want early access.
• Content request. Let readers pitch topics for a docs or media team.

Tip: keep the triage promise honest, a written verdict for every request is the whole reason this outperforms a generic contact form.