Every idea in one folder, by theme
The inbox files requests into the Ideas folder as they arrive, and you can group them by theme and, from Starter, filter by plan, company or any trait you pass.
Feature requests
Collect feature requests with the reason behind them
Let customers ask for what they need, in your app or from a link, and tell you the problem behind it. Usertick groups every request by theme, shows who asked and keeps each one in step with the issue in Jira or Linear.
A request is only as useful as the problem behind it
"Add a PDF export" tells you what someone asked for. "I send the report to my manager every Friday and copy it by hand" tells you what to build. A good feature request survey asks for both, and for how the customer gets by today.
With Usertick, requests come from a feedback button in your app, a short survey after someone clicks a feature that isn't built yet, or a link in your changelog. Every request carries the person, their plan and their company, so you can tell a common need from a loud one.
The AI reads each request and files it as an idea under a theme, and the inbox counts them. On every plan, a workflow opens one Jira or Linear issue per theme and adds every later request to it, so the size of each need stays visible while the team decides.
- Plans
- Request surveys, AI sorting and the inbox on every plan, the free plan included
- Where
- A feedback button, a popup at the moment, a link, or an email
- Grouping
- Ideas sorted into themes as they arrive, with counts and change
- Trackers
- Jira, Linear, Productboard and more tools through Zapier on every plan
Let requests come from wherever customers are
Every source lands in one inbox, already sorted.
A feedback button in your app
Add a side button with "Suggest an idea" as a first choice, so a request is always one click away. Set it to show on every visit so it stays after someone answers.
When someone clicks what isn't built yet
Show a feature behind a Coming soon badge, and a click on it opens a short follow-up: how important it is, what it should include and whether to email them when it is ready. Starter and above, and 1 survey on Free.
A link from your changelog or help center
Share the request survey's link in release notes, a help article or a community post, tagged with where it was shared, so you know which audience asked.
Ideas from every other survey
An open answer in any survey that reads as a request is filed as an idea too, so requests hidden in an NPS comment or a churn survey still reach the list.
See which requests come up most
Count requests by theme and by customer before you rank them.
Trade-offs in numbers
Ask customers to rank a short list or split 100 points across it, and Results shows the average place or points for each item, so priorities are clear.
A theme for every feature you are weighing
On every plan, add your own theme for a feature under discussion, up to your plan's limit, describe what it should catch or let the AI draft it, and see how many of your last 100 answers it would have caught before you save it. New requests are filed under it from then on.
Track every request to a decision
Statuses in the inbox and issues in your tracker, kept in step.
From Open to Planned to Resolved
Give each request an owner and a status, add notes with mentions, and keep Planned and In progress as the list your team works from.
One issue per theme, with a running count
A workflow opens a Jira or Linear issue for each theme and adds every later request to it with the customer's words and a count. Every plan.
Customer requests in Linear
Each request becomes a customer request on the Linear issue, with the company from the customer's email, so the issue shows who is waiting for it. Every plan.
Status that follows the work
Once you turn on sync, an issue moving to In progress or Done moves every linked request with it, and a status change reaches webhooks and Zapier, ready to tell the customer. Every plan.
How to collect feature requests with Usertick
Four steps from a feedback button to issues in your tracker.
- 1
Start from a template
Pick the Feature request, Integration request or Fake door follow-up template, or describe what you want to learn to Create with AI.
- 2
Know who is asking
Call Usertick.identify() with the user's ID, email and traits such as plan, so every request carries the person and the account.
- 3
Place it where requests happen
Add a side button to your app, open the follow-up on a Coming soon feature, or share the link in your changelog.
- 4
Send requests to your tracker
Add a workflow that opens one Jira or Linear issue per theme, and turn on status sync so the inbox follows the work.
How to handle feature requests well
Six habits that turn a list of wishes into decisions.
- 01
Ask for the problem
Follow "What would you like us to add?" with "What problem would it solve?" and "How do you handle it today?".
- 02
Ask how much it matters
Add an option such as "It would decide whether we stay", so the requests that put an account at risk stand out.
- 03
Count before you rank
Group by theme and by plan first. A request asked loudly by one customer and one asked quietly by fifty look different once counted.
- 04
Use points for trade-offs
A list of wishes shows what people want. Splitting 100 points shows what they would give up for it.
- 05
Keep one issue per need
Let later requests join the open issue, so the tracker shows the size of a need instead of a pile of duplicates.
- 06
Tell people what happened
When a request ships, reach the people who asked. Their names and emails stay on each response, and a status change reaches webhooks and Zapier.
Feature request templates and questions
Start from a template written for requests, integrations or roadmap priorities, and change any question.
Templates
Browse all templatesProductFeature requestCollect feature ideas together with the problem behind them and how people cope today. Link it from your help menu, your roadmap or your changelog.
ProductIntegration requestLearn which tools customers want you to connect to and what they'd do with the connection. Link it from your integrations page.
ResearchFake door follow-upFollow up with people who selected a feature that doesn't exist yet: how much they need it, what it has to include and whether they want to hear when it's ready. Show it right after the button for the planned feature is selected.
ResearchRoadmap prioritiesLet users divide 100 points across what you could build next, so you see real trade-offs instead of a wish list. Send it to active users before you plan the next quarter.
Questions from the library
Browse the question library- What should we build next?Text · Features
- Put these in the order you would want them built.Ranking · Features
- How often would you use this?Dropdown · Features
- Would you pay extra for this?Yes / No · Features
- How do you handle this today?Text · Research
- What would you move to the top of our list?Text · Roadmap and requests
- What are you working around today because we do not support it?Text · Roadmap and requests
- Split 100 points across where we should spend next yearPoints allocation · Roadmap and requests
Frequently asked questions
Ask in the product, at the moment a need comes up, and ask for the problem behind the request as well as the request. A feedback button covers anything, a short survey after someone clicks a feature that isn't built yet catches demand for it, and a link in your changelog reaches people reading about what's new.
AI reads each written answer as it arrives and files it under a type, such as idea, and a theme from your list, such as Missing capability or Integration wanted. The inbox groups requests by theme with counts, and on every plan you can add a theme for each feature you are weighing, up to your plan's limit.
Yes, on every plan. A workflow opens an issue for each request or for each theme, and later requests on the same theme join the open issue with a count. In Linear, each one becomes a customer request with the company.
Yes, once you turn it on. You choose what syncs when you connect: an issue moving to In progress or Done moves every linked request to the status you mapped, and comments, priority and the assignee can follow.
Each request keeps the person's name and email, so you know who to tell. On every plan, a status change reaches webhooks and the Zapier Response Status Changed trigger, which can start an email in your own tool. Usertick doesn't send the announcement itself.
No. Usertick collects requests privately and counts them by theme for your team. To show a roadmap or voting board to customers, send requests to a tool such as Productboard, Canny or Aha! through a workflow.
Yes, from Starter. Pass the plan, company and any other trait with Usertick.identify(), and the inbox can filter requests by them, so you can see what larger accounts ask for.
Show the feature behind a Coming soon badge or button, and open a short follow-up when someone clicks it, asking how important it is and whether to email them when it is ready. Click triggers work on 1 survey on Free and on every survey from Starter.
Request surveys, AI sorting, your own themes, the inbox and workflows to Slack, Jira, Linear, Productboard, webhooks and Zapier come with every plan, the free plan included. Starter adds click triggers on every survey and more workflows. The free plan keeps 30 days of responses.
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.
- 150 responses a month on Free
- Every channel and AI analysis
- No card needed