Setting the file. One moment.
Skill 02 · Email Best Practices
Subchapter 2.10
references/transactional-emails.mdMarkdown2 KBView on GitHub
Clear, actionable emails that users expect and need—password resets, confirmations, OTPs.
Be specific and include context:
| ✅ Good | ❌ Bad |
|---|---|
| Reset your password for [App] | Action required |
| Your order #12345 has shipped | Update on your order |
| Your 2FA code for [App] | Security code: 12345 |
| Verify your email for [App] | Verify your email |
Include identifiers when helpful: order numbers, account names, expiration times.
The text snippet after subject line. Use it to:
Keep under 90 characters.
Above the fold (first screen):
Hierarchy: Header → Primary message → Details → Action button → Secondary info
Format: Short paragraphs (2-3 sentences), bullet points, bold for emphasis, white space.
60%+ emails are opened on mobile.
| Field | Best Practice | Example |
|---|---|---|
| From Name | App/company name, consistent | [App Name] |
| From Email | Subdomain, real address | hello@mail.example.com (opens in a new tab) |
| Reply-To | Monitored inbox | support@example.com (opens in a new tab) |
Avoid noreply@ - users reply to transactional emails.
OTP/Verification codes:
Buttons:
Resend functionality:
Expired links:
“I didn’t request this”: