Welcome Email Examples (By Signup Context)

User signed up, hit a paywall-free trial, has not done anything yet.

Hi {{first_name}},

Welcome to {{ProductName}}.

Start here to reach {{aha_moment}}: {{first_action_link}}

Estimated time: {{time_estimate}}.

Reply if anything looks broken.

{{Sender name}}

One next action and one time estimate. Names the aha-moment outcome. Reply invitation in case anything is broken.

Single CTA. Specific time estimate ("90 seconds to first send"). A founder line for the first 1,000 signups.

A welcome that lists every feature. Multi-step drips that fire before the user has logged in once.

User joined the waitlist for a product not yet generally available.

Hi {{first_name}},

You are on the waitlist for {{ProductName}}.

Access invites will go out in {{rough_eta}}.

Until then, only product updates that affect launch timing will land here.

{{Sender name}}

Confirms what they did. Sets a soft expectation for when they will hear next. Avoids any marketing pretense.

Plain text. One-sentence paragraphs. A signed-from-founder line. A note on what they will hear about and roughly when.

Long backstory. Founder vision essay. Unsolicited social-proof links. They opted in for a wait, not a pitch.

User subscribed to a newsletter, not to a product.

Hi {{first_name}},

Welcome to {{newsletter_name}}.

Cadence: {{cadence}}
Topic: {{topic}}
Audience: {{reader_type}}

Start with this back issue: {{best_issue_link}}

Next send: {{next_send_day}}

{{Sender name}}

Sets cadence and topic. Anchors the relationship before sending the first issue. Optional: links to the best back-issue.

Cadence ("Tuesdays"). Topic. The kind of reader you write for. A "best of" issue link.

A 4-email drip before the next regular issue. Pitching a product they did not sign up to hear about.

User filled a contact or demo form. Sent quickly so it does not feel automated.

Hi {{first_name}},

Here are three times for a {{ProductName}} walkthrough:

1. {{time_option_one}}
2. {{time_option_two}}
3. {{time_option_three}}

Or use this calendar link: {{calendar_link}}

The call will cover {{call_scope}}.

{{Sender name}}

Treats the user as a buyer in motion, not a lead in a queue. Names a real human, gives real times, and leaves a fallback to reply.

A real first name. 3 specific time slots. A direct calendar link. A short line on what the call will cover.

A no-reply sender. A 24-hour response stall. A long qualification form before the call.

User joined because someone on their team invited them.

Hi {{first_name}},

{{Inviter_name}} added you to {{Workspace}} in {{ProductName}}.

Open the workspace here: {{workspace_link}}

{{Sender name}}

Leads with the inviter and the workspace, not the product. The user already has context; the email confirms it.

Inviter name and workspace name in the subject and lede. A direct link into the workspace they were added to.

A generic product welcome that ignores the inviter. Asking the user to re-onboard from scratch.

A developer signed up and generated their first API key.

Hi {{first_name}},

Your {{ProductName}} API key is ready: {{api_key_link}}

First send:

curl -X POST {{api_endpoint}} \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{{example_payload}}'

Docs: {{docs_link}}

{{Sender name}}

Recognizes the audience. Links straight to docs and a curl example. Does not waste their time with marketing copy.

A 4-line curl example. A docs link to the most-relevant endpoint. A reply line for support questions.

A product tour for someone who just wants to ship code. A welcome from a marketing alias.

Existing free user just upgraded to a paid plan.

Hi {{first_name}},

Your {{ProductName}} workspace is now on {{Plan}}.

Unlocked now:

1. {{unlocked_feature_one}}
2. {{unlocked_feature_two}}
3. {{unlocked_feature_three}}

Billing portal: {{billing_portal_link}}

{{Sender name}}

Confirms the upgrade. Names the new things they unlocked. Treats them like a paying customer, not a new signup.

A list of what is now unlocked. A direct link to the first paid-tier-only feature. A billing-portal link.

A "thank you for your business" form letter. A re-onboarding flow they already completed.

User was inactive for a while, came back, did the setup again.

Hi {{first_name}},

Welcome back to {{ProductName}}.

Since your last active session, these changed:

1. {{change_one}}
2. {{change_two}}
3. {{change_three}}

Start here: {{most_relevant_link}}

{{Sender name}}

Acknowledges the return without making it weird. Names what is new since they were last around.

A short list of meaningful changes since they were last active. A direct link to the area most relevant to them.

Acting like they have never been there. Surveys asking why they left.