Send feature request status updates to the customers who asked, brief your team privately, and see which accounts heard back, all from the idea.

The ability to update the internal or external status of any feedback is great, with the ability to specify and email those that have voted for an item.
The best part is that we can update the status of the issue so that the user is also updated of the progress.
Customers who ask for something and hear nothing stop asking. Every idea has a public status customers see and an internal status only your team sees. Change either one, add a message, and choose who hears about it.

Supporters subscribe when they vote on the portal, use the widget, or are added by your team. The Chrome extension has a Subscribe user to updates checkbox when you capture feedback for a customer.
Each person's own notification settings still apply, and every email has an unsubscribe link. The email shows the old and new status, your message, and a link to the idea. Teammates who captured feedback get a copy with the words they captured. The statuses guide covers setup.
Each kind of update reaches a different group. Check the audience before you post, because a status change can't be unsent.
Closing the loop is shared work. Each team owns a different part of the message.
A status isn't the only time to write. Before you commit to a design, ask the people who requested it whether it solves their problem. Email an idea's subscribed supporters to ask a question or share a design. Their replies come back to UserVoice and sit in the idea's activity, visible to admins, not posted publicly.

A few rules keep updates useful and avoid surprises.
The UserVoice agent and the UserVoice MCP server can find ideas, draft updates, and change statuses. Before anything changes, they show who will be emailed and wait for you to confirm.
Only if you choose. Each update has an Email subscribers checkbox. Leave it unchecked and customers aren't emailed, though teammates who captured feedback still are. For why every answer matters, even a no, read why you shouldn't ignore customer feedback.
No. Comment emails are off for customers by default. An admin can turn them on for new users, and each person can change their own setting.
No. Replies come back to UserVoice and show in the idea's activity for admins. They don't become portal comments.
Yes, once your sending domain passes SPF and DKIM checks. Ask us during your demo about setting it up for your account.
Yes. Select ideas in the idea grid and change their public status together, with one message and one notify choice.
Yes. Choose which channels get public status updates, internal status updates, and new comments. Slack channels can also see reactions to status emails.
No. View-only admins can read through the agent and MCP. Changing a status needs permission to edit feedback.
Get a free 30-day trial after your demo, see your own customer feedback in a real account.
Book a demo