Transactional Email Examples: 12 Every SaaS Needs

Every SaaS sends emails people expect the moment they act: sign up, forget a password, pay, invite a colleague. These are transactional emails.

This guide lists 12 transactional email examples every SaaS needs: when each one is sent, what to put in it and a sample subject line, with a link to a full guide for each. At the end there's one message you can send Claude Code to set up the whole set. It's written for people building with Claude Code who don't write code themselves.

What counts as a transactional email?

A transactional email is an automatic, one-to-one message sent because of something a person did, or something that changed in their account. A password reset, a receipt and a team invite are transactional. A launch announcement or a discount code is marketing.

US rules draw a similar line. The FTC's CAN-SPAM guide treats an email as transactional when its main purpose is to complete or confirm a deal the person already agreed to, share security information, update them on their account or subscription, or deliver something they signed up for. It reads those categories narrowly: an email that's mostly promotion counts as marketing. More on transactional vs marketing emails.

Which 12 transactional emails does a SaaS need?

Not every SaaS needs all 12 on day one. If you're not sure which fit yours, let Claude Code plan the set for your SaaS.

Which emails help people sign up and sign in?

Set these five up first.

1. Welcome email

Sent right after someone creates an account. Include a short thank-you, the one next step that gets them value fastest, a sign-in button and where to get help. Save tips and tours for later onboarding emails.

SubjectWelcome to YourCompany, Alex

Hi Alex,

Thanks for signing up. The quickest way to get going is to create your first project. It takes about two minutes.

Create your first project

If you get stuck, reply to this email and a real person will help.

The YourCompany team

Guides: sending a welcome email on sign-up, welcome email examples and SaaS onboarding emails.

2. Email verification

Sent after sign-up, and again when someone changes their address. Include one button to confirm, how long the link works, and what to do if they didn't sign up.

Example subject line: Confirm your email for YourCompany

Guide: adding email verification to your sign-up flow.

3. Password reset

Sent when someone asks to reset their password. Include a single reset link, how long it lasts, and a line saying they can ignore the email if they didn't ask. Never put a password in an email. OWASP, a respected web security project, recommends links that work once and expire, plus a short follow-up confirming the password was changed. It also suggests the "Forgot password" page shows the same message whether or not an account exists.

SubjectReset your YourCompany password

Hi Alex,

Someone asked to reset the password for your YourCompany account. Use the button below to choose a new one. The link works once and expires in 1 hour.

Reset password

If you didn't ask for this, you can ignore this email. Your password won't change.

The YourCompany team

Guides: setting up password reset emails and password reset email templates.

4. Magic link login

A magic link is a one-time sign-in link sent by email, so people log in without a password. It's sent each time someone asks to sign in. Include a sign-in button, how long the link lasts, and a note to ignore it if they didn't ask.

Example subject line: Your sign-in link for YourCompany

Guide: adding magic link login.

5. Team invite

Sent when a user invites a colleague. Include who sent it, the team's name, one line on what YourCompany does (the person invited may not know), an accept button, and when the invite expires.

Example subject line: Sam invited you to the Marketing team on YourCompany

Guide: sending team invite emails.

Which emails cover payments and billing?

If you take payments with Stripe, a payment service many SaaS products use, Stripe can send some of these itself. Receipts are switched on under Settings, then Business, then Customer emails in Stripe's dashboard. Stripe Billing can also send failed payment emails, a trial reminder 7 days before a trial ends, and renewal reminders.

Decide for each email whether Stripe or your SaaS sends it, so customers never get two copies. See sending your own emails after a Stripe payment.

6. Order confirmation and receipt

Sent after a payment succeeds, not when checkout opens (Stripe also only sends receipts for successful payments). Include what they bought, the amount, the date, a link to the receipt or invoice, and how to contact you.

Example subject line: Your YourCompany receipt for October

Guides: order confirmation emails, emailing invoices automatically and sending PDFs and other attachments.

7. Subscription confirmation

Sent when someone starts, changes or cancels a plan. Include the plan name, price, billing frequency, next billing date and how to change or cancel. For a cancellation, say exactly when access ends.

Example subject line: You're on the YourCompany Pro plan

Guide: sending subscription confirmation emails.

8. Payment failed

Sent soon after a card payment fails, with one or two follow-ups before anything changes on the account. Say what happened in plain words, add a button to update their card, and explain what happens next and when. Never ask for card details in the email itself.

Example subject line: Your YourCompany payment didn't go through

Guide: sending payment failed emails.

9. Trial ending and renewal reminder

Sent a few days before a free trial ends, and before an annual plan renews. Include the date, what they'll be charged, what they keep or lose, and how to change or cancel.

Example subject line: Your YourCompany trial ends on Friday

Guide: trial ending and renewal reminder emails.

Which emails keep you and your users up to date?

The last three keep everyone informed. Two of them go to you.

10. New sign-up notification

Sent to you each time someone signs up. Include their name, email, plan and anything else you ask at sign-up. As sign-ups grow, switch to a daily summary.

Example subject line: New sign-up: Priya, Pro trial

Guide: getting notified when someone signs up.

11. Form submission email

Sent when someone fills in your contact, demo or feedback form. Usually there are two emails. Yours holds their answers, with the reply-to set to their address so pressing Reply reaches them. The optional one to them confirms you got their message and when to expect a reply.

Example subject line: New contact form message from Jordan

Guides: getting an email for every form entry and making your contact form send emails.

12. Weekly summary

Sent on the same day each week. Include the few numbers that matter to that user, what changed, and one link back into your SaaS. Let people switch it off in their settings, and keep it about their account rather than promotions.

Example subject line: Your week on YourCompany: 3 new projects, 12 comments

Guide: sending a weekly summary email.

What other emails might your SaaS need?

Depending on your product, you may need a few more:

• Booking tools need a confirmation with a calendar invite, plus a reminder. See booking confirmation emails.
• Pre-launch products need a waitlist confirmation. See waitlist confirmation emails.
• Most SaaS products benefit from a new-device sign-in alert, and an "export ready" email if users can download their data.

What do good transactional email examples have in common?

The same habits apply to all 12:

• The subject says what it is. "Your receipt for October" beats "Thanks from YourCompany".
• One main action, with one clearly labelled button.
• It arrives fast. Resets and sign-in links are often opened within seconds.
• The sender is recognizable: your product's name and an address on your own domain, such as hello@yourcompany.com.
• Promotion stays out, or small and at the end.
• It's tested first. See testing your emails before users see them.

How do you set up all 12 at once?

With SimpleSends connected, you can brief Claude Code on the whole set in one message.

SimpleSends is a transactional email service built for people who build with Claude Code but don't write code. It connects through an MCP server, a standard way for AI tools to plug into other services (see what MCP is). In Claude, this kind of connection is called a connector.

1. Sign up on the SimpleSends website and follow the steps there to set up the email address you'll send from. To send from your own domain, this includes adding a few DNS records (settings that tell the internet how your domain's email works) where your domain is registered.
2. In Claude Code, open Customize, then Connectors, choose Add, then Add custom connector, and fill in:

3. When Claude prompts you to connect, log in to SimpleSends.
4. Back in the Claude Code chat, tell Claude Code: "I've connected SimpleSends for all transactional email." It takes it from there, including adding what your project needs to send email.

Then send the brief:

I'd like to set up all the transactional emails my SaaS needs. Look at my product and suggest which of these fit: welcome, email verification, password reset, magic link login, team invite, order confirmation and receipt, subscription confirmation, payment failed, trial ending and renewal reminders, a new sign-up notification to me, form submission emails and a weekly summary. Show me the list with when each one goes out. Then draft the wording and design for each, matching the look of my site, friendly and clear. I'd like to approve every email before it goes live.

What to expect: Claude Code replies with a plan of the emails that fit and when each is sent (more on timing each email). Once you approve, it drafts each email, sends test copies to your inbox from the chat, and makes changes when you ask. Then it builds each one into your SaaS. From then on, real emails go out from your live project on their own, without the chat.

Later changes are a message too (see briefing Claude Code like a copywriter). If a user says an email never arrived, ask Claude Code to check the send logs in SimpleSends and explain what happened. For the full picture, read transactional emails in Claude Code.