Journey orchestration is the automated, multi-step coordination of CRM messages and offers across channels, conditional on each player's behaviour and lifecycle stage.
Journey Orchestration
**TL;DR:** Journey orchestration is the automated, multi-step coordination of CRM messages and offers across channels, conditional on each player's behaviour and lifecycle stage.
What it means
Where traditional CRM was a calendar of mass blasts, orchestration treats each player as moving through a state machine: registered → FTD → 2nd deposit → first withdrawal → dormant → reactivated → VIP. At each node, rules and ML models decide the next message, channel (email, push, SMS, in-app, on-site banner, agent call), timing, and offer.
Platforms like Optimove, Solitics, Smartico, Iterable, Braze, and CRM-native tools (Fast Track) handle this. iGaming-specific orchestration also needs RG and compliance gates baked in: a self-excluded user must exit every journey instantly.
Formula / How it's measured
Not applicable — it is a discipline, not a metric. Mechanism: an event bus streams deposits, sessions, bets into the orchestration engine; rules + models evaluate per player; channel APIs (SendGrid, OneSignal, Twilio, push SDKs) execute. KPIs include journey conversion %, channel performance, and journey-attributed NGR.
Example: a sportsbook's FTD-to-2nd-deposit journey: Day 1 push reminder of in-play match → Day 3 free bet email if no 2nd deposit → Day 5 SMS if still inactive → Day 7 exit. Journey conversion 2nd dep = 38% vs 22% baseline.
Why it matters for operators
Orchestration is how CRM scales without ballooning headcount and how operators avoid message overload that drives unsubscribes and RG complaints. Done well, journey-driven NGR can be 25–45% of total CRM-attributed NGR.
Common benchmarks (2026)
- Active journeys per mid-size operator: 40–120
- Channels typically blended: email + push + SMS + in-app + on-site
- Lift vs broadcast CRM: +20%–60% on target KPI
- Common tools: Optimove, Smartico, Solitics, Fast Track, Braze
- Tier-1 operators run real-time decisioning across 5+ channels
Common mistakes
- Over-messaging — no global frequency cap across journeys
- Ignoring negative outcomes (RG, churn risk) in optimisation
- Building journeys without exit conditions; users stay forever
See also