📖Library
Each use case has its own dedicated one-pager, structured like this:
Trigger Purpose: Define the event or condition that starts the Co-Pilot process for this use case. What to include:
Segment definition or behavioral trigger (e.g., “user inactive for 45 days”)
Any filters or audience rules
When and how this segment is refreshed
Action Flow Options Purpose: List the available actions Co-Pilot can choose from when the trigger fires. What to include:
Each possible action (email, SMS, push, wait, etc.)
Channel logic (e.g., if no phone number, fallback to email)
Control group behavior (if applicable)
Co-Pilot Exploration Purpose: Explain how the Co-Pilot rotates actions, tracks results, and eventually converges on the best strategy. What to include:
The logic of random rotation and learning
How performance is evaluated (e.g., clicks, conversions)
How long exploration typically takes
Next-Best-Action Push Purpose: Show how the selected action is delivered to downstream systems (CRM, marketing automation). What to include:
Channels or tools used to push the NBA
Any personalization or segmentation applied
API or sync details (if needed)
KPIs Purpose: Define how success is measured for this use case. What to include:
Primary metrics (e.g., reactivation rate, click-through rate)
Secondary metrics (e.g., downstream purchases, unsubscribe rate)
Timeframes and benchmarks (if available)
Last updated
Was this helpful?