A feature request tool, step by step
Requests arrive in support tickets, sales calls, chat and the odd tweet. A feature request tool pulls them into one place where customers post, vote and follow what happens next. This page walks through how one works.
On a real board, people post requests, vote and follow them; when an admin moves a request from Under review to Planned, the roadmap updates. A starter board with fictional example posts is on our customer feedback board page.
What happens to a request, step by step
Every feature request tool is, underneath, a small workflow. Here is the one Votelantern uses. Knowing it helps you judge any tool, including ours.
- A customer posts. They give a short title and describe the problem. Posting needs a verified email (a sign-in link valid for 15 minutes) or, on the Team plan, a signed token from your app that says who they are.
- Others vote and comment. One vote per person. Display names show as first name and last initial, and a poster can choose to stay anonymous on a request. Emails are never shown.
- You triage. New requests start as Open. A first post from a new person can wait in a moderation queue until you approve it. You tag the request, pin it if it matters, or merge it into an existing duplicate. When you merge, the votes move to the surviving request.
- You set a status. Under review, Planned, In progress, Shipped or Closed. The roadmap page reads these: In progress shows under Now, Planned under Next and Under review under Later.
- You ship and tell people. A changelog entry linked to the request moves it to Shipped and emails every voter who opted in to updates.
If a tool you are testing skips step 3 or step 5, expect more cleanup and more "any news on this?" emails.
The form decides the quality of your board
A board fills with one-line wishes like "dark mode" or "better reports" unless the form asks for more. Those are hard to compare and harder to merge. The fix is to ask for the problem first, and the idea second.
The feature request template page shows a request form for a fictional inventory app. It asks what the person is trying to do before it asks what would help.
In Votelantern, every post has a title and a markdown body. On top of that, you as the admin can add a few extra fields (short text, long text, a select list or a checkbox), and the "Email me updates" box is always there. The template below sets up its extra fields for you, and you can change them once the board opens.
Before you add a field of your own, run it past three questions:
- Will anyone act on the answer? If nobody will sort, merge or reply differently because of it, leave it off.
- Can a requester answer it in a few seconds? Questions about budgets, deadlines or business impact stall people at the keyboard.
- Do you know it already? If your app passes a signed token on the Team plan, you know who posted, so don't ask.
Where answers fall into a handful of buckets, a select list keeps them comparable; a free-text box gives you a different phrase from everyone. And "which part of the product" doesn't need its own question: posters pick one of the board's categories, which you define.
For the reasoning behind each field in the template, and the fields we'd leave off, see the feature request template.
Start from a board that is already set up
An empty board looks abandoned. A starter board comes with categories (you set them as admin, and posters pick one when they post), statuses and a few example posts that show customers how a good request reads.
Once it opens, rename the categories to match your product, delete or pin the example posts, and share the link or add the widget to your app.
Managing and tracking requests without a spreadsheet
People searching for a feature request management or tracking tool are often leaving a spreadsheet behind. A spreadsheet works until three things happen: the same idea arrives five ways, nobody remembers who asked, and customers can't see progress. A board fixes each one.
- Duplicates: merge them and the votes add up in one place.
- Who asked: each request keeps its voters and commenters, and followers get status emails if they opted in.
- Progress: statuses feed a public roadmap, so customers can check for themselves.
What a board doesn't do is decide for you. Votes show demand from the people who found your board, which is not the same as your whole customer base. We suggest treating vote counts as one input next to revenue, strategy and effort. Say a request has 40 votes and another has 12: the smaller one may still matter more if it blocks your largest accounts.
Where Votelantern fits, and where it doesn't
Draft prices, not final: Free is $0 with one public board, the roadmap, the changelog and the widget, unlimited end users and one admin, with our badge on. Team (price not set yet) covers up to three admins, up to five boards, identify users, a custom domain and webhook alerts to Slack and Teams. Business (price not set yet) adds private boards, up to ten admins and CSV export.
Be aware of what isn't in the first version. There is no Zapier app and no two-way sync with issue trackers, so if your engineers live in one, requests won't flow there by themselves. Posts are text: end users have no way to add images or files, and that is deliberate. If those matter, compare other tools on the feature request software page, which lists what vendors gate by plan.
FAQ
Can customers post without creating an account? They confirm their email with a one-time link, or your app signs them in with a token on the Team plan. There is no password to set up.
What stops spam on a public board? First posts from new people can go to a moderation queue, and every post and comment has a Report button.
Can I hide a request I won't build? You can set it to Closed and add a comment saying why, which keeps the votes visible and heads off repeat requests, or delete it.
Can I post on the sample board? No. The sample board on our customer feedback board page is a static example. Open the starter board template when you want a board of your own.