Journey 7, recoverWorking draft

The win-back journey

Win-back: relevance or silence, never a blast. After day 60 of silence nobody owns the dormant customer and almost nothing reaches them; this journey builds the missing win-back: entry by hand-off at day 60, the churn band setting who and how hard, every message anchored to a trip the customer actually takes, two touches then a genuine end, and a launch gate that has shrunk from a whole model to one sync payload extension.

2,046,603The reactivation pool, all three tiers
351,976reachable by push and email
730,447reachable by push only
273,351reachable by email only
690,829on no marketing channel

Watch the customer experience

The film of this journey as the customer receives it

Every segment, outcome and channel state, with the change and the evidence at each moment.

Open the film ↗

What changes

4 changes; each one today beside what is proposed on the CRM brief
The momentWhat the customer gets insteadWho builds it
The two-touch episodeAfter day 60 of silence nobody owns the dormant customer and almost nothing reaches them. The first knock is banded, route-anchored and deep-linked: their usual route, a real from-price this week, only pay if you win. Recognition for power users (what they have saved), the mechanic re-explained for one-time customers.Analytics ships the band into the sync and sizes the waves; Design writes the registers; the Braze developer builds the canvas.
The welcome-back landingA returner stops landing on the same generic cold start as everyone else: the card recognises the absence, restates the account is as they left it, and lands them on their route at a real price. The failing magic-link door is flagged as a product fix beside it.Sheran rules the owner; the Braze developer ships the card; Product fixes the expiring magic-link door.
The long tail: a real end, one annual beatOne last try that says so: the best welcome-back deal, one time only, and after this we stop asking. Then the end is real: hard suppression, and the anniversary as the one remaining beat.Sheran and Finance rule the offer; Analytics sizes per band; the Braze developer wires the end-state suppression.
The live incentive card's dispositionThe card’s job (an incentive at re-entry) overlaps the welcome-back landing and the final attempt; the record needs one owner and one offer story before the new build ships beside it.Sheran rules; the Braze developer executes in the go-live change.

Your brief

one page per team, the asks linked to the board

What ships when

6 of 6 treatments ship in Phase 1 with no engineering; 0 wait for it

Phase 1 · ships on Braze and Analytics

  • The route-anchored win-back
  • The comparison anchor
  • The welcome-back landing
  • The final attempt, then a genuine end
  • The anniversary message
  • The live incentive card

Phase 2 · waits for engineering

  • Nothing waits.

Launch gates, Phase 1

  • No launch gates recorded.

Phase is derived from each row, never authored: engineering work that is a new event, feed or surface is Phase 2; new wording, a deletion, an Analytics trait or Braze wiring is Phase 1. The deck walks Phase 1 in situ.

What needs deciding

DecisionOwnerWhere it stands
The tier pools the 2 Sep Analytics pull sizes sit on a different definition to the held figuresSheran, with IviOpen
How the journey is measured: the holdout, the baseline and the readMichael, with CACIOn the Test and Learn record
Working detail
Leave feedbackThis pack is a proposal. The banded episode shape and the recognition-first door are the recorded position; the surface owner, the card disposition and the offer are open rulings. Say what is wrong with the journey, or what it is missing.
Pack version: 3 Sep 2026, 14:19 (London)