Free resource · use it on this page
Automation Blueprint: Reusable Journey Templates
Four proven lifecycle flows — welcome, abandonment, win-back, and renewal — mapped step by step so you launch from a working plan instead of a blank canvas.
How to use this blueprint
Each journey below is a complete flow: every step has a trigger, a timing, a message focus, and a rule for when the person leaves the journey. Copy the table into your automation tool, then adjust only the timings — the structure and exit logic are the part most teams get wrong, so keep those intact. The delays shown are common starting points, not laws: scale them to your purchase cycle. A coffee shop's win-back threshold might be three weeks; a tire shop's might be three years.
Three rules apply to every journey here. One entry trigger per journey — if you need two triggers, you need two journeys. Every journey needs an exit condition checked before every step, so a customer who converts at step 2 never receives step 3. And journey sends must count against your global frequency cap, or your most engaged customers will get buried the moment two journeys overlap.
The blueprints are channel-agnostic: they work for email, SMS, app push, or wallet passes. Channel economics change how aggressive a cadence you can afford — SMS bills per message, while wallet pass updates (through a platform like PushNotice) carry no per-message cost — but the triggers and exits stay the same. Pick the channel per step, not per journey.
Journey 1: Welcome (first 30 days)
Entry trigger: signup, opt-in, or first pass install. Exit at any step: unsubscribe, or completion of step 6. The single goal is one activation action — define yours (first purchase, first visit, first redemption) before you build anything.
| Step | Send when | Message focus | Skip or exit rule |
|---|---|---|---|
| 1. Confirm | Immediately on join | Confirm what they joined, restate the core benefit in one line, and set expectations: what you will send and how often | Always sends |
| 2. First-value nudge | Day 2-3 | One clear action — the activation action — with the single easiest way to take it; no feature tour | Skip if they already activated |
| 3. Educate | Day 7 | One benefit they have not used yet, shown with a concrete example rather than a feature list | Skip if that benefit was already used |
| 4. Show best use | Day 14 | How your best customers use the program: one real pattern, not a testimonial wall | Skip if fully active |
| 5. Check in | Day 21 | One question: is this useful so far? Route replies to a human, not a form | Skip if they replied to any earlier step |
| 6. Graduate | Day 30, or on activation, whichever comes first | Move them to your regular calendar; tag as activated or not-activated for later segmentation | Journey ends |
Journey 2: Cart and booking abandonment
Entry trigger: cart or booking started, contact reachable, no completion within your grace window (30-60 minutes is a common start). Exit at every step: purchase or booking completed, unsubscribe, or item out of stock.
| Step | Send when | Message focus | Guardrail |
|---|---|---|---|
| 1. Neutral reminder | 30-60 minutes after abandonment | The exact items or booking still held, with a one-tap way back in — no discount yet | Leading with a discount trains repeat abandoners to wait for one |
| 2. Objection handler | 24 hours | Answer the likely blocker: shipping cost, returns policy, availability, or payment options | Pick the objection your support tickets actually show |
| 3. Honest urgency | 48 hours | Real scarcity only: actual stock level or a booking slot that genuinely expires | Never fabricate urgency; fake countdowns destroy trust permanently |
| 4. Incentive (optional) | 72 hours | A small incentive if margin allows, reserved for higher-value carts | Gate by cart value and by how often this person has already received one |
| 5. Close out | Day 5-7 | One final note, then stop; return them to regular marketing | A journey that never ends is a spam list |
Journey 3: Win-back (lapsed customers)
Entry trigger: no purchase, visit, or redemption for your lapse threshold. Set the threshold from your own repurchase interval — a common rule is two to three times the typical gap between purchases, not a fixed 90 days. Exit at every step: any purchase, visit, or redemption returns them to the active lifecycle.
| Step | Send when | Message focus | Why this order |
|---|---|---|---|
| 1. Low-pressure check-in | At lapse threshold | Lead with what is new since they left; no guilt, no we-miss-you clichés | Curiosity outperforms pressure on a first touch |
| 2. What they would lose | 1 week later | Their own account: points balance, tier status, saved preferences, a favorite item back in stock | Loss of something already owned is a stronger motivator than a generic pitch |
| 3. Strongest offer | 2 weeks later | The best offer in the journey; win-back is the place a discount earns its cost | You are competing against inertia, not another purchase |
| 4. Honest last call | 3 weeks later | Say plainly this is the last of these messages | Stated finality is honest, and it gives a genuinely undecided customer a clear reason to act now |
| 5. Sunset | 4 weeks later, no response | No message — suppress them from regular sends or drop to your lowest frequency | Continuing to send to the unresponsive hurts deliverability for everyone else |
Journey 4: Renewal and expiry
Works for subscriptions, memberships, loyalty tier expiry, and pass or card expiry. Entry trigger: expiry date minus 30 days. Exit at every step: renewal completed. Compress the schedule proportionally for shorter terms — for a monthly plan, think days, not weeks.
| Step | Send when | Message focus | Rule |
|---|---|---|---|
| 1. Early notice | 30 days before expiry | Plain statement of what expires, the date, and the renewal path in one tap | No selling yet; this send is a service, and it is the one customers thank you for |
| 2. Usage recap | 14 days before | What they got this period: visits, savings, rewards earned, features used | Their own usage is the strongest renewal argument you have — use real numbers from their account |
| 3. Direct ask | 7 days before | Ask for the renewal with the exact price and terms stated up front | A surprise at checkout costs more renewals than the reminder ever wins |
| 4. Expiry day | Day 0 | Final reminder plus exactly what happens to their points, tier, or data if they lapse | State consequences factually; this is information, not a threat |
| 5. Grace recovery | 3-7 days after expiry | A reinstatement path if your terms allow one; otherwise hand them to the win-back journey | Journeys should chain — a renewal miss is a win-back entry, not a dead end |
Journey spec worksheet — fill one per journey before you build
Print this or copy it into a doc. If you cannot fill every field, the journey is not ready to build. The kill criteria field matters most: decide the failure condition before launch, when you are still objective.
Journey name
Audience plus goal in one line, e.g. Lapsed regulars to second visit
Entry trigger
The one exact event and condition that enrolls someone; two triggers means two journeys
Entry exclusions
Who never enters: recent purchasers, staff and test accounts, anyone currently in a conflicting journey
Exit conditions
Every event that removes someone mid-journey: conversion, unsubscribe, opened support ticket
Steps and timing
Each step with its delay, plus the total journey length end to end
Channel per step
Which channel carries each step and why it fits that specific message
Frequency cap behavior
How these sends count against your global cap, and which other sends this journey suppresses or yields to
Success metric
One number, measured against people who entered the journey — not against your whole list
Kill criteria
The result that pauses this journey, written down before launch
Owner and review date
The person who checks performance, and the calendar date they will do it
Pre-launch checklist — run once per journey, with a real test profile
Work through every item with a test contact enrolled in the actual journey, not in a preview screen. Each item below targets a failure mode that is easy to miss in a preview and expensive to discover in production.
Entry trigger fires exactly once
Re-trigger the entry event on the same test profile and confirm it does not double-enroll
Exit works at every step
Convert mid-journey with the test profile and confirm all remaining steps cancel
Journey collisions resolved
Decide priority when one person qualifies for two journeys the same week; one must yield
Frequency cap honored
Confirm journey sends count against your global cap rather than bypassing it
Quiet hours and time zones respected
Delays measured in hours can land at 3 a.m. in another time zone; check the send window setting
Personalization fallbacks set
Send every step to a profile with empty fields and read what actually renders
Links tested on both platforms
Every link and deep link, on iOS and Android, landing on a page that matches the message
Offers are real and redeemable
Codes work today, expiry dates match the copy, and terms match what the message claims
Opt-out stops the journey instantly
Unsubscribe mid-journey with the test profile and confirm no further steps send
Suppression lists applied
Staff, test accounts, and recent complainers are excluded at entry
Measurement live before the first send
The conversion event is tracked and you have a baseline or holdout to compare against
Rollout starts small
Limit the first cohort, read the results, then open to full volume
Kill switch identified
Know the exact button that pauses the journey and who is authorized to press it
From the guide: Best Push Notification Tools (2026)
This resource accompanies the full article — worth reading before you commit to a tool.