DEV Community

Lalit Kumar Jangid
Lalit Kumar Jangid

Posted on Fully Autonomous

Nine emails every SaaS product sends, and what each one has to say

Every software product sends the same handful of emails. A verification link. A welcome. A receipt. A warning that the trial is ending. They are usually written on the day the feature ships, by the developer who built it, and then nobody reads them again for two years.

That is a waste, because these are the emails your users actually open. Nobody ignores a receipt or a security alert. They are read more carefully than any newsletter you will ever send, and they are often the only writing from your company a customer sees in a normal month.

Below are the nine, in roughly the order a user meets them. For each one: what it is for, what it must contain, and a short example. The examples are written for made-up products, so take the structure and change the details.

1. The verification email

What it is for: proving that the person owns the address they typed.

What it must contain: one link or one code, how long it works, and a line for people who did not sign up.

Subject: Verify your email for Acme

Hi Ana,

Thanks for signing up for Acme. Confirm that this is your email address to finish creating your account.

[Verify my email]

The link works for 24 hours.

If you didn't sign up for Acme, you can ignore this email. No account will be created.

The most common mistake is adding things. A verification email is not the place for a product tour, social links or a discount. One action, then stop.

If you send a code instead of a link, put the code in the subject line: "482 913 is your Kettle verification code". The user can then read it from the notification without opening anything. Say that the code works once and for how long, and add a line that your staff will never ask for it.

2. The welcome email

What it is for: confirming the account exists and pointing to one useful next step.

What it must contain: a plain "your account is ready", one action, and a way to reply.

Subject: Welcome to Acme. Send your first invoice in 2 minutes

Hi Ana,

Your Acme account is ready.

The fastest way to see how it works is to send one real invoice. Add a client, add a line, press send. It takes about two minutes.

[Create my first invoice]

If you get stuck, reply to this email. A person on our team reads every reply.

Pick the single action that shows your product working, and say how long it takes. A list of ten features gives the reader nothing to do.

A second kind of welcome works well alongside it: a short plain-text note from a founder that asks one question, such as "what made you sign up today?" The answers tell you why people come, in their own words.

3. The notification

What it is for: telling a user that something happened in their account.

What it must contain: the event in the subject line, the details, and a link to the exact place.

Subject: Maya commented on "Q4 hiring plan"

Maya Chen commented on Q4 hiring plan:

"Can we move the design hire to January? The budget lands on the 5th."

[Open the document]

You are getting this because you own this document. Change which notifications you get in Settings.

Put the content in the email. If the reader can deal with the comment without opening your app, you have saved them a step, and they will trust the next notification more.

The last line matters as much as the first: say why they got the email and where to turn it off. A notification with no off switch becomes a spam complaint.

4. The security alert

What it is for: letting a user stop something they did not do.

What it must contain: what happened, when, from where, and one button for "this wasn't me".

Subject: New sign-in to your Kettle account

Hi Sam,

Your Kettle account was signed in to from a new device.

Device: Chrome on Windows
Location: Lisbon, Portugal (approximate)
Time: November 13, 10:42 UTC

If this was you, you can ignore this email. If not, change your password now. That signs out every device.

[Change my password]

Set the facts out on separate lines. A person can recognise their own sign-in in two seconds if the device, place and time are easy to see.

Security alerts should be sent whatever the user's notification settings say. They are not marketing and should not have an unsubscribe link.

5. The email change notice

What it is for: the same job as a security alert, for the most sensitive setting in the account.

What it must contain: two emails, not one.

Send a confirmation link to the new address, to prove the person owns it. Send an alert to the old address, so the real owner can cancel a change they did not make.

Subject: The email on your Acme account is being changed

Hi Ana,

Someone asked to change the email on your Acme account from this address to a••••@newmail.com on November 13 at 10:42 UTC.

If this was you, no action is needed.

If this wasn't you, cancel the change now and reset your password.

[Cancel this change]

The alert to the old address is the one that stops an account takeover, and it is the one most products forget. Show only part of the new address, and do not apply the change until the new address has been confirmed.

6. The payment confirmation

What it is for: a record the customer can keep.

What it must contain: amount, date, what it was for, how it was paid, a reference number, and the next charge.

Subject: Receipt for your Acme payment of $29.00

Hi Ana,

We received your payment. Thank you.

Amount: $29.00
Plan: Acme Pro, monthly
Paid on: November 13, 2026
Paid with: Visa ending 4242
Receipt number: AC-20418

Your next payment of $29.00 is on December 13, 2026.

Put the amount in the subject line. Months later, when someone is doing their accounts, that is what they will search for.

The sibling of this email is the failed payment notice. It needs three facts: what failed, when you will try again, and when the service stops. A clear date gets cards updated. A vague "there was a problem with your payment" gets ignored.

7. The trial-ending notice

What it is for: making sure nobody is surprised.

What it must contain: the date, what the user has done so far, and exactly what happens if they do nothing.

Subject: Your Acme trial ends in 3 days

Hi Ana,

Your free trial of Acme ends on Monday, November 16.

So far you have sent 14 invoices and been paid for 9 of them. To keep sending, choose a plan before Monday. Plans start at $12 a month.

If you do nothing, your account is paused, not deleted. Your data stays for 60 days.

The sentence people leave out is the last one. "What happens if I do nothing?" is the first question every reader has, and the answer decides whether they feel informed or trapped.

Showing the user's own numbers does more than any list of features. It reminds them the product is already doing a job for them.

8. The product update

What it is for: telling customers what they can now do.

What it must contain: the benefit first, one example or image, which plans have it, and a link to the feature.

Subject: New in Acme: get paid by card in one click

Hi Ana,

Your clients can now pay an invoice by card, straight from the email you send them. No account, no bank details to type.

It is on for every plan from today. Open any unpaid invoice and choose "Add a pay button".

Lead with what the customer can do, not what the team built. "We rebuilt our payments infrastructure" is news for your engineers. "Your clients can pay by card" is news for your customer.

Send a big launch on its own. Collect the small changes into a monthly round-up of three numbered items.

9. The policy update

What it is for: telling users that your privacy policy or terms are changing.

What it must contain: the effective date, a plain summary of the changes, what stays the same, and a link to the full text.

Subject: We're updating our privacy policy on December 15

Hi Ana,

We are updating the Acme privacy policy. The new version takes effect on December 15, 2026.

What is changing:

  1. We added a section on how payment data is handled by our payment provider.
  2. We now keep deleted invoices for 30 days instead of 90.

What is not changing: we do not sell your data, and you can export or delete it at any time.

Most policy emails say only "we've updated our policy to serve you better", which tells the reader nothing and makes them suspicious. List the real changes. Then say what has not changed, because that is the only question most readers have.

What notice you must give depends on the laws that apply to you, so have a lawyer check the wording.

What the nine have in common

Read them again and the same rules show up each time.

The subject line says what happened. "Receipt for your payment of $29.00." "New sign-in to your account." None of them is clever, because the reader is not being persuaded to open. They are being told what the email is.

Each one has one job. One link, one code, one button. The moment a receipt tries to upsell or a verification email tries to onboard, both jobs are done worse.

Each one answers "what happens next?" The link expires in 24 hours. The next charge is on December 13. Your account is paused, not deleted. Uncertainty is what makes people write to support.

They come from an address someone reads. People reply to these emails with real questions. A no-reply address turns each of those into a support ticket, or into silence.

Two rules about which emails need an unsubscribe link

These nine fall into two groups, and the difference matters.

Verification emails, receipts, security alerts and email change notices are transactional: they answer something the user did, or protect their account. They are sent regardless of marketing preferences and do not carry an unsubscribe link.

Product updates and anything else that promotes the product are marketing. They need an unsubscribe link and should only go to people who agreed to receive them.

Activity notifications sit in between: they are about the user's own account, but the user should be able to switch them off in settings.

Keep the two groups apart when you send, ideally on separate sending streams. If your product updates annoy people into marking them as spam, you do not want your password resets to pay for it.

Where to start

You do not need to rewrite all nine this week. Open your own product, trigger each email, and read it as a customer would. Ask three questions of each one:

  1. Does the subject line say what this is?
  2. Is there exactly one thing to do?
  3. Does it say what happens next?

Fix the ones that fail. It is an afternoon of work, and these are the emails every one of your users will read.


We build Cresca, an email platform for marketing campaigns and transactional email. Longer versions of these examples, with subject lines and templates you can copy, are on our email examples page.

Top comments (0)