Customer feedback tools, sorted by the question you're asking
"Customer feedback tool" is a label stuck on very different products. Some send questionnaires, some live in a support inbox, some put a button inside your app, and some host a public list of requests that customers vote on. They don't really compete with each other. Each one answers a different question, so the best customer feedback tool for you depends on which question you need answered this quarter.
Which question are you asking?
| Your question | Kind of tool | What it gives you | Where it falls short |
|---|---|---|---|
| What should we build next, and how many people want each thing? | A public request board | A shared list of requests with votes, comments and statuses | Votes reflect the people who found the board, not your whole customer base |
| What went wrong on this screen, just now? | An in-app feedback button | Notes written in the moment, inside the product | Notes arrive one at a time, and someone still has to sort them |
| What does this one customer need help with? | A support inbox | A private conversation and a fix for one person | Feature requests get buried in closed conversations |
| Why do customers do what they do? | Interviews | Depth: the job behind a request, in the customer's own words | Slow to run, and a handful of conversations is not a count |
| How do customers feel about us, and is that changing? | Scored questionnaires | A number you can watch from one quarter to the next | Says little about what to build or fix |
You'll probably use more than one of these over time. Start with the row whose question matters most today.
Where Votelantern fits
Votelantern is the request-board kind, with two pieces attached: a public roadmap that reads the board's statuses, and a changelog that tells voters when their request shipped. Its widget also gives you a feedback button inside your app, but that button opens the board in a panel. What people write there joins the shared list of requests rather than arriving as a private note.
So if your question sits in the support, interview or questionnaire rows, you'll want a help desk, a calendar and a notes document, or a questionnaire tool for that job. The board still helps alongside them. When a support reply, an interview or an open-text answer turns up a feature request, send the person to the board so they can post it or vote.
How to run a request board well
1. Give each audience its own board
Customers and colleagues use different words for the same product. If both send you requests, give each group a board with its own categories. Two starter boards are ready: one for a customer-facing software product and one for a team that builds an internal tool. Both are rendered on the customer feedback board page.
Each opens in a free account with five categories, all six statuses and example posts written problem first. An internal board usually shouldn't be public: private boards are on the Business plan, and on Free and Team every board is public.
2. Put the board where feedback already turns up
Customers won't go looking for a board. Link it from your help menu and your emails, add the widget to your app, and answer feature asks in support with a link to the matching request instead of "we'll pass it on".
3. Triage on a fixed day
Pick one slot a week. Approve first posts waiting in the moderation queue, merge duplicates (the votes move to the post you keep), tag what's new, and pin one well-written request near the top so newcomers can see what a good post looks like. A short slot every week beats a long cleanup every quarter.
4. Make every status mean one thing
Agree as a team what each status means before you use it. Planned should mean "we intend to build this", not "we like this". The roadmap reads Under review as Later, Planned as Next and In progress as Now, so a loose Planned turns into a loose public promise.
5. Close the loop where people can see it
When a request ships, link it from a changelog entry. Publishing the entry moves the request to Shipped and emails the voters who opted in to "Email me updates". When you decide against one, set it to Closed and post a comment with the reason, so the next visitor reads your answer instead of asking again.
6. Treat votes as one signal among several
Votes tell you how many board visitors care. The other rows in the table tell you why, and how much it costs them. Before you plan a popular request, check it against what support and recent interviews are telling you.
Collecting, managing and tracking customer feedback
People searching for a customer feedback collection, management or tracking tool usually mean one of three jobs. Here is what each looks like on a request board, and how Votelantern handles it.
| Job | What it means | How Votelantern does it |
|---|---|---|
| Collecting | Getting requests into one place | A public board, the widget's feedback panel, and a link you can share anywhere. Posting needs a verified email or, on Team, a signed token from your app |
| Managing | Turning many posts into a short list | Merge with votes moving, tags, board categories, pinning, and a moderation queue for first posts |
| Tracking | Knowing what happened to each request | Six statuses, follow, "Email me updates", the roadmap, and changelog entries linked to the requests they ship |
If you've decided a request board is what you need and want to compare vendors of that kind, our product feedback software page lists what a small team would pay at each, with every price dated.
A free customer feedback tool, and what it leaves out
Votelantern's prices are drafts and could change before launch. The Free plan costs $0 and includes one public board, the roadmap, the changelog and the widget, unlimited end users, posts and votes, voter update emails and one admin. Every free page shows a "Powered by Votelantern" badge. Team (price not set yet) adds up to three admins, up to five boards, signed-token sign-in, a custom domain, and Slack and Teams alerts, and lets you remove the badge. Business (price not set yet) adds up to ten admins, unlimited boards, private boards and CSV export of posts and votes.
FAQ
Can one tool answer all five questions? Some suites try to cover several rows. We'd still judge each tool on the one row you most need answered.
Should requests from the support inbox go on the board? Yes, if they are feature requests. Reply with a link to the matching request so the customer can vote and follow it, or ask them to post it. Bug reports and account questions belong in the inbox.
Won't a public board show competitors what we're working on? It shows what customers ask for and what you've decided to plan. If that is too much, keep roadmap items broad, or use a private board on the Business plan.
How do I know which customer posted a request? Posters confirm their email with a one-time link. On the Team plan, your app can pass a signed token, so you know which account each request came from. Publicly, names show as first name and last initial, and email addresses are never shown.