Usertick
Start free
Feature request survey template

Collect feature requests, with the problem behind each one

Four questions for your help menu or changelog: what users want added, the problem it would solve, how they handle it today and how important it is. Use it as it is or change any question, and Usertick reads every written answer for you.

Get started freeAll templates

What this feature request survey tells you

A feature request survey turns a one-line wish into something your team can weigh. This template asks four questions in a little over a minute: the request in the user's words, the problem it would solve, how they cope today and how much it matters to them.

It is written for a link in your help menu, on your roadmap page or in your changelog, where users go when they have an idea. The same survey runs in your web app as a side button or as a popup on the changelog page, and the link can go in your own emails, support replies and community posts.

Every written answer is read as it arrives and filed under a category such as features and gaps or integrations, with a theme, a type and a sentiment, so the same idea written ten different ways lands under one theme. Results shows how users cope today and how important their requests are, and selecting Critical narrows the page to the requests that could cost you customers.

As a linkOn your websiteIn an emailAs a conversation
Questions
4
Time to answer
About a minute
Written for
A link in your help menu, roadmap page or changelog
Plans
Every plan, the free plan included

See it on every channel

The same template on your website, behind a link, in an email and as a conversation.

The 4 questions, one by one

What each question asks, why it is there, what it shows you and what to change.

Question 1 of 4 · Text

What would you like us to add or improve?

Why ask it
The request comes first and in the user's own words, so nothing in a list of options steers what they ask for.
What you learn
Usertick reads each request, gives it a category and a theme from your list, and marks it as an idea, a bug or a complaint. Results groups the answers by theme with each theme's trend, so a request many users make shows as one growing theme.
Make it yours
Keep it required. A feature survey with the feature left blank tells you little.
Question 2 of 4 · Text · Optional

What problem would it solve for you?

Why ask it
Users describe solutions, while your team designs for the problem behind them. Two users asking for different features often share one problem.
What you learn
Each answer with its sentiment and theme, filterable by theme, so you can read every problem filed under one area side by side.
Make it yours
Read this answer before the request when you plan, and look for problems that come up across several themes.
Question 3 of 4 · Multiple choice

How do you handle this today?

Why ask it
How users cope today shows the cost of the gap. Another tool means they could leave for it; a workaround in your product means they want to stay and are paying for it in time.
What you learn
A donut with the share and count of each answer and the typed Other answers listed. Select I use another tool to see which requests send users to other products.
Make it yours
If competitors matter to your planning, add a rule that sends I use another tool to a short text question asking which one.
Question 4 of 4 · Multiple choice

How important is this to you?

Why ask it
Importance in the user's own terms separates a nice extra from a reason to leave. The three levels are easy to tell apart and quick to pick.
What you learn
The share of each level over time. Select Critical, I might leave without it to filter the whole page to those requests and the problems behind them.
Make it yours
On every plan, a workflow can post every critical answer to your product channel in Slack or Microsoft Teams, so the team sees it the day it arrives.

What the answers show

Results turns each question into numbers you can follow week by week.

How do you handle this today?

The share of each answer with its count. Select an answer to narrow the whole page to those people and read what else they said.

How important is this to you?

The share of each answer with its count. Select an answer to narrow the whole page to those people and read what else they said.

Every written answer, read for you

Each answer arrives with its category, theme, type and urgency, so the urgent ones reach your team first.

Use this template in four steps

From the template to the first answers.

  1. 1

    Open the template

    Sign up free and pick Feature request in the template gallery. It opens in a matching style, ready to change.

  2. 2

    Make the questions yours

    Reword any question, change the options, and add logic or more questions.

  3. 3

    Choose where it runs

    Show it on your website, send it by email, share its link and QR code, or switch it to a conversation.

  4. 4

    Publish and read the answers

    Answers arrive in Results and the inbox as people send them, each written one read and filed by Usertick.

Tips for this survey

Small choices that keep people answering and the answers useful.

  1. 01

    Put the link where ideas start

    Add the link to your help menu, the changelog and the reply your support team sends when a user asks for a feature, so every request lands in one place.

  2. 02

    Pass the account with each request

    In your web app, call Usertick.identify() with the user's ID, plan and email, so each request shows who asked and you can weigh it by the account behind it.

  3. 03

    Send requests to your product tool

    On every plan, a workflow creates a Productboard note, a Jira issue or a Linear issue for each request, and in Jira and Linear it can create one issue per AI theme instead.

  4. 04

    Show users what shipped

    Mark each request's status in the inbox as you plan, and announce what shipped in the changelog next to the link, so users see that requests lead somewhere.

Product feedbackSaaS surveysLink and QR code surveysTrial and conversion questions

More product feedback templates and questions

Templates like this one, and single questions from the library to add to it.

Templates

Browse all templates
ProductProduct feedbackGive users one place to share what they think of the product, sorted by area so it reaches the right team. Run it as an always-on feedback button inside your app.
ProductBeta feedbackGet structured feedback from early users on a feature before it launches to everyone. Send it after testers have used the beta for about a week.
ProductFeature adoption checkFind out whether users have found a new feature, what keeps the rest away and what would make it part of their routine. Show it in the app two weeks after the release.
ProductDeveloper experienceLearn how quickly developers get their first API call working and where your docs or SDKs slow them down. Send it a few days after someone creates their first API key.

Frequently asked questions

Wherever users already go with ideas: the help menu, your changelog, your roadmap page and your support replies. In a web app, a side button keeps it one click away on every page.

Start with the themes that grow fastest, then filter by Critical, I might leave without it and by users who use another tool today. Those requests carry the most weight.

It shows the cost of the gap. Users who do it by hand or skip it lose time with you, and users on another tool already have a way out.

Yes, on every plan. A workflow creates a Jira or Linear issue for each request or one per AI theme, and Productboard gets a note with the user as the customer.

Yes, when you know who they are. In a web app, Usertick.identify() adds the user's email to each answer; on the link, add a Contact question for a name and an email.

Yes. Every template comes with every plan, the free plan included, and the free plan covers 150 responses a month across your surveys.

Yes. The template becomes your own survey, so reword any question, add or remove questions, and change the options and the logic. The gallery stays as it is.

Yes, from Starter. The template is written in US English. Add languages by hand or with AI translation, and each person sees the survey in their browser's language.

Listen better, act faster, and build what truly matters.

Start free, see what your customers mean, and get each answer to the person who can act on it.

Get started freeTalk to sales
  • 150 responses a month on Free
  • Every channel and AI analysis
  • No card needed