Setting the file. One moment.
Transactional Email Catalog · Email Best Practices · resend/resend-skills · Skills Docs
A comprehensive catalog of transactional emails organized by category, plus recommended email combinations for different app types.
Planning what transactional emails your app needs
Choosing the right emails for your app type
Understanding what content each email type should include
Back to the top of the page
Implementing transactional email features Use these combinations as a starting point based on what you’re building.
Apps where user accounts and security are core (login systems, identity providers, account management).
Email verification
Password reset
OTP / 2FA codes
Security alerts (new device, password change)
Account update notifications
Welcome email (must not be promotional)
Account deletion confirmation
Apps focused on content delivery and subscriptions.
Email verification
Password reset
Welcome email (must not be promotional)
Subscription confirmation
OTP / 2FA codes
Account update notifications
Apps where users buy products or services.
Email verification
Password reset
Welcome email (must not be promotional)
Order confirmation
Shipping notifications
Invoice / receipt
Payment failed notices
OTP / 2FA codes
Security alerts
Subscription confirmations (for recurring orders)
Apps with paid subscription tiers and ongoing billing.
Email verification
Password reset
Welcome email (must not be promotional)
OTP / 2FA codes
Security alerts
Subscription confirmation
Subscription renewal notice
Payment failed notices
Invoice / receipt
Account update notifications
Feature change notifications (for breaking changes)
Apps handling money, payments, or sensitive financial data.
Email verification
Password reset
OTP / 2FA codes (required for sensitive actions)
Security alerts (all types)
Account update notifications
Transaction confirmations
Invoice / receipt
Payment failed notices
Welcome email (must not be promotional)
Compliance notices
Apps focused on user interaction and community features.
Email verification
Password reset
Welcome email (must not be promotional)
Security alerts
OTP / 2FA codes
Account update notifications
Activity notifications (mentions, replies)
Apps targeting developers with API access and integrations.
Email verification
Password reset
OTP / 2FA codes
Security alerts
API key notifications (creation, expiration)
Subscription confirmation
Payment failed notices
Welcome email (must not be promotional)
Usage alerts (approaching limits)
Feature change notifications
Apps handling protected health information.
Email verification
Password reset
OTP / 2FA codes (required)
Security alerts (all types, detailed)
Account update notifications
Appointment confirmations
Welcome email (must not be promotional)
Compliance notices
Note: Healthcare apps have strict requirements. Emails should contain minimal PHI and link to secure portals for sensitive information.
When to send: Immediately after user signs up or changes email address.
Purpose: Verify the email address belongs to the user.
Clear verification link or code
Expiration time (typically 24-48 hours)
Instructions on what to do
Security notice if link is clicked by mistake
Send immediately (within seconds)
Include expiration notice
Provide resend option
Link to support if issues
When to send: When user requests two-factor authentication code.
Purpose: Provide time-sensitive authentication code.
The OTP code (clearly displayed)
Expiration time (typically 5-10 minutes)
Security warnings
Instructions on what to do if not requested
Send immediately
Code should be large and easy to read
Include expiration prominently
Warn about sharing codes
Provide “I didn’t request this” link
When to send: When user requests password reset.
Purpose: Allow user to securely reset forgotten password.
Reset link (with token)
Expiration time (typically 1 hour)
Security warnings
Instructions if not requested
Send immediately
Link expires quickly (1 hour)
Include IP address and location if available
Provide “I didn’t request this” link
Don’t include the old password
When to send: When security-relevant events occur (login from new device, password change, etc.).
Purpose: Notify user of account security events.
What happened (clear description)
When it happened
Location/IP if available
Action to take if suspicious
Link to security settings
Send immediately
Be clear and specific
Include actionable steps
Provide way to report suspicious activity
When to send: Immediately after successful account creation and verification.
Purpose: Welcome new users and guide them to next steps (must not be promotional).
Welcome message
Key features or next steps
Links to important resources
Support contact information
Send after email verification
Keep it focused and actionable
Don’t overwhelm with information
Set expectations about future emails
When to send: When user changes account settings (email, password, profile, etc.).
Purpose: Confirm account changes and provide security notice.
What changed
When it changed
Action to take if unauthorized
Link to account settings
Send immediately after change
Be specific about what changed
Include security notice
Provide easy way to revert if needed
When to send: Immediately after order is placed.
Purpose: Confirm order details and provide receipt.
Order number
Items ordered with quantities
Pricing breakdown
Shipping address
Estimated delivery date
Order tracking link (if available)
Send within minutes of order
Include all order details
Make it easy to print or save
Provide customer service contact
When to send: When order ships, with tracking updates.
Purpose: Notify user that order has shipped and provide tracking.
Order number
Tracking number
Carrier information
Expected delivery date
Tracking link
Shipping address confirmation
Send when order ships
Include tracking number prominently
Provide carrier tracking link
Update on major tracking milestones
When to send: After payment is processed.
Purpose: Provide payment confirmation and receipt.
Invoice/receipt number
Payment amount
Payment method
Items/services purchased
Payment date
Downloadable PDF (if applicable)
Send immediately after payment
Include all payment details
Make it easy to download/save
Include tax information if applicable
When to send: When user subscribes or changes subscription.
Purpose: Confirm subscription details and billing information.
Subscription plan details
Billing amount and frequency
Next billing date
Payment method
Link to manage subscription
Send immediately after subscription
Clearly state billing terms
Provide easy cancellation option
Include support contact
When to send: Before subscription renews (typically 3-7 days before).
Purpose: Notify user of upcoming renewal and charge.
Renewal date
Amount to be charged
Payment method on file
Link to update payment method
Link to cancel if desired
Send with enough notice (3-7 days)
Be clear about amount and date
Make it easy to update payment method
Provide cancellation option
When to send: When subscription payment fails.
Purpose: Notify user of payment failure and provide resolution steps.
What happened
Amount that failed
Reason for failure (if available)
Steps to resolve
Link to update payment method
Consequences if not resolved
Send immediately after failure
Be clear about consequences
Provide easy resolution path
Include support contact
When to send: When a feature the user is using changes significantly.
Purpose: Notify users of changes that affect their use of the service.
What changed
How it affects the user
What action (if any) is needed
Link to more information
Only for significant changes
Focus on user impact
Provide clear next steps
Link to documentation
Note: General feature announcements are marketing emails. Only send as transactional if the change directly affects an active feature the user is using.
Reference