Many lifecycle programmes are really email programmes. Email is reliable, flexible and familiar, so it ends up carrying every message, from urgent reminders to detailed guides. But customers don't live in their inbox. The best lifecycle programmes use each channel for what it's genuinely good at, and orchestrate them so they work together.
Here's how we think about the role of email, push notifications and in-app messages, and how to decide which to use for each message.
- Detailed guidance
- Persistent reminders
- Rich educational content
- Timely prompts
- One quick action
- Reactivation
- Contextual guidance
- Feature promotion
- Usage-based triggers
Email: depth and persistence
Email is the channel for anything that needs explanation, or that the customer might want to come back to.
- Detailed guidance: step-by-step setup instructions, what to prepare before a task, how a feature works.
- Persistent reminders: an email stays in the inbox until it's dealt with, so it works well for things that don't need doing immediately.
- Rich educational content: tips, use cases, case studies and product updates, with space for images and layout.
- Proactive triggers: welcome sequences, onboarding series and lifecycle milestones.
Email reaches customers whether or not they have your app installed or open, which makes it the backbone of most programmes. It's slower, though: people often read email hours after it's sent.
Push notifications: urgency and action
Push is the channel for things that matter now.
- Timely prompts: "You're one step away from finishing your setup".
- Driving immediate action: short, specific messages with a single tap to the right screen.
- Urgent next steps: an expiring trial, an incomplete verification, an action someone else is waiting on.
- Reactivation: bringing lapsed users back at the moment they're most likely to respond.
Push is powerful but easy to overuse. Every notification spends some of the customer's goodwill, and people who feel spammed turn notifications off, often permanently. Keep push for messages that are genuinely timely and useful, and cap how many you send.
In-app messages: context
In-app messages reach customers while they're actually using the product, which makes them the best channel for contextual help.
- Contextual guidance: tooltips and walkthroughs at the moment a customer reaches a feature.
- Feature promotion: highlighting a relevant feature based on what the customer is doing.
- Supporting next steps: guiding customers from one completed task to the next.
- Usage-based triggers: messages that respond to behaviour in real time.
The limitation is obvious: in-app messages only reach people who are already in the product. They can't bring anyone back.
Choosing the right channel
| If the message… | Best channel |
|---|---|
| Needs explaining, or includes several steps | |
| Is time-sensitive and needs one quick action | Push |
| Relates to what the customer is doing right now | In-app |
| Needs to reach customers who haven't opened the app recently | Email or push |
| Is something the customer might want to refer back to | |
| Promotes a feature relevant to current usage | In-app |
Orchestrating channels together
The real gains come from combining channels into a single journey, rather than running separate email, push and in-app programmes. A typical sequence for a customer who has started but not finished setting up might be:
- Immediately: an in-app message confirming progress and showing what's left.
- A few hours later: a push notification reminding them they're nearly done, linking straight to the next step.
- The next day: an email with detailed guidance, what to have ready, and answers to common questions.
- If they complete the step: all reminders stop, and the next stage of the journey begins.
That last point matters. Every message should be triggered by behaviour and suppressed as soon as the customer has done what you asked. Nothing damages trust faster than a reminder to do something you did yesterday. Building this well depends on a solid set of behavioural events. See Behavioural triggers for how to design one.
Grow your reachable audience
A channel only works if you can use it, so treat reachability as a metric in its own right:
- Push opt-in rate: ask for permission at a moment when the benefit is obvious, and explain it. Asking during onboarding, with a clear reason, usually works far better than a generic prompt on first launch.
- Email engagement: track engaged versus inactive subscribers, and re-engage or suppress inactive ones to protect deliverability.
- App activity: in-app reach depends on how many customers use the app, so it rises as activation and retention improve.
Segmenting customers by the channels they can be reached on lets journeys adapt automatically: if push isn't enabled, the email carries more of the load.
Measure channels as part of the journey
It's tempting to compare channels on their own engagement rates, but push will usually win on speed and email on clicks to rich content. The better question is which combination moves customers through the lifecycle fastest. Measure journeys on their primary goal, such as activation rate, time to first value or upgrade rate, and test channel mixes against each other with a holdout group, as described in Proving lifecycle marketing works.
Want help designing multi-channel lifecycle journeys? Book a free consultation.