Usertick
Product feedback

Product feedback from inside your app, sorted before you read it

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.

Feedback that arrives with everything you need to act

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.

Plans
Feedback button, in-app surveys, AI sorting and the inbox on every plan, the free plan included
Ways to open
A side button, a popup after a feature, a card inside the page, your own menu item
Screenshots
Marked up by the user, with password and card fields blurred, on every plan
Follow-up
Slack, Microsoft Teams, Jira, Linear and Productboard on every plan

Give users a way to tell you, on any screen

An always-on button for anything, and short questions at the moments that matter.

A feedback button on every screen

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.

Right after someone uses a feature

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.

Inside the page it is about

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.

Behind your own Give feedback item

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.

Every answer arrives with its context

No follow-up email to ask which page, which plan or which browser.

Who sent it

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.

The screenshot they marked up

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.

What it is about

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.

See what users ask for most

The inbox and Results turn single answers into patterns you can plan around.

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.

Themes that grow, flagged early

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.

From feedback to the roadmap

Workflows send each answer to the tool where the work happens, and keep both sides in step.

One issue per problem, with a running count

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.

Status that moves both ways

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.

Ideas to Productboard

Send feature ideas to Productboard as notes with the user as the customer, ready to link to a feature. Every plan.

Urgent answers in Slack

Post urgent bugs to the team's channel with buttons that assign them or set their status in Usertick. Every plan.

How to collect product feedback with Usertick

Four steps from the script tag to your first answers in Jira.

  1. 1

    Add Usertick to your app

    Paste the script tag into your app once, and call Usertick.identify() with the user's ID and traits such as plan.

  2. 2

    Start from a template

    Pick the Product feedback or Website feedback button template, or describe what you want to learn to Create with AI.

  3. 3

    Choose where it opens

    Pick a side button, a popup after a feature or a card inside a page, then choose who sees it and how often.

  4. 4

    Publish and connect

    Publish the survey, then add a workflow that sends bugs to Jira or Linear and urgent answers to Slack.

How to get product feedback you can use

Six habits that keep the answers specific and the backlog honest.

  1. 01

    Ask about one feature at a time

    Open the question right after a feature runs, and name the feature in it, so every answer describes the same thing.

  2. 02

    Keep the button for everything else

    A side button catches what you didn't think to ask about. Keep it short: what it is about, and what happened.

  3. 03

    Ask for a screenshot only for bugs

    Send people who report a problem to the screenshot question with a branching rule, and keep the survey short for everyone else.

  4. 04

    Pass plan and role

    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.

  5. 05

    Correct a reading once

    When a type or theme is wrong, fix it in the inbox. The correction counts everywhere the answer appears.

  6. 06

    Count before you build

    Group requests by theme and watch how each one grows before you commit a sprint to it.

Product feedback templates and questions

Start from a template written for features, betas and new releases, and change any question.

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.
ProductWebsite feedback buttonAn always-on button that lets visitors report a problem, suggest an idea or leave a compliment. Keep it on every page as a side tab.
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.
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.

Frequently asked questions

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.

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