Journey 2 · Before the trip: Review Pack
← Journey 2 front pageThe working record behind it: the matrix, the maps, the campaign brief in full and the reference.
Journey 2 · Before the trip: the won trip protected · Review packPack version: 3 Sep 2026, 23:20 (London) · source of truth: J2/content.json

Before the trip: reassure, wayfind, bank the value

The strategy this pack executes: Strategy on a page ↗

📮 Leave feedback
This pack is at Gate 1: the strategy review. The timing-test decision, the post-win slot ratification, the deleted recovery send and the catering call are the open decisions. Say what is wrong with the strategy, or what it is missing.
How we work with agents ↗
Journey 2 · Protect
The pre-travel journey

The customer's four questions (did it work, which platform, which coach, was it worth it) go unanswered on every channel while the window sells taxis and swaps over them. One arc per trip answers all four in order and demotes every sell below the reassurance, with disruption yielding everything to the service layer. The stake is won-trip lifetime value: £115.62 against £22.92 when the trip goes wrong.

The CRM brief: every comms change, today beside proposed
▶ Watch the customer experienceOpen full screen

The film of this journey as the customer receives it: every segment, trip path and channel, with the change and the evidence at each moment. The static walkthrough below carries every change in full beside its evidence.

The static walkthrough

The same journey with every moment on screen at once: each change, its evidence and its full logic, moment by moment below.

Two live defects sit under this journey: the legacy swap push firing with no known caller, and the swap-eligibility defect. The detail, with the fixes: the Engineering brief.

ValidatedAnalytics validation requiredData / build outstanding

Choose the viewEvery change redraws the walkthrough below: one traveller, one channel state, one ending, one phase.

The D pins: the data the changes need

The pins on the walkthrough above mark the data each change needs, coloured by the sort of ask: COMPUTED TRAIT · ANALYTICS APP AND JOURNEY OWNED NEW EVENT · ENGINEERING BUILDS EXISTS · PIPE TO BRAZE READY · NOTHING TO BRIEF. Tap any pin, anywhere in the pack, for what it is. The full contracts live on the Engineering brief, the computed traits on the Analytics brief.

PinWhat it isThe askWhere it stands
D1EXISTS · PIPE TO BRAZEExists, no route to braze
D2NEW EVENT · ENGINEERING BUILDSDoes not exist yet
D3COMPUTED TRAIT · ANALYTICSExists, not synced to braze
D4NEW EVENT · ENGINEERING BUILDSDoes not exist yet
D5APP AND JOURNEY OWNEDApp and journey owned
D6EXISTS · PIPE TO BRAZEExists, pipeline stale
D7COMPUTED TRAIT · ANALYTICSDoes not exist yet
D8EXISTS · PIPE TO BRAZEExists, no route to braze

Who walks through this journey

The volumes behind the walk: how many customers take it, split by who they are and what we can reach them on. These numbers prioritise what gets built first.

WhoPush and emailPush onlyEmail onlyNo marketing channelAll channels
Upgrade purchasers entering the pre-travel window, each month11,44918,2963,35610,92344,024 a month
Upgrades bought within 24 hours of departureTBCTBCTBCTBC85%
The proven email family's eligibilityTBCTBCTBCTBCFirst Class upgraders, no past ticket, email opted in: the narrow slice
Six-month average, counted at purchase as distinct purchasers. A quarter hold no marketing channel, which is the reach ceiling on the day-before email. Source: Analytics (Ivi), 2 Sep 2026.
Working detail
Leave feedbackThis pack is at Gate 1: the strategy review. The timing-test decision, the post-win slot ratification, the deleted recovery send and the catering call are the open decisions. Say what is wrong with the strategy, or what it is missing.
Pack version: 3 Sep 2026, 23:20 (London)