If half of new signups churn in the first week, it’s time to redesign your onboarding messages. The 7 days after signup decide whether a user first feels the value of your product. In this window, the order and timing of messages matter more than how many you send.
The big picture of seven days
The key is to ask for just one action per day. If you tell users several things at once, they do nothing.
Onboarding isn’t a job you build once and finish. Each week, check how many users move from each step after signup to the next, and fix the messages at the biggest drop-off points first. Small fixes add up and noticeably lower first-week churn.
- Day 0: Welcome and one first task
- Day 1: Try the easiest core feature
- Day 3: A use case from a similar customer
- Day 5: Check where they’re stuck and offer help
- Day 7: Summary of results so far and the next step
Timing follows behavior
Sends that respond to behavior work far better than sends tied to the calendar. Telling a user who has already used the core feature to “get started” actually costs you trust. Build branches that skip or swap the next message based on behavior.
Put just one button at the end of each message. If there are several places to click after reading, users click none. Button labels work better when they show what happens next, like “Create your first project,” rather than “Learn more.”
The goal of onboarding isn’t to explain your product to users; it’s to let them experience a first success.
The Story Light editorial team
Meet them outside email, too
In-app guidance, checklists, and empty-state copy are part of onboarding too. Email complements this experience, so keep a balance and don’t rely on email alone for all guidance.
Onboarding messages need a human voice. Even if they’re sent automatically, keep guidance short and signed by a real team member, and let users know a person reads their replies. The moment a stuck user leaves a question is your biggest chance to convert.
What to check in each message
When building a 7-day sequence, first decide for each message the one thing the user should do after reading it, and cut the rest. The subject line should show the benefit of that action in one line, and the body only needs to be short enough to read without scrolling. Whenever you’re tempted to introduce every feature, go back and ask what today’s one thing is.
Send time is worth checking as well. Work-related products tend to do better in the morning when users start work, personal products in the relaxed evening hours. It varies by industry, though, so start by sending at two or three different times and find what suits your customers.
The sender name and reply address are easy to overlook. Email from a send-only address gives the impression that replies aren’t expected, so using an address that actually receives replies raises trust in your onboarding. That’s because this reply address is the easiest channel for users to leave a question. Decide ahead of time who reads replies and how soon they’ll answer.
How to bring stuck users back
A user who hasn’t reached a first success after a week is more likely stuck somewhere than uninterested. Rather than repeating the same guidance to these users, it works better to ask where they got stuck and offer choices. For example, a simple pick such as “Was setup difficult, or is this not something you need yet?” makes it easy for them to respond.
It helps to branch the next message based on the response. The follow-ups can be organized like this.
- For “setup was difficult,” send a short tutorial video or a guide link
- For “not needed right now,” ask whether they’d like to hear from you in a month
- For no response, send one email in which a team member offers help personally
- If there’s still no response, stop sending and quietly remove them from the list
Deciding when to give up is part of onboarding design, too. Continuing to email unresponsive users damages your sender reputation and keeps even the messages that matter from being read.
Removing users who have left may feel unwelcome, but it’s also a choice that gives a better experience to the users who do respond. Later, when you have news worth sharing, such as a new feature or a pricing change, reaching out once more is enough.
Summary
The retention of users who experience a “first success” within 7 days of signup is often markedly different from those who don’t. Start by defining what a first success is in your product, then build the shortest path to it.
Add your first comment to this post