Most customers who leave feedback never hear back. Not a response, not a status update, not even a "we saw this." They assume it went into a black hole, because it usually does.
That's not a small thing. The customer who took two minutes to write out a suggestion did it because they care about your business. When nothing comes back, they don't get angry about it. They just stop caring too.
What actually breaks down
The problem isn't that you're ignoring feedback. You're probably doing something with it. The problem is that customers don't know that.
If you fix something based on a suggestion, you might mention it in an email or a changelog. But the person who suggested it isn't necessarily reading your changelog. They're not going to know their idea turned into a real change unless you tell them.
A public roadmap makes that visible. It doesn't require anyone to read a newsletter or check back on your site. They can see it whenever they visit your feedback page, and if they're curious what happened to something they submitted, it's there.
What you're actually showing them
In Feedbaxster, the roadmap has three public columns: Planned, In Progress, and Completed. (There's also a Cancelled status for internal use, but that one doesn't show on the public page.)
Each item you create can have a title, a description, a target date or quarter, and a category. You can also link it to suggestions that inspired it. When an item has linked suggestions, a count shows up on the card, and customers can expand the detail view to see which submissions are connected to it.
That's what closes the loop. Someone submits "I wish you had online booking" and six months later they visit your feedback page and see "Online booking" sitting in the Completed column, with their own suggestion listed underneath it. That's a very different feeling from wondering whether anyone read what they wrote.
If an item has more than one linked suggestion, it gets labeled as an Epic automatically. That's just a signal that several customers asked for the same thing, which is often useful context for people browsing the roadmap.
Setting one up
From your dashboard, go to Roadmap in the sidebar. If it's empty, you'll see an option to add your first item.
When you create an item, you pick a status (start with Planned unless it's already underway), write a short description of what you're working on, and optionally set a target date or quarter. You can also choose a category from a default list (things like Features, UX/Design, Bug Fixes, Mobile) or create your own.
Each item has a visibility toggle. Items are public by default, but you can flip one to private if you're working on something you're not ready to announce.
To link a suggestion to a roadmap item, open the suggestion from your dashboard. There's a "Link to a roadmap item" dropdown in the suggestion detail panel. Pick the matching roadmap item and you're done. The link shows up on the roadmap item's detail panel after, and the suggestion count on the public roadmap card updates to reflect it.
Comments work like you'd expect: customers can leave comments on individual roadmap items from your public page. They need to be signed in to do it, which keeps things from getting spammy. If a comment gets reported, you'll see it in the Reported Comments section at the bottom of your Roadmap page so you can dismiss or remove it.
What it looks like in practice
One business using Feedbaxster ran a coffee shop with a small catering side. They'd been collecting suggestions for a while and had a growing list of things they intended to do but hadn't found time to communicate. They started with three items: a loyalty card program they'd been working on, an update to their weekend catering menu, and a fix for their online order form that was causing confusion.
They moved the loyalty card to Completed when it launched, linked the handful of suggestions that had asked for it, and posted a short update in the item description explaining how it worked.
Over the following weeks they noticed something. People who'd been quiet on the feedback page started showing back up. Not a flood of responses, but a visible uptick. Some left comments on roadmap items. A few new suggestions came in that were clearly from people who'd looked at what was Planned and wanted to add on to it.
It wasn't immediate and it wasn't dramatic. It probably helped that they'd been consistent about checking feedback regularly, so there was already something to show. But posting the roadmap gave customers a reason to come back and look.
Cadence is the thing
An empty roadmap is worse than no roadmap. If someone clicks through expecting to see what you're working on and finds nothing, that's more discouraging than not having the page at all.
You don't need a lot of items to make it feel active. Two or three things moving through statuses over time is enough. What matters is that something ships. If you can move at least one item to Completed every two to four weeks, the roadmap stays honest. People can see it's not a static list of promises.
If you're not sure where to start, look at your feedback page for anything that already has a few upvotes. That's usually the shortest path to an item that customers actually care about. You don't have to build everything customers ask for, but starting from there at least means you're building things people noticed.