Changelog
Publish release notes with labels, let customers subscribe, and link an entry back to the request it resolves.
The changelog is your public record of what shipped. It keeps customers informed, reduces "is this new?" questions, and gives your team a place to celebrate progress.
Entries and labels
A changelog entry has a title, a body, and labels (for example, New, Improved, Fixed) that let readers scan for the kind of change they care about. Entries are drafted first and published when ready, so you can prepare an announcement ahead of a release.
Subscribers
Customers can subscribe to your changelog by email to hear about new releases. When a subscribing email matches an existing customer, the portal can tell that signed-in visitor they are already subscribed, so they are never asked twice.
Linking back to feedback
An entry can point back to the feedback post it announces. When you resolve a request that customers voted on and draft it into the changelog, the entry keeps that link. This is the end of the customer-voice loop: a request came in, customers voted, it moved across the roadmap, it shipped, and the changelog entry ties the announcement back to the exact request, so the people who asked can be told it is done.
Where the changelog appears
The changelog is a public surface: it can appear as a module in the chat widget's support home, inside the customer portal, and as its own page you can link to from your site. Most entries are authored free-form, but the link back to feedback is what makes the changelog feel like a conversation rather than a broadcast.