Transactional
A transactional email is functional. It is triggered by an event and usually is a short single message and call to action.
Requirements
See the overview below outlining the required components, their variations, and any optional add-ons that may be needed.
| Component | Quantity | Description | Required |
|---|---|---|---|
| Header | x 1 | Use the Stack Overflow wordmark and icon at the top of every email. | |
| Headline (2 variants) | x 1 | Keep headline copy ideally under 50 characters and make the core message clear without relying on body text. | |
| Text block + primary CTA | x 1 | Body copy can be longer but should stay concise, include links where needed, and focus on one clear CTA per transactional email. | |
| Footer | x 1 | End all emails with a simple branded footer and utility links. | |
| Illustration | x 1 | Optional branded illustration for additional context. Use no more than one. | |
| Alert | x 1 | Optional secondary message not directly tied to the primary communication. Keep copy under 150 characters where possible and use no more than one. |
Short
Compiling…
Long
Compiling…