Feedback board to changelog: closing the loop with your users

By Hasan · November 5, 2026 · 3 min read

A feedback board only works if it ends somewhere. Customers submit an idea, others vote, you decide, and then the people who asked see it ship. That last step is the one most teams skip. This guide shows how to run the loop end to end. I am building JustOneCX (disclosure), so the setup uses its Roadmap & Changelog. The loop works with any tool.

What are the three parts?

Part What visitors see
Ideas Ideas with votes and comments. Visitors can submit new ones.
Roadmap Ideas grouped by status: planned, in progress, shipped.
Changelog The entries you published, newest first. Visitors can mark an entry helpful.

What is the loop?

  1. A customer submits an idea, or you add one yourself.
  2. Other customers vote and comment.
  3. You move it through the roadmap: Planned, In progress, Shipped.
  4. When it ships, you publish a changelog entry.
  5. The people who asked can see it landed.

Skipping step 4 is the common mistake. People who asked for a feature and never hear back stop asking.

Where can you show it?

You manage it in one place, and turn each way on or off in its Publish tab:

  • On your own website, embedded in any page, plus an in-app What's new panel.
  • On your own subdomain, such as roadmap.yourcompany.com. Add a TXT record to prove you own the domain and a CNAME to the hosting domain. The dashboard shows the status: pending, verified, active.
  • On a hosted page at boards.justonecx.com/<your-workspace>/roadmap, with no code.

All of them show the same content.

What about private boards?

A private board opens only for a visitor whose identity was verified. On a hosted page or a custom domain you use a sign-on link from your server, so a signed-in customer is recognised. The secret key stays on your server. See board sign-on.

How do you keep the board healthy?

  • Merge duplicates, so votes are not split across five wordings of one idea. Merged ideas can be restored from the trash.
  • Moderate comments. A moderation queue holds anything you want to check.
  • When you change an idea's status, voters are emailed. Think before you move something to Shipped.
  • Write the changelog entry in the customer's words, not in the words of the ticket.

A small habit

Once a month, open the board, sort by votes, and look at the top five. For each one write down: shipping, not shipping and why, or not sure. Then say so on the board. Even a "not planned, here is why" keeps trust.

What next?

Read the Roadmap, ideas and changelog guide and hosted boards. If you want to see it first, you can book a demo.

See it working in 2 minutes

Try the live demo

Related