Bugs, ideas and questions in their own folders
The inbox files every answer by type as it arrives, with counts for each folder, and from Starter you can filter by plan or any trait you pass.
Give users a feedback button on every screen and ask about a feature right after they use it. Usertick sorts every answer into bugs, ideas and questions, keeps who sent it and where, and sends it to Jira, Linear or Slack.
Users notice the broken button, the missing export format and the confusing setting long before a report shows it. With Usertick, they can tell you on the screen where it happened, through a feedback button that is always there or a short survey that opens after they use a feature.
Every answer arrives with the person who sent it, their plan and other traits, the page they were on and a screenshot they marked up themselves. The AI reads each answer and files it as a bug, an idea, a complaint, a question or praise, with a theme, so the inbox sorts itself.
From there, a workflow turns bugs into Jira or Linear issues and keeps their status in step with the inbox, sends ideas to Productboard and posts urgent answers to Slack. Your team works from the tools it already uses.
An always-on button for anything, and short questions at the moments that matter.
Add a side button that stays on the edge of every page, so users can report a problem or share an idea whenever it comes up. Set it to show on every visit so it never disappears.
Your app tells Usertick when an export or a report finishes, and a short question about that feature opens a moment later. Events from your code are on Starter and above, and 1 survey on Free.
Place the survey inside a settings page, an empty state or a new screen, as part of the layout, so feedback sits next to the thing it describes.
Open the survey from a menu item or a button you already have. A click on any element on your page can open it, on 1 survey on Free and on every survey from Starter.
No follow-up email to ask which page, which plan or which browser.
Pass the user's ID, email and traits such as plan and role with Usertick.identify(), and each answer belongs to a person and an account, with a Verified mark when it is signed.
Users can capture the screen or one part of it, then draw, box or hide what they need before sending. Password and card fields are always blurred. Every plan, 1 per survey on Free.
Each answer is read as it arrives and given a type, a theme, a sentiment and an urgency, in any language, so a bug report and a feature idea never sit in the same pile.
The inbox and Results turn single answers into patterns you can plan around.
The inbox files every answer by type as it arrives, with counts for each folder, and from Starter you can filter by plan or any trait you pass.
Results counts each theme and compares it with the period before, so a problem that doubled this week stands out from the ones that are steady.
Workflows send each answer to the tool where the work happens, and keep both sides in step.
Open a Jira or Linear issue for each theme, and later answers about the same problem join that issue with a count, so the size of a problem is always visible. Every plan.
Once you turn on sync, an issue moving to In progress or Done moves the response with it, and comments and the assignee can follow. Every plan.
Send feature ideas to Productboard as notes with the user as the customer, ready to link to a feature. Every plan.
Post urgent bugs to the team's channel with buttons that assign them or set their status in Usertick. Every plan.
Four steps from the script tag to your first answers in Jira.
Paste the script tag into your app once, and call Usertick.identify() with the user's ID and traits such as plan.
Pick the Product feedback or Website feedback button template, or describe what you want to learn to Create with AI.
Pick a side button, a popup after a feature or a card inside a page, then choose who sees it and how often.
Publish the survey, then add a workflow that sends bugs to Jira or Linear and urgent answers to Slack.
Six habits that keep the answers specific and the backlog honest.
Open the question right after a feature runs, and name the feature in it, so every answer describes the same thing.
A side button catches what you didn't think to ask about. Keep it short: what it is about, and what happened.
Send people who report a problem to the screenshot question with a branching rule, and keep the survey short for everyone else.
From Starter, traits from identify() let you read feedback by plan or role in the inbox, so a request from a large account is easy to find.
When a type or theme is wrong, fix it in the inbox. The correction counts everywhere the answer appears.
Group requests by theme and watch how each one grows before you commit a sprint to it.
Start from a template written for features, betas and new releases, and change any question.
Paste the Usertick script tag into your web app once, then add a side button that stays on every screen or a survey that opens after a feature is used. Single-page apps work too, since page rules are checked again after every in-app navigation.
Yes, on every plan, with 1 per survey on Free. A screenshot question lets users capture the whole screen or one part of it, then draw, add arrows or boxes and hide anything private before sending. Password and card fields are always blurred.
AI reads each written answer as it arrives and gives it a type (bug, idea, complaint, question or praise), a theme from your list, a sentiment and an urgency. The inbox files answers into folders by type, and a teammate's correction counts everywhere.
Yes, on every plan. A workflow opens an issue for each answer or each theme, and later answers about the same theme join the open issue. Once you turn on sync, the issue's stage moves the response's status, and comments, priority and the assignee can sync too.
Yes. Call Usertick.identify() with the user's ID, email, name and traits such as plan and role, and each answer belongs to that person. From Starter, the inbox can filter by any trait.
No. The widget runs in its own isolated layer, so your styles and its styles never mix, and it adds one global object, window.Usertick. It shows only on your verified domain and its subdomains.
Yes. On every plan, target pages, devices, countries and new or returning visitors. Skipping people who answered another survey recently and showing it to 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 their traits.
No. Usertick collects feedback inside your product and sorts it for your team. To show a roadmap to users, send answers to a tool such as Productboard or Canny through a workflow.
The feedback button, in-app surveys, screenshots, AI sorting, the inbox and workflows to Slack, Jira, Linear and Productboard come with every plan, the free plan included. Starter adds event triggers on every survey and more than 1 screenshot question per survey, and Pro adds the Frustration trigger.
Start free, see what your customers mean, and get each answer to the person who can act on it.