Welcome email examples: 5 originals you can adapt

The welcome email is the only message you will ever send with close to guaranteed attention: the subscriber asked for it seconds ago. Every issue after this one lands in a crowded inbox and competes. This one arrives while the person is still thinking about you, and what you do with that attention decides whether issue two gets opened. It also shapes something less visible: how Gmail scores the next thousand emails your domain sends.

This article assumes people can already subscribe to you. If you are still wiring that up, start with our guide to running a newsletter on your own domain and come back for this part.

The three jobs of a welcome email

A welcome email that works does three things. Everything else is decoration.

First, deliver the promise. If the signup form offered a guide, the guide is the first line, not paragraph four. If it offered a weekly digest, hand over the best of the archive right now so the subscriber gets value before the first scheduled issue. An empty "thanks for subscribing" wastes the one send with guaranteed attention.

Second, set expectations. What arrives, how often, from which address. A subscriber who knows the Tuesday issue is coming does not mark it as spam on Tuesday. Asking them to add your address to their contacts is worth one line here; a contact add is a small positive signal and it costs nothing to ask.

Third, ask for a reply. One question, specific and easy. This is the deliverability play, and it is the part most welcome emails skip. Mailbox providers rank engagement in a clear order: replies above clicks, clicks above opens. A reply tells Gmail this sender is a correspondent, not a broadcaster, and that judgment matters most in the first weeks, while a new domain's reputation is still forming (reputation on a fresh domain matures over 4 to 8 weeks). "Let me know your thoughts" gets no replies. "What made you subscribe today?" gets some, and you only need some.

Send it instantly, from an address that answers

Timing is simple: the welcome fires the moment the subscription completes, not in tonight's batch. Fifteen minutes later the person has moved on and your carefully written email is just another unread row.

The From address matters more than most people think. Never send a welcome from noreply@. It contradicts the email's own reply prompt, and a subscriber who replies anyway gets a bounce as their first interaction with you. Use a real address: hello@, yourname@, editor@. On LetterDuck an address is a routing rule, not a paid seat, so a dedicated hello@yourdomain costs nothing, and replies thread into a shared inbox where you answer as that address.

Double opt-in makes it a two-part welcome

If you confirm subscriptions (we think you should, and we wrote out the double opt-in math separately), the welcome becomes two emails with two different jobs. Part one is the confirmation: one sentence, one button, no marketing. Part two is the welcome proper, and it fires the instant the confirmation click lands. Do not merge them. An unconfirmed address might be a typo or a bot, so welcome content is wasted on it, and anything you add to the confirmation dilutes its single job, which is the click.

Five welcome emails, written by us

The usual "welcome email examples" post is screenshots of other companies' mail. These five are originals we wrote for the newsletter shapes we see most, in the plain register we argue for in how to write a newsletter. Steal any of them.

1. The personal essay newsletter

Subject: You're in. Here's the deal.

You subscribed to [Name], so here is exactly what that means.

One essay, most Fridays, usually about [topic]. No roundups,
no sponsor breaks between paragraphs. When I have nothing
worth your time, I skip the week.

Start with the piece people share most:
[link to your best essay]

One question before you go: what made you subscribe today?
Hit reply and tell me. I read everything.

[Your name]

The cadence carries an honest escape clause. "I skip the week" builds more trust than an "every Friday" you will not keep. One link, one question, done.

2. The curated links digest

Subject: Welcome. Your first five links are inside.

Every Tuesday: five links on [niche], each with two sentences
on why it matters. Fifteen minutes of reading, tops.

So you don't have to wait a week, five from the archive:

- [Link]: one line on why it mattered
- [Link]: one line
- [Link]: one line
- [Link]: one line
- [Link]: one line

Reply with the best thing you read this month and it might
make next Tuesday's issue, credited to you.

[Name]

A curation newsletter can deliver its product inside the welcome itself, so it should. The reply prompt doubles as sourcing.

3. The indie product changelog

Subject: Subscribed: [Product] updates, monthly-ish

You'll get an email when we ship something worth telling you
about. In practice that is about once a month. No feature
votes, no "we've been quiet lately" filler.

Last month we shipped [feature]: [one line on what it does].
Full changelog: [link]

What is the one thing [Product] doesn't do that you wish it
did? Reply and it goes straight into the planning doc.

[Founder name], [Product]

"Monthly-ish" is an honest cadence for a changelog, and the reply prompt is roadmap research you would otherwise pay for.

4. The local newsletter

Subject: Welcome to [Name]. First question: where do you live?

Twice a week, everything worth knowing in [town]: council
decisions, openings and closings, and the stories the
regional paper skips.

Reply with your neighborhood and I'll keep a closer eye on
it. Not a gimmick: half our best stories start as reader
replies.

While you wait for Thursday's issue, the three most-read
stories this year: [links]

The reply prompt sits in the subject line itself. A local newsletter runs on reader tips, so the deliverability signal and the editorial engine are the same mechanism.

5. The paid newsletter with a free tier

Subject: You're on the free list. Here is exactly what that means.

Free: the Monday issue, every week, full length.
Paid ([price]/month): Thursday deep dives plus the archive.

No guilt trips. The Monday issue has to earn the upgrade on
its own.

Read the deep dive most subscribers upgrade for, free
for new readers: [link]

Reply if the link is broken or you have a question about
[topic]. A human answers, usually me, usually same day.

Drawing the free/paid line in the welcome prevents the churn that surprise paywalls cause later. The free sample does the selling so the copy does not have to.

Before you turn it on

Run the finished email against this list:

• It fires instantly on confirmation (or on signup, if you run single opt-in).
• It comes from a real address a human reads.
• The signup form's promise is delivered in the first two lines.
• The cadence is stated in plain words, with honest hedges.
• There is exactly one question, and it is easy to answer.
• The subject line does its own work; if it reads like a receipt, borrow from our notes on newsletter subject lines.

Then send yourself a test, read it on a phone, and answer honestly: would you reply to this? If not, cut it in half and sharpen the question.