Free account

Save your progress

Keep lessons, quiz scores and your certificate in sync across devices. Lessons you already finished in this browser are added automatically.

At least 8 characters.

By continuing you agree to our terms and privacy policy. We store your name, email and course progress. No spam.

Track 4 · Retention, CRM & Lifecycle · Lesson 3 of 4

Lifecycle Orchestration Across Email, Push, SMS and WhatsApp

Design trigger-wait-split journeys that pick the right channel per user, respect consent, frequency caps and quiet hours, and follow India's WhatsApp and TRAI rules.

TL;DR

Advanced 18 min
  • Every journey is the same skeleton: a behavioural trigger, a wait, a split on what the user did, and an exit the moment the goal is reached.
  • Orchestration means one decision layer chooses the channel per user and per moment, using consent, reachability, cost and urgency. It is not four teams each blasting their own channel.
  • Global frequency caps, quiet hours and exit conditions protect the asset that matters most: the user's permission to message you at all.
  • In India, WhatsApp is often the highest-response channel and also the most regulated and costly per message. Use it for high-intent moments, with explicit opt-in, and measure against a holdout.
KPIs it moves
  • Incremental conversion vs holdout
  • Revenue per recipient
  • Opt-out and block rate
  • Messages per user per week
  • WhatsApp quality rating
  • Cost per incremental conversion
Best for
  • E-commerce / D2C
  • B2B SaaS

Why this matters

Most retention programmes grow by accretion. Someone builds a welcome email. Someone else adds push. A third team buys a WhatsApp vendor for sale announcements. Each channel looks good on its own dashboard, and the customer gets six messages on a Friday night.

The cost shows up in three places. Users opt out or block, which shrinks the reachable base permanently. Channel costs rise, because WhatsApp and SMS are paid per message. And attribution double counts the same purchase in every channel, so nobody can tell what actually worked.

Orchestration is the fix. It treats all channels as one system with one set of rules: who is eligible, which channel goes first, how many messages a person can get, when to stay silent and when to stop.

The framework

The journey skeleton

Every lifecycle flow, from abandoned cart to trial onboarding, has the same four parts.

PartQuestion it answersExample
TriggerWhat behaviour starts the journey?Cart created and no checkout within 30 minutes
WaitHow long until the next decision?1 hour, or until 10 am local time
SplitWhat did the user do, and what do we know about them?Purchased? Opened? Opted in to WhatsApp? High cart value?
ExitWhen must the journey stop?Purchase, unsubscribe, support ticket, cap reached

Design the exits first. A journey that keeps sending after the goal is met is worse than no journey.

The channel decision

For every message slot, the orchestration layer picks a channel using four filters in order:

  1. Consent. Does the user allow this channel for this message type (transactional vs marketing)?
  2. Reachability. Is there a valid email, an app install with push enabled, a WhatsApp-registered number?
  3. Urgency and richness. Time-critical and high-intent moments justify interruptive channels (push, WhatsApp). Long content suits email.
  4. Cost. Email and push are close to free per send. SMS and WhatsApp marketing templates are paid per message, so they must earn their place.
ChannelBest forCost per sendIntrusivenessMain risk
EmailRich content, nurture, receiptsVery lowLowDeliverability, ignored
PushTime-sensitive nudges in appVery lowMediumOpt-out, app uninstall
In-appUsers already in sessionFreeLowOnly reaches active users
SMSOTPs, critical alertsPaidHighLittle content, strict sending rules
WhatsAppHigh-intent, conversational, India and other WhatsApp-first marketsPaid per templateHighBlocks lower quality rating and limits reach

Guardrails that apply across every journey

  • Global frequency cap. A starting point many teams use is one marketing message a day and four to six a week per user across all channels. Transactional messages (OTP, order updates) sit outside the cap.
  • Channel priority. If a user is reachable on several channels, send on the cheapest one likely to work, and escalate only if there is no response.
  • Quiet hours. No promotional pushes, SMS or WhatsApp at night in the user’s local time. A common rule is no marketing between 9 pm and 9 am.
  • Journey priority. When two journeys want the same user, a fixed hierarchy decides (for example, transactional, then cart recovery, then onboarding, then newsletters).
  • Holdout. Every journey keeps a random 5 to 10% of eligible users unmessaged so you can measure incremental impact.

India: WhatsApp and TRAI specifics

WhatsApp is the default messaging app for most Indian consumers, which is why it so often outperforms email there. It also comes with rules you must design around. Check current documentation before you launch, since details change.

  • Opt-in. Meta requires that the user clearly agreed to receive messages from your named business. The opt-in can be collected on your site, at checkout, by SMS or on a paper form, and you must honour opt-outs.
  • Template categories. Business-initiated messages use approved templates in one of three categories: marketing, utility or authentication. Mixing an offer into an order update makes it marketing.
  • Per-message pricing. Since 1 July 2025 Meta charges per delivered template message, with rates by category and country. Utility templates sent inside an open 24-hour customer service window are free, and free-form replies inside that window cost nothing.
  • Free entry point. When a user messages you from a Click to WhatsApp ad and you reply within 24 hours, a 72-hour window opens in which all messages are free. That makes ad-led conversations cheaper to follow up.
  • Per-user marketing limits. Meta caps how many marketing templates a given user can receive from all businesses combined, and does not publish a fixed number. Some sends will simply fail for heavily messaged users, so never rely on WhatsApp as the only touch.
  • Quality rating. Blocks and reports lower your number’s quality rating, and sustained low quality can get your sending rate limited.
  • SMS under TRAI. Commercial SMS in India runs through the DLT system under TRAI’s TCCCPR 2018, with registered headers and templates. Operators restrict promotional messages to daytime hours (widely implemented as 9 am to 9 pm). TRAI’s February 2025 amendment tightened definitions, for example treating messages that mix promotional and service content as promotional.
  • Data protection. India’s Digital Personal Data Protection Act, 2023 adds a general expectation that consent is specific and can be withdrawn. Keep a consent ledger per channel and purpose.

Step-by-step playbook

  1. Inventory every automated message. List all journeys, channels, triggers and owners in one sheet. You will usually find overlaps and orphan flows nobody owns.
  2. Build the consent and reachability profile. Per user: email status, push token, WhatsApp opt-in with timestamp and source, SMS DND status, preferred language and time zone.
  3. Set global rules before journeys. Frequency cap, quiet hours, journey priority, holdout share. Put them in the orchestration tool, not in each campaign.
  4. Design each journey on paper. Write the trigger, the exits, then the waits and splits. Every split must answer a question that changes what you do next.
  5. Assign channels by step, not by journey. Start with the cheapest channel. Escalate to push, then WhatsApp, only for users who have not converted and still show intent (cart value above a threshold, product viewed again).
  6. Write content per channel. Email gets detail. Push gets one line and a deep link. WhatsApp gets a short, personal message, product image and one button. Tag every link with UTMs so you can see channel contribution.
  7. Launch with a holdout and a guardrail dashboard. Track incremental conversions, unsubscribes, push opt-outs, WhatsApp blocks and quality rating weekly.
  8. Prune quarterly. Kill steps that show no incremental lift. Fewer, better messages usually beat more messages.

Worked example

D2C abandoned cart across four channels

Abandoned cart: email first, escalate on intent

  1. TriggerCart created, no checkout in 30 minutes
  2. WaitWait 30 minutes (respect quiet hours)
  3. Send · EmailReminder with cart contents
  4. WaitWait 4 hours
  5. SplitPurchased or still has intent?

    Purchased

    1. ExitExit, move to post-purchase journey

    No purchase, cart over ₹1,500, WhatsApp opt-in

    1. Send · WhatsAppCart reminder with product image and checkout button
    2. WaitWait 24 hours
    3. Send · PushLow-stock or social proof nudge (no discount)
    4. ExitExit after 72 hours or on purchase

    No purchase, other users

    1. Send · PushNudge with deep link to cart
    2. WaitWait 24 hours
    3. Send · EmailBestseller reviews for cart items
    4. ExitExit after 72 hours or on purchase
WhatsApp is reserved for opted-in, high-value carts. Every step re-checks purchase before sending.

Say a D2C brand gets 10,000 abandoned carts a month with an average cart of ₹1,800 and a 40% gross margin. 30% of these shoppers (3,000) have opted in to WhatsApp and have carts over ₹1,500.

  • Holdout result. A 10% holdout shows 4.0% of abandoners buy within 72 hours with no messages.
  • Email and push only (treated group). 6.5% buy. Incremental rate = 6.5% - 4.0% = 2.5 points. On 9,000 treated carts, that is 225 incremental orders.
  • Adding WhatsApp for the eligible 3,000. Say the eligible group converts at 9.0% with WhatsApp versus 6.5% without (measured with a split inside the eligible group). That is 2.5 more points on about 2,700 treated eligible carts: about 68 extra orders.
  • Is WhatsApp worth it? Assume ₹0.90 per delivered marketing template for this arithmetic (check Meta’s current India rate card). Cost = 2,700 x ₹0.90 = ₹2,430. Margin from 68 orders = 68 x ₹1,800 x 40% = ₹48,960. The channel pays back roughly 20 times. Now repeat the sum for carts below ₹1,500 and for users who already got push. That is where paid channels often stop paying back.

B2B SaaS trial onboarding

14-day trial: activate first, sell second

  1. TriggerTrial started
  2. Send · EmailWelcome with one setup task
  3. WaitWait 2 days
  4. SplitCompleted key setup action?

    Yes, activated

    1. Send · In-appInvite teammates checklist
    2. WaitWait until day 10
    3. Send · EmailPlan recommendation based on usage
    4. ExitExit on upgrade

    No, not activated

    1. Send · EmailSample data and 3-minute walkthrough
    2. WaitWait 2 days
    3. Send · EmailOffer a 15-minute setup call (sales-assist if company size over 50)
    4. ExitExit on activation, move to activated branch
In B2B, email and in-app carry most of the load. WhatsApp and SMS are used for meeting reminders where the user has opted in.

B2B SaaS vs D2C: what changes

TopicB2B SaaSD2C
Primary channelsEmail, in-app, sales and CS tasksEmail, push, WhatsApp, SMS
Trigger sourceProduct events (setup, invites, usage drops)Commerce events (browse, cart, order, delivery)
RecipientSeveral users per account, different rolesOne person
SplitsActivation state, role, account sizePurchase, cart value, consent, category
Human stepHand-off to sales or CS is a channelRare, mostly support
WhatsApp in IndiaMeeting reminders, renewals, supportCart, delivery, COD confirmation, reorders

In B2B, orchestrate at account level too. If an admin is already in a renewal conversation with a CSM, suppress automated upsell emails to everyone in that account.

How to measure it

MetricDefinitionNotes
Incremental conversionTreatment conversion rate minus holdout conversion rateSame window, randomised assignment
Revenue per recipientRevenue from treated users / users enteredCompare to holdout revenue per user
Cost per incremental conversionPaid channel cost / incremental conversionsDo this per channel and per branch
Messages per user per weekMarketing sends / active reachable usersWatch the 95th percentile, not just the average
Opt-out and block rateUnsubscribes, push opt-outs, WhatsApp blocks / sendsPer channel, per journey
WhatsApp quality ratingMeta’s rating for your numberCheck weekly, pause journeys that drive blocks

Use your A/B test calculator to size holdouts. A journey with a 4% baseline and an expected 1 point lift needs several thousand users per group to read with confidence, so small journeys may need a longer test window or a pooled holdout across journeys.

Case study · Tata CLiQ

Case study: Adding WhatsApp to the lifecycle mix for opted-in shoppers (Meta-published)

  • 10x ROI vs email, push and SMS
  • 57% WhatsApp clickthrough rate
  • $500K Sales attributed in one month
  • 1.7x Purchase likelihood from WhatsApp visits

Tata CLiQ, the Tata Group's e-commerce marketplace, worked with Gupshup to add the WhatsApp Business Platform to its retention channels. According to Meta's success story, email was reaching a 10% open rate and SMS could not carry rich personalised content. The team rolled out in stages. First came transactional messages such as shipping updates. Then, for the high-volume Diwali and Black Friday periods, it sent targeted messages only to customers who had opted in, using data science to choose who received what: recommendations based on a month of browsing history, abandoned cart reminders, price-drop alerts on wishlisted items, and welcome coupons for new users. Across two one-month campaigns in October 2021, Tata CLiQ reports 10x ROI compared with email, in-app push and SMS, a 57% clickthrough rate, $500,000 in sales attributed to WhatsApp in one month, and that customers who arrived from a WhatsApp notification were 1.7x more likely to purchase. These are business-reported results on Meta's own site and the attribution method is not described, so treat the ROI as directional. The design lesson holds regardless: transactional first to build trust, then opt-in, behaviour-triggered marketing on the channel customers prefer.

Sources: Meta for Developers: Tata CLiQ success story (WhatsApp Business Platform)

Pitfalls vs pro moves

What amateurs do What top 1% growth teams do
Each channel team runs its own calendar, so one user gets an email, a push, an SMS and a WhatsApp about the same sale on the same evening. One orchestration layer owns a global per-user cap (for example 1 marketing touch a day and 5 a week across all channels) and a channel priority order.
Send the abandoned cart sequence on a fixed timer even after the customer has bought. Re-check the goal before every step and exit immediately on purchase, unsubscribe, a support ticket or a refund.
Put every user on WhatsApp because it gets the best open rates. Reserve WhatsApp for opted-in users at high-intent moments, track block rate and quality rating weekly, and prove incrementality against a holdout before scaling.
Mix a promotional offer into an order update to get it through as a transactional message. Keep utility and marketing templates separate. Mixed content is classed as marketing under both WhatsApp template rules and TRAI's commercial communication rules.
Judge journeys on opens and clicks. Judge them on incremental conversions and revenue per recipient against a randomised holdout, net of channel cost.
Send at 11 pm because the scheduler defaulted to the server time zone. Send in the user's local time, inside quiet hours rules, and learn per-user best send time from past engagement.

Knowledge check

Knowledge check

3 questions · pick an answer to see the reasoning

  1. Q1. A shopper abandons a ₹3,200 cart at 10:40 pm IST. She has opted in to WhatsApp marketing, has the app installed with push enabled, and has an email on file. What is the best first touch?

  2. Q2. Your B2B trial onboarding journey shows a 38% conversion rate for users who received it. Last quarter's overall trial conversion was 30%. Can you claim an 8 point lift?

  3. Q3. You want to send a WhatsApp order-shipped update and, in the same message, a 10% off code for the next order. What happens?

Sources

  1. Meta for Developers: Tata CLiQ success story
  2. Meta for Developers: WhatsApp Business Platform pricing
  3. Meta for Developers: Getting opt-in for WhatsApp
  4. Meta for Developers: WhatsApp template fundamentals
  5. Exotel: TCCCPR 2018 FAQ (TRAI commercial communication rules)
  6. Khaitan & Co: TRAI Second Amendment to the TCCCPR 2018

Updated