The Welcome Email
The one message with reliable attention, used to return the user to an unfinished task.
The problem it solves
Most new users leave mid setup and never come back. The welcome email is the only channel that reaches them, and it is usually spent on a company introduction nobody reads.
A welcome email arrives with more attention than any message that follows. Teams spend it on a founder letter, a feature list and four links. The user was in the middle of something when they left, and the email talks about the company instead.
The version that works is short, addressed to the specific state the user left in, and carries one link that resumes it.
Company letter
- Welcome to the future of team productivity!
- Three paragraphs on the founding story.
- Six links: docs, blog, community, pricing, webinar, app.
- Identical for everyone who signs up.
Resume email
- Your workspace is ready. One step left: connect your calendar.
- Two sentences on what that step unlocks.
- One link, straight to that step, already authenticated.
- Different for someone who connected a calendar and someone who did not.
State awareness is what separates these. Branching on two or three states covers most of the value: user did nothing after signup, user completed setup but produced nothing, user is active. Each state needs a different sentence and a different link, and a user who already finished should get a short acknowledgement rather than a prompt to do what they did.
- Send it within minutes, while the session is still recent enough to resume.
- Under a hundred words in the body, with one action.
- Deep link to the exact unfinished step, not the homepage or the dashboard.
- Send from a person at the company, with a reply address that a person reads.
- Suppress it entirely for users who already reached first value in the same session.
Worked example
Beacon, an alerting tool
Beacon sent a four hundred word welcome with the founding story and seven links. They replaced it with three variants of roughly sixty words each, branched on whether the user had added a monitor. The variant for users with no monitor contains one line about what a monitor does and one link that opens the create form with the fields prefilled from their domain.
One caution about volume. A welcome email is a single message, and the instinct after it works is to build a five part sequence. Each additional message performs worse than the last and raises the chance of an unsubscribe, which costs you the channel for everything that follows.
When it fits
- Products where setup routinely spans more than one session.
- Cases where you can deep link into the exact incomplete step.
- Products with a real person behind the reply address who can answer a question.
- Teams able to branch on at least two or three states of account progress.
When it backfires
- When it is identical for everyone, so active users are told to do what they already did.
- When it links to the homepage rather than the unfinished step, reopening the same dead end.
- When it becomes a five part drip, burning the unsubscribe on messages that matter less than the first.
- When it substitutes for fixing the step people abandon, which the email will keep dragging them back to.
Products using it
Basecamp
Onboarding email has been written as short plain text from a named person with a reply address that reaches a human.
Duolingo
Follow up messages reference the specific streak and lesson state rather than sending a generic welcome.
Dropbox
Early emails have pointed at the specific remaining setup step, such as installing the desktop client.
The psychology under it
The takeaway
Spend the welcome email on one link back to the step the user abandoned, and branch it on what they actually did.
Finished the teardown? Bank it and the day counts toward your run.