Choose by where your requests come from and how you'll tell customers what happened to them. A simple voting board suits small teams. A wider feedback platform suits companies sorting requests from many channels, and a support-led tool suits teams whose requests mostly arrive as chats and emails.
Feature request boards look alike from the outside: a list of ideas, a vote button and a status label. The differences show up later, when you're sorting hundreds of requests and trying to tell customers what happened to theirs. Here are eight options for product teams moving on from Nolt, in no particular order.
Eight feedback tools at a glance
| Tool | Kind of tool | Good for |
|---|---|---|
| Canny | AI feedback management | Capturing and sorting feedback from many sources with AI |
| FeedBear | Feedback board and updates | Small apps keeping users posted on product changes |
| Fider | Open source feedback board | A simple board where users vote on requests |
| Frill | All-in-one feedback tool | Ideas board, roadmap and announcements in one widget |
| Productlane | Support and feedback inbox | Pulling Slack, email and widget messages into one queue |
| Upvoty | Voting feedback platform | Prioritising requests by user votes |
| Userback | Feedback widgets and replays | Bug reports and feedback with session replays |
| UserVoice | Enterprise feedback platform | Weighing large volumes of feedback by revenue |
The full list, A to Z
Alphabetical, in no particular order. Each line paraphrases the vendor's own description.
Canny
Best for: Product teams that want AI to capture, analyse and prioritise feedback; the vendor ties it to building the features that drive revenue.
FeedBear
Best for: Founders of small apps who want ideas collected in one place and customers kept up to date on changes; the vendor names a free plan.
Fider
Best for: Teams wanting a simple home for feature requests where users vote on direction; the vendor describes it as completely free to use.
Frill
Best for: SaaS companies wanting an ideas board, public roadmap, announcements and in-app surveys in one widget, as the vendor lists them; a free plan is named.
Productlane
Best for: Startups that hear requests through Slack, email and a chat widget and want them in one queue to prioritise; the vendor positions it as customer support.
Upvoty
Best for: Product managers who want feedback centralised and sorted by votes, which the vendor says shows what to build next; a free trial is named.
Userback
Best for: QA and product teams wanting widgets, in-app surveys, session replays and feature portals together, which the vendor says speeds up acting on feedback; a free plan is named.
UserVoice
Best for: Enterprise product teams that want to capture feedback anywhere and weigh it by revenue before closing the loop with customers, per the vendor.
Boards, platforms and inboxes
Simple voting boards
Fider, FeedBear and Upvoty keep things close to what Nolt users know: a board, votes and statuses. They suit small product teams and indie founders who want something light that customers will use without any training.
Wider feedback platforms
Frill, Canny and UserVoice add roadmaps, announcements, AI sorting or revenue weighting on top of the board. They make sense when feedback arrives from many places and you need help deciding what matters.
Tools that start from support or bugs
Userback leans towards visual bug reports and session replays, and Productlane starts from support conversations. Look at these when most of your requests arrive as problems rather than ideas.
Where most boards fall short: the update
Nolt describes itself as a shared home for user requests where you collect feedback, plan work and keep users informed. The last part is the one that's easy to neglect. Collecting requests is simple. Telling the right people when something ships is where trust is won or lost. A public changelog is one simple way to do it, so I'd read through these changelog tools for SaaS startups before choosing.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
So when you trial a replacement, test two things above everything else. First, how requests come in and get voted on, including whether customers can add to an existing idea instead of posting a duplicate. Second, how updates reach the people who asked: an email, a changelog post, an in-app message or nothing at all. Tools in this category split by who they're built for and how much you set up yourself, so run the same real request through each one.
Setting up the new board so it stays tidy
- Create a few clear categories before you invite anyone, such as integrations, reporting and mobile.
- Write a short note at the top explaining what happens after someone votes.
- Merge duplicates every week so votes gather in one place.
- Use a small set of statuses, such as under review, planned, in progress and shipped, and stick to them.
- Close requests you won't build with a polite reason, rather than leaving them open for years.
A tidy board is what makes customers come back to it. If they can find their idea and see where it stands, they'll keep adding to it instead of emailing your support team to ask.
Final advice on choosing a feedback board
Pick by where your requests come from today. If customers already visit a board, a voting tool will feel natural. If requests arrive through support chats and email, a tool that gathers them from those channels will save you copying and pasting. And if you've got a large customer base, weighting feedback by account size can stop the loudest users setting your roadmap. If you're a small team, don't let the tool become a second job: a light board you update every week beats a powerful one nobody looks after.
Whatever you choose, export your Nolt board first and keep the vote history, because it's the best record you have of what customers asked for. For more options, see my guides to customer feedback tools and roadmap software.
Do you make feedback board software? Tool makers can ask to be considered for a featured place on this list.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Should my feedback board be public or private?
A public board shows customers you're listening and cuts duplicates, because people can see existing ideas. A private board suits sensitive products or B2B clients who don't want competitors reading their requests.
Do votes tell you what to build?
They help, but they aren't the whole story. Votes favour your most engaged users, so weigh them against support tickets, sales conversations and your own product plans.
How do I move my existing requests to a new tool?
Export your posts, votes and statuses, then check whether the new tool can import them. Where it can't, move the open requests only and keep the export for reference.
Do I need a public roadmap?
Not always. It helps when customers keep asking what's coming next. If your plans change often, a simple changelog of shipped work may serve you better.
How often should I update customers on their requests?
Whenever a request changes status, and at minimum when it ships. A short automatic message to everyone who voted is usually enough.
Should I let customers comment on requests?
Yes, where you can. Comments tell you why people want something, which is often more useful than the vote count. Reply to the most useful ones so people know someone's reading.