> Featurevote docs. Every page, as an index: https://featurevote.app/llms.txt

# Which emails Featurevote sends, and to whom

Featurevote can email voters when their request ships and subscribers when you publish a changelog, and tells your team about new requests.

Source: https://featurevote.app/docs/guides/notifications
Last updated: 2026-10-10

Featurevote sends automatic email notifications to keep everyone informed about feature requests, updates, and changes.

## Types of Notifications

### Feature Completion (To Voters)

When you mark a feature as "done," you can email the people who voted for it. This closes the feedback loop and shows users you listen.

**What it includes:**
- The request's title, as your customer wrote it, so voters recognise what they voted for
- Your release note, if you wrote one in the completion dialog, with the request quoted under it. Otherwise the request's description
- Link to view the completed feature
- Any images you uploaded
- Direct link to your Feedback Portal

**Who receives it:** Voters who left an email address. Visitors who voted in one click without an email don't get it.

**How to send:** Leave **Notify Voters** ticked in the completion dialog (it is by default), then click **Mark as Completed**.

**For a bug:** on a board with [Known issues](https://featurevote.app/docs/guides/known-issues) on, the email says **Fixed** instead of Completed, and its subject reads `Fixed - "…"`. It goes out on the same terms, to the reporter and everyone who said **Me too**, if they left an email.

### New Feature Requests (To Team)

When someone submits a new feature request, your team gets notified so you can review it quickly.

**What it includes:**
- Feature title and description
- Who submitted it
- Link to review in your admin dashboard
- Any attachments

**Who receives it:** All team members with access to your workspace.

**How it works:** Sends automatically when a new feature is created on any of your boards.

### Changelog Announcements (To Subscribers)

When you publish a changelog, all your subscribers receive an email with the updates.

**What it includes:**
- Changelog title and content, including any images in it
- **View detailed changelog** link
- **Visit the feature board** link
- **Unsubscribe** link

**Who receives it:** Everyone in **Contacts** with an email who hasn't unsubscribed. That includes voters and commenters who left an email and contacts you imported. Use **Recipients** in the publish panel to send to one or more contact groups, or to people you pick.

**How to send:** When publishing a changelog, you have the option to send it to subscribers. You can customize the subject line, preview text, and introduction message.

### Comment Notifications

**Reply notifications** — When your team replies to someone's comment from the dashboard, that person gets an email.

**Feature creator notifications** — If you created a feature request, you're notified when someone comments on it.

**Team notifications** — When someone comments on your Feedback Portal, your team gets an email.

## Email Limits

Your plan sets how many people one email can go to. This applies to changelog emails and to emails telling voters their request shipped:

| Plan | People per email |
| --- | --- |
| Free | 50 |
| Growth | 500 |
| Pro and Lifetime | 1,000 |

- The limit is per email, not per month. Publish as often as you like.
- If the list is bigger than your plan allows, no email is sent. For changelogs, the publish screen tells you before you publish and links to an upgrade, and the limit counts the recipients you selected, so narrowing **Recipients** can bring a send under it.

## Reply-To Configuration

Notification emails use smart reply-to logic:

**Team notifications** (new features) — Replies go to your account email, or to the submitter's email if the account has none.

**Voter notifications** (completed features) — Replies go to your account email, or to the admin who marked the feature complete if the account has none.

**Changelog notifications** — Replies go to your account email or a custom address you configure.

This creates natural two-way communication with your users.

## Integration with Slack

If you've connected Slack, certain events also trigger Slack notifications:

- New feature requests
- New private feedback in your Feedback Inbox
- New comments
- Features marked as complete
- Requests reaching 5, 10, 25, 50 or 100 votes

Slack notifications work alongside email — they don't replace it.

## Best Practices

**Notify voters sparingly** — Only send completion notifications for significant features. If you ship 10 small fixes, bundle them into a changelog instead.

**Customize changelog emails** — Use the customization options to add context about the update and make the message feel personal.

**Set clear reply-to addresses** — Make sure your account email is set so users know where replies go.

**Watch your subscriber count** — The publish screen shows your subscribers next to your plan's limit. Upgrade before your list outgrows it.

**Test before sending** — For changelogs, **Send Test Email** sends the email to you only, and **Save for later** keeps the entry as a draft.

## Unsubscribing

Users can unsubscribe from changelog notifications using the link at the bottom of each email. Gmail, Outlook and Yahoo also show their own one-click **Unsubscribe** button next to the sender. This only unsubscribes them from changelog updates — they'll still receive notifications for features they voted on.

If someone marks your changelog email as spam, or the address bounces because it doesn't exist, we unsubscribe them for you. They show as unsubscribed in **Contacts** and stop counting toward your email limit.

There's no way to unsubscribe from feature completion notifications since users explicitly voted for those features and expect to hear when they ship.