Transactional Emails for SaaS: What to Send
Emails are part of the product. The welcome, the trial reminder, the receipt and the ‘we miss you’ note often decide whether a user comes back. They also have to reach the inbox, which now depends on meeting mailbox providers’ rules.
Which emails should a SaaS product send?
Most SaaS products need a small set: verification, welcome with the first step, onboarding nudges tied to activation, invites, trial ending, receipts and failed payments, and a re-engagement email for inactive users. Each should have one purpose, one main button, and a link that lands on the exact screen it mentions.
What should a welcome email look like?
A welcome email should confirm the account, name the one next step that leads to value, and make it a button. Skip the feature tour; the product can teach that.
Your workspace is ready. The fastest way to see Fieldnote work is to schedule one real job, which takes about two minutes.
Schedule your first jobYou can import your existing jobs from a spreadsheet at any time. Reply to this email if you get stuck; a person reads every reply.
Send it immediately after signup, and from an address people can reply to. Replies to welcome emails are some of the most useful feedback you will get.
Which emails matter most after signup?
After signup, the emails tied to activation and revenue matter most. The table lists the core set with timing and the one action each should drive.
| When | Main action | |
|---|---|---|
| Verification | Immediately | Verify email |
| Welcome | Immediately | Do the first meaningful task |
| Activation nudge | If not activated after a day or two | Finish the step they stopped at |
| Invite | When a teammate is invited | Join the item they were invited to |
| Trial ending | Several days before, and the day before | Choose a plan, or know what happens |
| Receipt | After each payment | Download invoice |
| Failed payment | After a failed charge, then before the deadline | Update card |
| Re-engagement | After a period of inactivity | See what changed, or one quick win |
What do mailbox providers require?
Gmail’s sender guidelines require all senders to authenticate with SPF or DKIM and keep spam rates below 0.3%; senders of more than 5,000 messages a day to Gmail must also use SPF, DKIM and DMARC and support one-click unsubscribe for marketing messages (Google’s email sender guidelines). Keep transactional emails separate from marketing, and include your business address and a way to manage preferences. Canadian senders must also follow CASL for commercial messages.
One email, one job, one button.
An email that tries to announce features, request a review and push an upgrade does none of them.
How do you measure transactional emails?
Measure the action each email exists for, not opens: verified accounts, activated users, accepted invites, recovered payments and reactivated users. Opens are unreliable as a metric. The screens these emails link to are covered on onboarding, team invites, billing and cancellation.
Frequently asked questions
What transactional emails should a SaaS app send?
Verification, welcome, activation nudges, invites, trial ending, receipts, failed payments and re-engagement.
What should a SaaS welcome email include?
Confirmation, one next step that leads to value as a button, and a way to reply to a person.
What are Gmail’s rules for bulk senders?
Senders of more than 5,000 messages a day must use SPF, DKIM and DMARC, support one-click unsubscribe and keep spam rates below 0.3%.
How should SaaS emails be measured?
By the action each email drives, such as activation or recovered payments, not opens.
When should trial-ending emails be sent?
Several days before and the day before the trial ends, saying clearly what will happen.
Should transactional emails include marketing?
Keep them separate, and respect marketing opt-outs and consent rules.
Sources & further reading
Standards and platform rules change. These sources let you verify the current requirements directly. All screens shown are mock-ups of fictional products.