Feedback
Feature request
Asks what they're trying to do before what they want built. Half of all feature requests turn out to be a different, smaller problem once you ask.
- Questions
- 5
- Takes about
- 2.5 min
- Style
- One page
- Scoring
- None
Free, no card. It lands in your workspace as an editable draft.
Worth knowing
- The welcome screen and the intro text above the first question carry example turnaround times, policies and promises. Rewrite them as yours before you publish — they are the part respondents take literally.
What's in it
Request a feature
Welcome screen
We ask what you're trying to do before what you'd like built, because the answer often tur…
Rich text
- 1
What would you like to be able to do?*
Short text
- 2
What are you trying to achieve?*
Long text
- 3
How do you handle it today?
Long text
- 4
How much would this help?
It's a nice-to-have · It would save me real time · I can't do my job without it
Multiple choice
- 5
Your email
Email
Logged
Ending
How to use this template
Open it as a draft
Press "Use this template" and it lands in your workspace as an editable form with all 5 questions already in it. No card, and nothing is published until you say so.
Cut what you do not need
Every question you remove is one fewer reason to abandon the form. It takes about 2.5 minutes to fill in as it stands, and that is the number worth protecting.
Add from the question bank
Pick what you are missing from the questions below. Drag any of them in, change the wording, and use conditional logic so people only see the ones that apply to them.
Share it, or put it on your own site
Publish to get a link, or embed it in a page you already have. Answers arrive in your dashboard, and you can send them on to anywhere else with a webhook or an integration.
32 feature request form questions to choose from
Feature requests arrive as solutions. The job of the form is to get back to the problem, because the problem is often solvable without building the thing that was asked for.
Ask what they are trying to do before you ask what they want you to build.
The problem
- What are you trying to do?
- What is stopping you today?
- How do you work around it at the moment?
- How long does that workaround take?
- How often do you hit this?
- What happens if it never gets solved?
- Who else on your team hits the same thing?
- When did this first become a problem?
The request
- What would you like us to build?
- What would it look like if it worked perfectly?
- Where in the product would you expect to find it?
- Is there a tool that already does this well?
- What does that tool get right?
- What should we not copy from it?
- Would a partial version help, or is it all or nothing?
- Is there a simpler version that would do?
Weighting it
- How much time would this save you per week?
- Would it change which plan you are on?
- Is this blocking a purchase or a renewal?
- How urgent is it? (Now, this quarter, someday)
- Would you pay extra for it?
- How many people at your company would use it?
- Is there a deadline driving this?
- What would you trade for it?
Staying in touch
- What is your name?
- What is your email address?
- What is your role?
- Which plan are you on?
- How long have you been a customer?
- Would you test an early version?
- Can we contact you to talk it through?
- Would you like to be told when it ships?
Feature Request form questions, answered
- What should a feature request form ask?
- The problem before the solution. 'What are you trying to do and what stops you' tells you far more than 'what feature do you want', and frequently points at a fix you can ship this week.
- How do I manage feature requests from customers?
- Collect them in one place with enough context to compare them, and be honest about what you will not build. A request that sits unanswered for a year does more damage than a clear no.
- Should I promise to build what people ask for?
- No, and say so on the form. 'We read every one of these and build a few of them' sets an expectation you can keep and still gets you the request.
- How do I tell people when a feature ships?
- Ask for an email and permission on the form, then write to them when it lands. It is the cheapest retention work available and almost nobody does it.
- Is this feature request form template free?
- Yes. Use it, publish it and collect answers on the free plan with no card. Paid plans add things like payments, scheduling, removing our badge and your own domain, but none of them are needed to run this form.
- Do I need an account to use it?
- You need one to edit and publish, because the form has to live somewhere and the answers have to come back to you. Signing up takes about a minute and does not ask for a card. The people filling your form in never need an account.
- Can I change the questions?
- All of them. The template is a starting point, not a fixed form: add, remove, reword and reorder anything, change the look, and use logic so people only see the questions that apply to them.
- Can I put it on my own website?
- Yes. Embed it in a page you already have, or share the link. On a paid plan you can serve it from your own domain so the address says your name rather than ours.
- Where do the answers go?
- Into your dashboard, where you can read, search and export them as CSV. You can also have each response emailed to you, pushed to another tool with a webhook, or sent to a connected integration.
- How long does this form take to fill in?
- About 2.5 minutes as it stands, across 5 questions. Every question you cut brings that down, and shorter forms get finished more often.
Worth reading next
- 30 Customer Feedback Questions That Get Real AnswersQuestions grouped by what you are trying to learn, and the wording changes that stop people giving you polite nothing.
- 18 Survey Question Types, and When Each One Earns Its PlaceMultiple choice, scales, matrices, rankings and open text, with the specific failure mode of each and how to avoid it.
- What to do with two hundred open text answersThe most valuable question on most forms is the one nobody reads, because reading it properly takes an afternoon nobody has.
Others in feedback
Customer feedback
A rating, the reason behind it, and permission to follow up.
Net Promoter Score
The standard NPS question, with the follow-up that makes it useful.
Customer satisfaction (CSAT)
One satisfaction question, asked straight after the interaction.