Customer feedback board: start from one that already works
A customer feedback board is a shared page where customers post ideas and problems, vote on each other's, and see what you decided. Its value comes from being shared. Ten people asking for the same thing in ten emails is noise; one request with ten votes is a signal you can act on.
Setting one up is mostly a matter of choices: what categories to use, which statuses to show, and what the first posts look like. In Votelantern, you define a board's categories and each poster picks one. Below are two boards with those choices already made, and an example of the roadmap a board produces.
Starter board 1: a customer-facing software product
Quillpost is a fictional newsletter tool for small publishers; the posts below are made-up examples.
Categories: Writing and editing Sending Subscribers Reports Account and billing
- Schedule a send for a time zone Planned Sending
Many of my readers are on the other side of the country. I'd like to pick the time zone for a scheduled send instead of using mine. - Save a draft as a reusable layout In progress Writing and editing
I rebuild the same header and footer every week. Saving a draft as a layout would save me ten minutes per issue. - Import subscribers from a spreadsheet with tags Under review Subscribers
When I move a list over, the tags column is ignored, so I have to tag everyone again by hand. - See which links readers clicked per issue Shipped Reports
I want to know which stories people opened, not just whether they opened the email. - Pay yearly instead of monthly Open Account and billing
A yearly option would make my bookkeeping simpler. - Dark mode for the editor Closed Writing and editing
I write late at night and the bright editor is hard on the eyes.
A board for a fictional newsletter tool, with five categories, six statuses and example requests at different stages.
Why it is set up this way:
- Categories follow the product, not the org chart. Writing and editing, Sending, Subscribers, Reports, and Account and billing are words a customer would use. "Backend" and "Growth team" are not.
- Five categories, no more. With too many, people pick the wrong one and you spend time moving posts.
- Every status appears at least once, so visitors can see the board is tended: something shipped, something planned, something politely closed.
- The example posts describe a problem. "Many of my readers are on the other side of the country" says more than "time zones please".
Starter board 2: an internal tool team
Not every board faces customers. Teams that build tools for their own colleagues get the same flood of requests, from support, operations or finance, and the same "did anyone look at this?" follow-ups.
Dispatchdesk is a fictional in-house order and delivery console used by the support and warehouse staff of a made-up home goods retailer; every post below is invented for the example.
Categories: Order lookup Returns and refunds Warehouse screens Reports for managers Access and logins
- Search orders by the customer's phone number In progress Order lookup
Callers often don't have their order number handy. Being able to look them up by phone would keep them from waiting on hold while I search by name. - Show the reason code on every return Planned Returns and refunds
When a return comes back to the warehouse, we can't see why the customer sent it. A reason code on the return screen would tell us whether to restock or set the item aside. - Bigger buttons on the packing station screen Shipped Warehouse screens
We wear gloves at the packing benches, and the small buttons are easy to miss. Larger targets for Packed and Problem would cut down on mis-taps. - Weekly late-delivery summary for team leads Under review Reports for managers
Every Monday I copy late deliveries into a spreadsheet by hand. A saved weekly view I can send to my manager would replace that chore. - Let new starters see the console before their first shift Open Access and logins
New staff wait for access until their first morning, so their training session is spent watching someone else's screen. - Undo for a refund issued by mistake Under review Returns and refunds
If I click the wrong order, I have to ask finance to reverse it. A short undo window would save a ticket. - Color the order status badges Closed Order lookup
All the statuses look the same gray, so I read every word. Separate colors would make the list quicker to scan.
A board for a fictional in-house order console used by a made-up retailer's support and warehouse staff.
What changes for an internal board:
- Categories by screen or job. Order lookup, Returns and refunds, Warehouse screens, Reports for managers, Access and logins. Staff know these names already.
- Posts carry a business reason. The phone-search post explains it would keep callers from waiting on hold, which helps you weigh it against other requests far better than a bare "add phone search" would.
- Privacy. An internal board usually shouldn't be public. Private boards are on the Business plan, and a private board's roadmap and changelog are private too. On Free and Team, boards are public.
The roadmap a board feeds
A board on its own shows demand. A roadmap shows your answer. Each board in Votelantern has one roadmap, and its Now, Next, Later layout reads the statuses on that board: In progress appears under Now, Planned under Next, and Under review under Later. You can rename the columns. Open either starter board and its roadmap fills from its own posts.
An example Now, Next, Later roadmap for a different fictional product, an invoicing app, is on the roadmap template page, with more layouts such as quarterly columns. It uses the same statuses as the boards above.
Customer feedback board ideas: categories by product type
If neither starter board fits, start from a list like these and trim it to five.
- A billing or invoicing app: Invoices, Payments, Clients, Reports, Account.
- A scheduling or booking product: Booking, Calendar, Reminders, Staff, Payments.
- A developer tool or API: Endpoints, Docs, Dashboard, Limits and keys, Account.
- An online course or community: Lessons, Members, Events, Payments, Mobile access.
- A shop or marketplace back office: Products, Orders, Shipping, Reports, Account.
If you add a catch-all such as "Something else", as the feature request template does, put it last and check it weekly. When several posts there share a theme, that theme is your missing category.
Five habits that keep a board useful
- Reply to new posts within a few days, even if only to say "Under review". Silence teaches customers not to post.
- Merge duplicates as you see them. The votes move to the request you keep, so the count stays honest.
- Close what you won't build, with one sentence of why. A closed request with a reason beats one that sits open forever.
- Pin one model request at the top so newcomers see what a good post looks like.
- Tell people when it ships. Link the changelog entry to the request. Voters who opted in get an email, and the request moves to Shipped.
Where to put the board
- A link in your help menu and emails. The board has its own address, on our subdomain or, on the Team plan, your own domain.
- Inside your product. The widget opens the board in a panel. On Team, your app can pass a signed token so customers are already identified and don't need to confirm their email.
- In support replies. When someone asks for a feature, reply with the link to the existing request so they can vote.
What it costs
Draft pricing, which may change before launch. Free is $0: one public board, the roadmap, the changelog and the widget, unlimited customers, posts and votes, one admin, and a "Powered by Votelantern" badge. Team (price not set yet): up to three admins, up to five boards, identify users, a custom domain and Slack or Teams alerts. Business (price not set yet): up to ten admins, unlimited boards and private boards, and CSV export.
FAQ
Should one board cover everything, or should I make several? Start with one. Split only when two audiences need different categories, such as customers and internal staff.
What statuses should a customer see? Use all six: Open, Under review, Planned, In progress, Shipped and Closed. Hiding Closed makes a board look like nothing is ever turned down.
Can I seed the board before launch? Yes. Post the top requests you already know about, written as problems, so the first visitors have something to vote on.
Will customers see each other's email addresses? No. Names show as first name and last initial, posters can choose to be anonymous, and emails are never public.