← StrategyJourney 3 campaign brief
Journey 3, CRM brief (the comms changes)Pack version: 14 Oct 2026, 09:01 (London)
Leave feedback
The CRM brief

The journey by phase, and the Phase 1 Braze build

This journey’s strategy. Customers who stall at the bid are not short of interest, they are short of confidence. Build it at the moment of doubt: the screen answers first, one message answers the rest. The full statement and the case: the campaign brief tab.

For the CRM team and the Braze developer. The journey as it runs today and as it should run by phase, then the Phase 1 build: one row per send Braze builds, with what starts it, what stops it and what it needs. The words per version are on the Design brief; the full logic per row, and the copy of record, sit on the Decisioning matrix.

Work from this brief in FigJam: the send changes as cards, today beside proposed↗▶Watch the customer experience: this journey as the customer receives it↗

The journey maps

today's journey, and the proposed journey by phase: what the canvases must become
searches, sees resultson an Avanti routestill unsure on pricetaps through to bidreaches confirmno auction to showthe one thing offeredopts in🕐 while in the leadno branch to takethe auction plays out🕐 minutes later🕐 Avanti, laterthe net effect🕐 then nothing🕐 next morningthe same opening,answered twice⚡A funnel session, todayno journey owns itcomms fire per screen,nothing reads the stepiamIN-APPRisk-free bannersearch results, always-onprior evidence exists,the team believes it fires too earlyKEPT · TEST PLACEMENTiamIN-APPThe cabin coachmarkAvanti results, no pricenames the cabin choice,never resolves it: no priceREWORDED IN THE TO-BEGAP: price-view exitnothing fires; "not actuallycheaper" walks out unansweredGAP: bid-add dwellthe biggest controllable leak,and nothing is on itGAP: confirm-abandonthe last step before a bid,no answer at all⚡A dead-end search, todayroute not covered,or the window is not openiamIN-APPThe dead-end results screenno reason, no redirectno reason given,no redirect offeredREWORDED IN THE TO-BEiamIN-APPThe alert capture cardplus Route Watch (April)“Get upgrade alerts”the best dead-end converter today,and the opt-in rate is unmeasuredKEPT · EXTENDED✅Exit: an alert is set;it fires the NEXT MORNINGA 9:00am day-1 batch: 9 to 33 hoursafter the match, no won, bought orclosed suppressions, doubled forpush-and-email watchers.⚡A bid is placed, todaythe auction runs from hereiamIN-APPThe in-lead slide-upone generic messageno permission branch,no outcome branchSIGNED REWORKGAP: consent and lead state⛔ 2 LAUNCH BLOCKERSpush consent is not queryable,and lead state is not carried🚪Exit: the live auction,which Journey 4 ownsnothing here reads the outcome⚡Mid-auction drop-offthe only chase that existsa timer, blind to the steppushPUSHAbandoned-auction push5, 10 and 15-minute variants“come back to your auction”blanket: no step, no owner,no consent readDECIDE FIRST · AT BOUNDARYpushPUSHThe Avanti cross-sell push1 to 2 hours after the addsame job, Avanti cohort onlyDECIDE FIRST · AT BOUNDARYSTACKS: no cap, no ownerlands alongside close-moment sends,and the entry criteria are unaudited🚪Exit: silenceno second designed touchand no incrementality read, everpushPUSHemailEMAILThe matched-alert campaignpush and email, day-late batchKEPT · RE-TIMED IN THE TO-BEpushPUSHBidding-has-started pushnative, real time, watchersKEPT

Phase 1 ships on Braze and Analytics with no app release; Phase 2 is anything that needs engineering.

For the Braze developer

the Phase 1 build, one row per send Braze builds: what it fires on, its caps and what stops it, what it needs, and the questions still open on it
The buildFires onCaps, and what stops itWhat it needs, and what is open
The watched route opens
Braze Push, Email: push where held, else email, one alert per opening
Phase 1
The route’s auction window opens or coverage goes live: a supply event, not a clock. Today’s send runs as a day-1 batch at 9:00am on the matched alert, live since 13 Apr 2026, with no exception events, no property filters and no quiet hours (console-confirmed 14 Aug 2026).One alert per opening per customer. The episode is already closed: setting the watch closed it.
Stops: Won, bought and closed suppressions added; never sends beside the bidding-has-started push for the same opening.

The existing matched-alert event (window-open fix, Braze only); a new coverage-live supply event for the coverage half (phase 2). Alert requests reach Braze daily, but nothing records a watch removed and their warehouse copy is unconfirmed, so a has-an-active-alert segment cannot be built yet: on the engineering record.
  • Measure the alert capture card’s opt-in rate, and the alert’s own conversion. Analytics: Ivi and Ben
The abandoned search
Braze Push, Email: push where held, else email
Phase 1
Search-episode read: the last search of the episode with no auction opened, no bid, no purchase and no new session since. Arm A next day (batch); arms B and C 30 minutes and two hours after the last search (real time). A later search in the episode resets the clock and replaces the earlier one.One send per search episode; the episode's two-touch cap is shared with the recovery spine (rows 8 and 9); never more than one abandoned-search send per customer in seven days.
Stops: Any bid, purchase, auction opened or new session since; the searched date passed with no alternative on the route (silence); a dead-end result (row 6 owns it); live disruption on the route; power users; an open support contact; any owned Journey 4 or 5 episode; quiet hours. The instant option never renders where the train carries no Buy Upgrade Now or the whole party cannot be seated: the bid-only copy sends. Every auction on the searched date has closed by send time while the train has not yet left: no send. Once the date has passed, the date-passed copy sends instead (Your {route} trip has been and gone). The walk-up line renders only where the walk-up is above the floor; otherwise the push and email carry the floor alone (bid from {floor}).
search event payload, episode stamp, buy upgrade now flag
The search event with origin, destination, travel date, party size, results count, lowest opening bid, walk-up fare, session id and timestamp, into the warehouse (arm A) and Braze in real time (arms B, C); the search-episode stamp; the results deep link with the search restored; Analytics: the unaided-return curve, the holdout and minimum detectable effect, the depth and frequency traits for the later arm; the Buy Upgrade Now availability flag and the whole-party availability check (Journey 4’s engineering rows, consumed here) for the instant option.
  • Measure the unaided-return curve for search-only abandoners (share who open an auction or bid within 30 minutes, two hours and 24 hours of their last search, from existing search events), then size the three timing arms and the holdout. Analytics: Ivi and Ben
  • Define the depth and frequency traits that rank which search to chase when several were made, and say whether a model is warranted after the rules have run for a cycle. Analytics: Ivi and Ben
The recovery message
Braze Push, Email: push where held, else email
Phase 1
Still unfinished at the next-day batch read: no bid, no purchase, no new funnel session since the abandon. The deepest step reached stamps the episode (search-only is the shallowest and is owned by row 7b); a deeper abandon upgrades it in place, never opens a second episode.Two touches per episode, then silence. Day 7 closes every episode and hands back to Journey 5.
Stops: While the legacy abandoned-auction pushes still fire on this cohort, no recovery sends from this journey: replace, never stack. Power users suppressed from the whole spine. One owner per customer: a live bid means Journey 4 owns them. The auction has closed or the train has left by send time: no send (checked when each touch sends, from the episode’s auction close time). The recent-wins band renders only when its top is at or above the current opening bid; otherwise the no-band version (Sam Ayles, 13 Oct 2026).
episode stamp, legacy audit
The deepest-step episode stamp (warehouse batch, buildable today; the funnel mart lags about six days so the batch rides the raw streams); the legacy-pair reach audit; the journey-ownership flag, an open decision that gates launch; the Analytics-sized holdout; the auction id and its close time on the episode record, so a closed auction cancels the send. The saved-bid store (and the bid-amount event, paused with the confirm screen on 5 Oct 2026): Sheran’s answer to Dirk of 29 Sep 2026, no message mentions a saved amount until it is built.
  • Ratify the recovery owner: this journey authors and owns the shared funnel-abandon recovery spine, deepest step wins, two touches then silence, day-7 hand-back. Sheran, at Gate 1
  • Ratify day-one timing for the first recovery touch, superseding the earlier one-hour working assumption. Sheran, at Gate 1
  • The legacy pair’s entry criteria and actual reach: one console audit of who the abandoned-auction pushes chase today, then the bid-placed boundary ruling. Lisa, and the Braze developer
  • Size the recovery holdout and the headline test: baseline, minimum detectable effect, significance and runtime, stated up front. Analytics: Ivi and Ben
The second touch
Braze Push, Email: the other channel, or again on the one held
Phase 1
Touch 1 unseen at the +22 hour check, in-canvas.Two touches per episode, hard. Day 7 closes the episode and hands back to Journey 5.
Stops: Any bid, purchase or new funnel session exits instantly at any point. The auction has closed or the train has left by send time: no send. The recent-wins band renders only when its top is at or above the current opening bid; otherwise the no-band version (inherited from row 8).

Nothing beyond row 8’s spine.
  • Ratify the recovery owner: this journey authors and owns the shared funnel-abandon recovery spine, deepest step wins, two touches then silence, day-7 hand-back. Sheran, at Gate 1
Permission at peak intent
Braze In-App Message
Phase 1
Entering the lead, per the signed row.Owned by the signed row.
Stops: Owned by the signed row.

Nothing from this journey.

Build paused until written sign-off. Every build carries its exit, cap and suppression; a control group is verified real, never assumed; Liquid never renders raw; a dependency that does not exist yet is flagged, not faked.

Not in this build

Phase 2, and the app surfaces: do not build any part of these, because each waits on an engineering release, and half-building one splits a moment across two owners
The treatmentWho it reachesWhy it waits
The results banner
Tooltip Card At The Price, Braze In-App Message
Everyone who reaches the search results, by customer stateWaits on an app release.
The cabin coachmark, priced
Native Screen Or Modal
Customers on Avanti routes, the first time the Standard Premium and First Class toggle showsWaits on an app release.
The price comparison on the auction screen
Native Screen Or Modal
Customers dwelling or cancelling at an auction’s price viewWaits on an app release.
The enter-amount stall
Native Card, Braze Copy
Everyone who opens the bid flow; the card forks by bid history: never bid, bid before, power userAn app surface (native card, braze copy), so an app build, not a Braze one.
The last-step check · native screen or modal
Native Screen Or Modal
Everyone who reaches the confirm screenPAUSED 5 OCT 2026 No change at the confirm screen for now: Journey 3 does not intervene at this step. Removed as a requirement for this journey.
The last-step check · Braze push, email
Braze Push, Email: push where held, else email
Confirm-screen abandoners: about 10,300 a month on the assumed splitPAUSED 5 OCT 2026 No message is sent when a customer leaves at the confirm screen, for now. Removed as a requirement for this journey; the confirm-abandon event (D6) is parked with it.
The dead-end answer
Native Screen Or Modal
Searchers whose route is not covered, or whose auction window has not openedWaits on an app release.
The abandoned search
Braze Push, Email: push where held, else email
Searchers who saw results for a route and left without opening an auction, and did not come back on their ownWaits on an app release.
Working detailPack version: 14 Oct 2026, 09:01 (London)