Skip to content
All Articles
Email Deliverability

SaaS Email Deliverability: Transactional, Onboarding, and Notification Best Practices

SaaS products send dozens of email types: welcome emails, trial reminders, feature updates, billing. Learn how to set up email infrastructure that handles all of them reliably.

6 min read

The SaaS email stack

A typical SaaS product sends multiple categories of email, each with different deliverability requirements:

Transactional: Signup confirmations, email verification, password resets, 2FA codes, payment receipts — must reach inbox instantly

Onboarding/lifecycle: Welcome series, feature tours, setup reminders — high stakes for product adoption

Product notifications: Usage alerts, team invites, comment notifications — moderate volume, personalized

Marketing: Blog updates, feature announcements, case studies — promotional, permission-based

Billing: Invoice emails, renewal reminders, payment failure notices — must reach inbox

Separate streams by importance

Route email into priority tiers:

Tier 1 (critical): Transactional and billing — dedicated IP or premium ESP with transactional focus (Postmark, SparkPost). No shared pool risk.

Tier 2 (important): Onboarding and lifecycle sequences — separate sending domain (e.g., app.yoursaas.com) via product email tool (Customer.io, Brevo, Postmark)

Tier 3 (marketing): Newsletters and announcements — separate domain (e.g., news.yoursaas.com) via marketing ESP (Mailchimp, Klaviyo, Campaign Monitor)

Separate domains protect your primary domain reputation and allow independent monitoring.

Startup Stack (< 10k emails/day)

  • Single sending domain for all email types
  • Shared IP pool via Mailgun or SendGrid free tier
  • Basic SPF + DKIM only
  • DMARC p=none monitoring
  • Single ESP for transactional + marketing
  • Manual blacklist checks

Scale Stack (> 100k emails/day)

  • Separate subdomains: transactional, product, marketing
  • Dedicated IPs warmed per stream
  • SPF + DKIM + DMARC p=reject enforced
  • DMARC aggregate reports processed weekly
  • Postmark or SparkPost for transactional; Klaviyo for marketing
  • Automated 15-min blacklist monitoring with alerts
  • SPF record includes all sending services (primary domain + each subdomain)
  • DKIM enabled in every ESP with 2048-bit keys
  • DMARC published at minimum p=none with rua= reporting
  • ·Transactional email on dedicated IPs or isolated IP pool
  • Email verification required before onboarding emails are sent
  • ·Automated blacklist monitoring for each sending domain and IP
  • Bounce handler configured to suppress hard bounces immediately
  • ·Spam complaint feedback loop registered with Gmail and Yahoo

Email verification at signup

Require email verification before sending any other email. This: - Confirms the address is real and accessible - Prevents typo addresses from entering your system - Creates a confirmed opt-in record - Removes addresses that generate bounces immediately

Implement rate limiting on verification resend requests to prevent abuse. After 3-5 failed verification attempts, require manual support intervention.

Monitoring for SaaS

Critical metrics for SaaS email:

Verification email delivery rate: If below 95%, investigate immediately — users can't onboard

Password reset delivery time: Should arrive within 30 seconds. Delays indicate throttling or filtering.

Blacklist status: Check daily for sending IPs and sending domains

Authentication validity: Any break in SPF, DKIM, or DMARC can immediately affect delivery across all email tiers

Bounce rate by email category: High bounces on marketing signals list quality issues; high bounces on transactional signals a systemic infrastructure problem

Check your domain's email health

Run a free scan against 60 blacklists. Validate SPF, DKIM, DMARC, and MX records in seconds.