Which emails featurevote sends, and to whom

When you mark a feature as done, leave Notify Voters ticked in the completion dialog (it is on by default), then mark the feature as completed. The email includes the request’s title, your release note if you wrote one (otherwise the request description), a link to view the completed feature, uploaded images, and a link to your Feedback Portal. It goes to voters who left an email address; one-click voters without an email do not receive it. For a bug on a board with Known issues enabled, the email says Fixed and goes to the reporter and people who selected Me too, if they left an email.

When someone creates a feature request on any of your boards, featurevote automatically emails all team members with access to your workspace. The message includes the request’s title and description, who submitted it, a link to review it in your admin dashboard, and any attachments.

Requests created through MCP are an exception: they do not send the new-request email or Slack notification sent by admin screens.

When publishing a changelog, you can choose to email subscribers and customize the subject line, preview text, and introduction message. The email includes the changelog title and content (including images), links to the detailed changelog and feature board, and an unsubscribe link. Recipients are contacts with an email address who have not unsubscribed; you can use Recipients in the publish panel to select contact groups or individual people.

When your team replies to someone’s comment from the dashboard, that person gets an email. A feature’s creator is notified when someone comments on their request, and your team gets an email when someone comments on your Feedback Portal.

Your plan limits recipients per send, rather than the number of emails per month. The limit applies to changelog emails, voter completion emails, and new-request notification emails to your team: Free allows 50 recipients, Growth 500, and Pro and Lifetime 1,000. If the recipient list exceeds the applicable limit, no email is sent. For changelogs, the entry can still publish without an email; narrow the selected recipients to fit before publishing if delivery is needed.

For new-request team notifications, replies go to your account email, or to the submitter’s email if the account has none. For completed-feature voter notifications, replies go to your account email, or to the admin who marked the feature complete if the account has none. Changelog replies go to your account email or a custom address you configure.

Recipients can unsubscribe from changelog notifications using the link in the email; Gmail, Outlook, and Yahoo also show a one-click unsubscribe option. This stops changelog updates, not feature-completion notifications. If someone marks a changelog email as spam or the address bounces because it does not exist, featurevote unsubscribes them; they appear as unsubscribed in Contacts and no longer count toward the email limit. There is no unsubscribe option for feature-completion notifications.

If Slack is connected, certain events can also trigger Slack notifications: new feature requests, new private feedback in the Feedback Inbox, new comments, features marked complete, and requests reaching 5, 10, 25, 50, or 100 votes. Slack notifications work alongside email; they do not replace it.