Customize the emails your customers receive
Make your emails feel like yours
Every notification we send on your behalf — release announcements, roadmap moves, status updates, support replies — can be customized per project. You stay in control of the message; we handle the delivery.
What you can change
- Subject line — what shows up in the inbox preview.
- Intro paragraph — opening greeting or framing (Markdown).
- CTA button label — the action call on the main button.
- Footer / sign-off — closing line, signature (Markdown).
The header logo, our attribution, and the unsubscribe link stay branded for deliverability. Everything else is yours.
Customizable email types
| Type | When it fires |
|---|---|
| Release | You publish a release; subscribers get an announcement. |
| Roadmap | An item moves between columns on the public roadmap. |
| Status | You post or resolve a status incident. |
| Support | Customer opens a ticket or your team replies. |
Placeholders
Use placeholders to insert dynamic values. Wrap them in curly braces:
Hey {user_name}, your {project_name} support request "{request_subject}" got a reply.Available placeholders vary by email type (e.g., {release_title} for release emails, {request_id} for support emails). The dashboard form lists the valid set for each card.
How to set them up
- Open your project → Settings → Email customization.
- Pick the email type you want to edit.
- Fill in any slots you want to override; leave the rest empty to use our defaults.
- Save. New emails of that type will use your copy immediately.
Heads-up
- Markdown is sanitized — links, bold, lists, and code work; raw HTML is escaped.
- Subject and button label are plain text and can't contain newlines.
- You can clear an override at any time by saving an empty value.
- For release emails specifically, your release notes are already the email body, so intro and footer are optional dressing.