Product teams can take enhancement ideas on a public roadmap page. The form should ask what they need and how soon, so requests are not trapped in a sales Slack huddle.
Notify product@, not only support.
Feature, integration, UX, other—in the copied select.
Honesty about ‘we read these, we do not commit dates’ belongs in the intro copy.
Paste into Linear/Jira manually or via Zapier.
A feature request form is how a user asks for behaviour the product does not have yet. It is distinct from a bug: the product works as designed; they want a new design. US product orgs often score these in Canny or Productboard; UK B2B teams still often live in a spreadsheet. The HTML form is the intake, not the roadmap vote.
Without structure you get ‘make it like Salesforce’. With a textarea and a type field you get a job-to-be-done, a workaround, and whether it is blocking a renewal.
Ask for the job and the workaround. Do not ask them to write your spec.
Never auto-reply that it is ‘on the roadmap’. That is a legal-adjacent promise in some enterprise deals.
Canny, UserVoice, and Linear intakes exist. HTML is honest when you are not ready to run a public voting board.
Quiet intake. You control the narrative; they do not pile-on vote.
Great marketing, noisy signal, and competitors reading the board.
Biased to the last deal. Still log it here so engineering sees the same queue.
Too slow. Use the form year-round.
A /changelog page on Astro or Next.js static export can host this form next to ‘what we shipped’.
Export quarterly for planning. US and UK privacy notices should say you keep product-feedback emails for research.
Not from A form on your site. Reply personally if you want a conversation.
Search the dashboard. Thank them and link to the existing ticket if you have one.
Do not let this form amend the contract. Features stay in the SOW process.
You can make email optional on the form. You will not be able to follow up.
Capture repro steps, severity, and environment from users on your site.
A lighter intake than a feature request for culture, process, or UX niggles.
Collect quotes, permission to name the company, and a contact for follow-up.