By plan, role or usage
Pass the user's plan, role and seats with Usertick.identify(), and show a survey only to the people whose traits match your rules. Starter and above.
Product teams
Product decisions backed by what users tell you
Ask the users a feature was built for, right after they use it. Usertick sorts every answer into bugs, ideas and questions with a theme, and sends them to Jira, Linear or Slack with their status in sync.
Feedback at the moment, from the right users
Product teams need feedback that is specific: about one feature, from the people who use it, close to the moment they used it. Usertick asks inside your web app when your code says a feature ran, shows the question only to the plans and roles you choose, and keeps it from coming back too often.
Every answer arrives with the user, their plan and the page, and the AI files it as a bug, an idea, a complaint, a question or praise, with a theme from your list. Results shows how each theme moves week to week, and rankings and points show what users would trade for what.
From there, your tools take over. A workflow opens one Jira or Linear issue per theme and keeps its status in step with the inbox, posts urgent bugs to Slack and sends survey events to Amplitude, Mixpanel or Segment.
- Plans
- In-app surveys, AI sorting and the inbox on every plan, the free plan included
- Install
- One script tag in your web app, single-page apps included
- Targeting
- Pages and devices on every plan, plans and roles from Starter
- Tools
- Slack, Jira, Linear, Productboard and analytics events on every plan
Ask inside your product, at the moment it matters
Short questions where users work, and a button for everything else.
Right after a feature is used
Your app tells Usertick when an export, an import or a report finishes, and a short question about that feature opens a moment later. Starter and above, and 1 survey on Free.
A feedback button on every screen
Keep a side button on the edge of the app for bugs and ideas, with an optional screenshot the user marks up. Screenshots on every plan, 1 per survey on Free.
Before you build
Show a feature behind a Coming soon badge, and a click on it asks how important it is and whether to tell them when it ships. Starter and above, and 1 survey on Free.
When users get stuck
The Frustration trigger opens a question after repeated clicks, dead buttons and errors, while the problem is still on screen. Pro and above.
Ask the users a feature was built for
Targeting by trait keeps each question in front of the right people.
A different version for one group
Show a variant of the survey to users on one plan or in one country, and compare the answers with the base. Business and above.
See what users ask for, and what breaks
Every answer is sorted before anyone reads it.
Bugs, ideas and questions in their own folders
The inbox files every answer by type, with counts, and from Starter filters by plan, role or any trait you pass.
The screenshot behind the bug
Users capture what they see, then draw and box the problem before sending, with private fields blurred. Every plan, 1 per survey on Free.
Themes that move week to week
Results counts each theme and compares it with the period before, so a problem that doubled after a release stands out.
Trade-offs in numbers
Ask users to rank a list or split 100 points across it, and read the average place or points for each item.
From feedback to the roadmap
Workflows put each answer in the tool where the work happens.
One issue per theme in Jira
Open a Jira issue for each theme, and later answers about the same problem join it with a count, so the size of each problem is clear. Every plan.
Customer requests in Linear
Each answer becomes a customer request on the Linear issue, with the company from the user's email. Every plan.
A daily thread in Slack
Post new feedback as it arrives or as one thread a day, with buttons that assign answers and set their status. Every plan.
Survey events in your analytics
Send each answer as an event on the user in Amplitude, Mixpanel or Segment, to read feedback next to behavior. Every plan.
Works with the tools product teams use
Send bugs and ideas to your tracker, conversations to Slack and events to your analytics, and keep statuses in step without copying anything by hand.
See all integrationsHow product teams start with Usertick
Four steps from the script tag to your first issues.
- 1
Add Usertick to your app
Paste the script tag into your web app, and call Usertick.identify() with the user's ID and traits such as plan and role.
- 2
Pick a moment
Start from Feature check-in, Product feedback or Product-market fit, and open it after an event from your code or as a side button.
- 3
Choose who sees it
Target plans, roles and pages, and set how often the survey can return to the same user.
- 4
Connect your tracker
Add a workflow that opens Jira or Linear issues by theme, and turn on status sync so the inbox follows the work.
How product teams get feedback they can use
Six habits that keep feedback specific and the backlog honest.
- 01
Ask right after the action
Open the question on the screen that follows the feature, while the user still remembers what happened.
- 02
One score and one why
A rating and an open question get answered. A long form inside the product gets closed.
- 03
Ask the people a feature is for
Use traits to reach the plan or role the feature serves, and leave everyone else alone.
- 04
Space surveys out
Set how often a survey returns, and wait after someone closes one, so users aren't asked on every visit.
- 05
Offer a screenshot for bugs
A marked-up screenshot answers the first question an engineer would ask.
- 06
Test the wording first
Try a new question on a share of users with a variant before you replace the old one.
Templates and questions for product teams
Start from a template written for features, betas, priorities and fit, and change any question.
Templates
Browse all templatesProductProduct 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.
ProductFeature check-inAsk people right after they use a specific feature how well it did the job and what's missing. Show it once, the second time someone uses the feature, and replace the example feature with your own.
ResearchProduct-market fitTrack product-market fit with the Sean Ellis question: the share of users who would be very disappointed without you. Send it to people who used the product at least twice in the last two weeks.
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- How would you feel if you could no longer use this product?Multiple choice · Product
- How useful is this feature to you?Stars · Features
- How easy was this feature to use?Customer effort · Features
- What is missing from this feature?Text · Features
- What stops you from using this more?Text · Features
- Spread 100 points across what we should work on nextPoints allocation · Product
- What are you working around today because we do not support it?Text · Roadmap and requests
- You would rather weThis or that · Roadmap and requests
Frequently asked questions
Ask users inside the product at the moment they use a feature, collect bugs and ideas through a feedback button, test demand before building, and measure product-market fit. The AI sorts every answer by type and theme, and workflows send them to Jira, Linear or Slack.
Yes. Paste the Usertick script tag into your app once. It works in single-page apps, since page rules are checked again after every in-app navigation. Native mobile apps aren't supported yet.
Yes, on 1 survey on Free and on every survey from Starter. Your app calls Usertick.trigger() with an event name, such as export_done, and the survey opens when it arrives. You can wait for a later time, such as the fifth export, and add rules on the event's details.
Yes. On every plan, target pages, devices, countries and new or returning visitors. Skipping people who answered recently and asking a share of traffic work on 1 survey on Free and on every survey from Starter, and from Starter you can target signed-in users by traits such as plan, role or seats.
Yes, on every plan. A workflow opens an issue for each answer or each theme, later answers join the open issue, and once you turn on sync, the issue's stage moves the response's status in the inbox.
Yes, on every plan. Each answer goes to Amplitude, Mixpanel or Segment as an event on the user you identified, so you can read feedback beside what the user did.
No. Usertick collects and sorts feedback for your team. To share a roadmap with users, send ideas to Productboard, Canny or Aha! through a workflow.
Yes, on Business and above. Show a variant to a share of users or to one plan, and the Variants tab compares it with the base, with a verdict at 95% confidence once both sides have 30 answers.
In-app surveys, the feedback button, AI sorting, the inbox and workflows to Slack, Jira, Linear and analytics tools come with every plan. Starter adds trait targeting, event triggers on every survey and more than 1 screenshot question per survey, Pro adds the Frustration trigger, and Business adds variants.
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