The best feedback widget, according to the questions Reddit keeps asking

“What are people using for a feedback widget?” is one of those questions that gets asked on Reddit every few weeks, in r/SaaS, r/webdev, r/ProductManagement and half a dozen smaller subs, and it almost never gets a straight answer. The replies are usually a list of product names with no indication of which one fits which situation, plus at least one person who built their own.

This page is the answer written out properly. We make one of the tools on this list, which you should factor in, so every section says what the alternatives are genuinely better at and there is a section at the end on when to pick none of them.

The four things people mean by feedback widget

Almost every recommendation thread mixes these up, which is why the answers look contradictory.

• A public voting board. Customers post requests, everyone sees them, people vote. Canny is the best-known. The value is transparency and the cost is that your feature requests become a public forum you have to moderate.
• A private feedback inbox. People write in, only you read it. Nobody performs for an audience, which changes what they write. This is where Voicebox sits.
• Behavioural analytics. Heatmaps and session recordings. Hotjar is the default. You see what people did without asking them anything, which is powerful and answers a different question.
• Visual bug reporting. Annotated screenshots with browser and console detail attached. Usersnap. Built for QA cycles rather than for hearing from customers.

If a thread recommends Hotjar to someone asking about feature requests, or Canny to someone collecting bug reports from beta testers, that is the mix-up happening in real time.

The pricing model matters more than the price

The complaint that comes up most often in these threads is not that a tool is expensive, it is that it got expensive unexpectedly. That is almost always the meter rather than the price.

• Per tracked user means anyone who submits, votes or comments counts. Your bill grows as engagement grows. Canny is free to 25 tracked users, then Core from $19/mo and Pro from $79/mo billed annually, and reported costs at 1,000 tracked users are around $275 and $579 a month respectively.
• Per seat means you pay for colleagues who only ever read. Featurebase runs $29, $59 and $99 per seat per month on its paid tiers, with a permanent free plan at one seat, plus $0.29 per AI resolution.
• Per session is how behavioural tools meter. Hotjar's paid plans are reported from about $32/mo, rising with traffic rather than with feedback.
• Per piece of feedback is what Voicebox uses: $0 for 50 a month, $19 for 3,000, $49 for 15,000, with unlimited seats on the top plan.

None of these is dishonest. They just fail differently. Per-user pricing punishes a successful launch, per-seat pricing punishes involving your team, and volume pricing punishes a spam wave. Pick the failure mode you can live with, and read the longer piece on tracked-user pricing if that is the one biting you.

What each one is actually good at

• Canny if you want customers voting in public on what you build next. Nothing else on this list does that properly, and Voicebox does not attempt it. Full comparison.
• Featurebase if you would rather have one subscription covering support inbox, help centre, roadmap and feedback than run several tools. Full comparison.
• Hotjar if your real question is where people get stuck, not what they think. Full comparison.
• Usersnap if you need reproducible bug reports with screenshots and environment detail. Full comparison.
• Voicebox if you want written feedback collected privately and grouped by the underlying problem, so five wordings of one complaint arrive as one ranked theme instead of five tickets.

When to build your own instead

Someone always suggests this, and for a lot of cases they are right. A form that posts to a database or a Slack webhook is an afternoon of work, and if you get ten pieces of feedback a month you can read all of them yourself. No tool beats reading ten messages.

It stops being right at roughly the point where you can no longer hold the whole picture in your head. That is usually somewhere between 50 and 200 pieces a month, and the symptom is specific: you remember that several people complained about the same thing but you cannot say how many, or whether it is getting worse. Counting that by hand is the work these tools exist to remove.

A shorter way to decide

Three questions, in order:

• Should other customers see what people submit? Yes means a public board. No means a private inbox.
• Do you need to know what they said, or what they did? Said means a feedback tool. Did means behavioural analytics.
• What breaks first as you grow, your user count, your team size, or your feedback volume? Whichever it is, do not pick the tool that meters on it.

Questions people ask alongside this one