Three things, done really well
No dashboards to configure. No integrations to wire up. Just the feedback loop your users deserve — a widget they submit to, a roadmap they vote on, and a changelog that closes the loop. Up and running in minutes.
Feedback that lives
inside your app
Most feedback tools ask users to leave your product and visit a separate portal. Most users don't bother — and the insight you needed never arrives. The FeedbackZu widget lives directly inside your app. One click and they're submitting, without ever navigating away from the screen that prompted the thought.
- One script tag. Drop a single line of code into your app — or add it through your tag manager. The widget button appears automatically. No npm install, no build step, no design work.
- Categorize on submit. Users pick Idea, Issue, or Other — so submissions arrive pre-sorted in your inbox and ready to triage, merge, or promote onto the roadmap.
- Anonymous or identified. Ask for an email so you can follow up — or allow fully anonymous submissions to keep friction as low as possible. You decide per workspace.
- Matches your brand. On Pro, customize the widget accent color and remove the "Powered by FeedbackZu" footer so it feels native to your product.
Widget shown on a live app. Try it on this page →
From thought to inbox in three taps
No redirect. No login wall. The feedback arrives the moment your user thinks of it.
Add one line of code
Paste the FeedbackZu script tag into your app's HTML, or load it through Google Tag Manager. A clean feedback button appears in the corner of every page — styled and ready, with nothing to configure.
Your users submit in context
They click the button, choose a type — Idea, Issue, or Other — type their thoughts, and optionally leave an email. The panel opens over your app, so they never lose their place or their train of thought.
It lands on your board, pre-sorted
Every submission flows straight into your dashboard inbox, already tagged by type. From there you triage it, merge duplicates, reply, or promote it onto the public roadmap with a click.
In-context capture
The panel slides over your app instead of redirecting to a portal. You collect feedback in the exact moment it happens — the moment most tools lose it.
Anonymous or identified
Allow fully anonymous submissions for the lowest possible friction, or require an email when you need to follow up. The choice is yours, set once per workspace.
A triage-ready inbox
Idea, Issue, and Other tags mean nothing arrives as an undifferentiated blob. Submissions show up sorted and ready to act on — not as another spreadsheet row.
Let your users tell you
what to build next
Every submission can land on a public board where users upvote the things they care about most. Instead of guessing what to build next — or letting the loudest customer in the room decide — you read the board. The signal is already ranked by genuine demand.
- One vote, one voice. Each person can upvote an item once. The vote count surfaces the strongest demand to the top automatically — no spreadsheet, no manual tallying.
- A clear status workflow. Move items through Open, Under Review, Planned, In Progress, and Shipped. The public board groups everything into tidy Planned, In Progress, and Shipped columns.
- Comments and reactions. Users discuss submissions and react to them, giving you the rich "why" behind each request — context the original one-liner never captures.
- Public or private. Share a public board at a clean URL — or, on Pro, create private boards for beta groups, customer councils, and your own team's backlog.
A live feedback board. Users vote, you prioritize.
Prioritize by demand, not by volume
Turn a pile of requests into a ranked, transparent plan your users can follow.
Submissions become roadmap items
Feedback from the widget, your public portal, or your own team can be promoted onto a board in a click. Similar requests can be merged so the votes — and the demand — stay consolidated.
Users upvote what matters
Anyone can browse the board and upvote the ideas they want most. Vote counts are shown right on each item, and the board sorts itself so the strongest signal is always at the top.
You move it through the workflow
Set each item's status as work progresses — Under Review, Planned, In Progress, Shipped. Everyone following the item gets an email when its status changes, so the board stays a living source of truth.
Demand, already ranked
Vote counts do the prioritization for you. The board surfaces what most of your users actually want — not just what the last person to email you happened to ask for.
Discussion built in
Comments and reactions on every item give you the reasoning behind each request — the use cases, edge cases, and "+1, because…" that turn a vote into a real spec.
Public or private
Run an open board your whole community can see, or — on Pro — spin up private boards for beta cohorts, named accounts, or your internal backlog.
Close the loop.
Every single time.
Most teams ship something and say nothing. The user who asked for the feature never finds out it was built — so they keep asking, and slowly conclude you aren't listening. The FeedbackZu changelog fixes that: mark something Shipped and the loop closes automatically.
- Tied to your roadmap. Publish a changelog entry straight from a shipped item and link it to the original feedback — so the trail from request to release stays intact. Save it as a draft or schedule it for later.
- Notifications on publish. Publishing an entry emails your changelog subscribers, and the users following the shipped item get a status update too — no manual outreach, no "did you know we built this?" support tickets.
- Categorized & filterable. Tag each entry as Feature, Improvement, or Fix. Visitors filter the feed to exactly the kind of update they care about.
-
Custom domain on Pro. Host the changelog at
updates.yourproduct.comwith your own branding and FeedbackZu's removed.
Your changelog, auto-populated as you ship.
One status change, zero busywork
The announcement writes and sends itself the moment you ship.
Ship it and write the note
When a request is done, mark it Shipped and write a short release note in the changelog editor. Link the entry to the original feedback so the line from idea to launch stays visible to everyone.
Publish — or schedule it
Publish the entry to your public changelog, tagged as a Feature, Improvement, or Fix. Save it as a draft to polish later, or schedule it to go live at the right moment. Readers can filter the feed by category.
Everyone hears about it
Publishing emails your changelog subscribers, and the users following the shipped item get a status update too. Anyone can subscribe to catch every future release — the people who asked finally find out you delivered.
Categorized entries
Feature, Improvement, and Fix tags keep your release feed scannable. Readers — and your own team — filter to just what they need in a click.
Email subscribers
A built-in subscribe box turns your changelog into a low-effort release newsletter. Subscribers are emailed on publish, and anyone can opt in with just an email address.
Your domain, your brand
On Pro, host the changelog on your own subdomain with FeedbackZu branding removed, so every release reads as a first-party update from your product.
Start free. Upgrade when it pays off.
Every core feature works on the free plan. Pro removes the limits and adds the polish teams need.
Everything you need to close the loop on one product.
- 1 board, 100 submissions / month
- Embeddable widget on your app
- Public, voteable roadmap
- Public changelog with email subscribers
- Anonymous or identified feedback
- Comments, reactions & status notifications
For teams ready to take feedback seriously.
- Unlimited boards & submissions
- Private boards for beta groups & internal use
- Custom domain on your portal & changelog
- Remove FeedbackZu branding
- Custom widget accent color
- Slack & webhook integrations, priority support
Questions about the features
Do my users need an account to submit or vote?
Will the widget slow down my site?
What statuses can a roadmap item have?
Can I keep a board private?
How does the changelog notify people?
Can I use my own domain and branding?
updates.yourproduct.com, set the widget accent color, and remove FeedbackZu branding so the whole experience feels native to your product.