Feedback widget: a way in for requests, and a way out for news
A feedback widget is a small button on your website or web app that lets people tell you something without leaving the page they are on. The useful ones do two jobs: they take feedback in, and they show people what happened to it.
Not every feedback widget does the same job
"Feedback widget" names several different things.
- Page markup tools let a visitor point at part of a page and leave a note. They suit design and bug work.
- One-question pop-ups ask "Was this page helpful?" or a scored question. They measure a moment.
- Chat windows start a conversation with your support team.
- Request-board panels open your feature request board in a panel, so people can post an idea, vote on existing ones and follow them.
Votelantern's widget is the last kind, with a second panel for product news. If you need the first three, they are different products, and it is fine to run one alongside a request board.
What Votelantern's widget does
The widget has two modes.
- A feedback button that opens your board in a panel. People see the existing requests first, so they can vote on a match instead of posting a near copy. They can also post, comment and follow.
- A "what's new" panel that shows your latest changelog entries inside your product.
It comes on every plan, Free included, where it carries a "Powered by Votelantern" badge. The widget is a small, versioned script that runs in its own sealed area of your page, so its styles and yours don't collide.
Where to place it
These are judgments, not rules. Test them on your own product.
- In the help or account menu of your app, where people look when something is missing. It stays out of the way.
- As a small corner button on the screens where people do their main work. That is where ideas occur to them.
- Next to a feature you just launched, for a few weeks, to catch first reactions.
- Not on sign-up or payment screens. Someone halfway through paying shouldn't be asked for ideas.
- On your marketing site, if you like. Visitors there aren't signed in to your app, so they confirm an email address to post (a one-time link, valid for 15 minutes).
What it should ask
Each post on a Votelantern board has a title and a body. Make the body prompt ask about the problem, not the fix. A prompt we suggest, for a fictional timesheet app: "What were you trying to do when you thought of this?" That draws out "I log the same hours every Friday" rather than a bare "add templates".
Keep the form short. As admin you can add a few extra fields (short text, long text, a select list or a checkbox), and the "Email me updates" box is always on the form. Every field you add is one more reason to close the panel, so add one only if you will act on the answer. The feature request tool page walks through what happens to a request once it is posted.
Recognizing signed-in users (Team plan)
Inside your app, customers are already signed in, so asking them to confirm an email again is friction. On the Team plan, Votelantern can identify them instead.
- Your server signs a short-lived token with a secret key for that board. The token says who the person is, such as their name and email, and when it expires.
- The widget passes the token when it opens. Votelantern checks the signature and the expiry.
- The person posts and votes as themselves, with no extra step. Other people still see only "First L." as the name, and email addresses are never shown publicly.
Three points for the developer who sets it up:
- Keep the secret on your server. Never put it in code that runs in the browser.
- A token never grants admin rights. Admin access comes only from your team's own Votelantern accounts.
- Two keys can be live at once, so you can swap to a new key without breaking signed-in posting.
On Free, the widget works the same way, but people confirm their email before they post or vote.
Closing the loop with "what's new"
The second panel is what turns a widget from a suggestion box into a conversation. When you publish a changelog entry linked to requests, those requests move to Shipped, and voters who chose "Email me updates" get an email. Everyone else sees the entry in the "what's new" panel the next time they open it.
A sample "what's new" panel, with recent changelog entries the way your users would see them inside an app, is on the changelog template page.
For how changelog tools compare, see changelog software.
Start with a board for the widget to open
A widget that opens an empty board invites nobody. This starter board has categories, all six statuses and example posts; rename the categories to fit your product. It is previewed on the customer feedback board page.
Which plan each tool puts its widget on
Read on each rival's own page, 10 November 2026. The second column is the plan where the tool recognizes your signed-in users (vendors use several names for this). Where a pricing page didn't say, the table says so.
| Tool | Widget | Recognizes signed-in users |
|---|---|---|
| Canny | Free (base features) | Free (base features) |
| Featurebase | Growth (embeddable in-app widgets) | Growth (automatic user authentication) |
| Upvoty | Not stated on the pricing page | Hyper |
| Fider (cloud) | Not stated on the page | Not stated on the page |
| Sleekplan | All plans (JavaScript kit, Indie included) | Starter |
| UserJot | Not gated on the page; its branding row covers board and widget on all plans | Starter (automatic login) |
| FeatureOS | Starter | Add-on on Starter, included on Growth |
| Rapidr | Startup | Business |
| ProductLift | Not stated on the pricing page | Business |
| Supahub | Starter (changelog and feedback widgets) | Growth |
| FeedBear | Lite | Business |
| Productboard (portal) | Embedded portal on Business | Business (portal) |
| Votelantern (draft) | Free and up | Team (signed token) |
Frill, Nolt, Feature Upvote and Convas refused our page reader, so we have nothing for them.
What the table shows: at several tools the widget comes on an early plan, while recognizing signed-in users inside it sits higher. At Rapidr and FeedBear, for example, the widget is on the first plan and user recognition is on Business. If you want the widget to know who your customers are, price the plan with both.
Draft prices
Votelantern's prices are drafts and may change before launch. Free is $0: the widget, one public board, the roadmap and the changelog, with one admin and the badge. Team (price not set yet) adds identify users, a custom domain, up to three admins, up to five boards and a removable badge. Business (price not set yet) adds private boards and up to ten admins.
FAQ
Do I need a developer to add the widget? Someone who can paste a script snippet into your site can add it. Recognizing signed-in users takes a little server code, because the token is signed on your server.
Can the widget show only product news, without the feedback button? The feedback button and the "what's new" panel are separate modes, so you can use either.
Will people see each other's email addresses in the widget? No. Names appear as first name and last initial, a poster can choose to be anonymous, and email addresses stay private.
Can someone use a forged token to post as another person? Not without your secret key. Votelantern rejects a token whose signature doesn't match, or one that has expired.