Design a Full Win-Back Program in One Session
Architect a multi-tier program conversationally — map coverage gaps, define tiered segments, and produce a send-volume calendar before you launch.
Designing a win-back or lifecycle program usually means juggling spreadsheets, segment logic, and a calendar across several sessions. With the Optimove MCP, a marketer can do the whole design pass in one conversation: surface where current Streams leave lifecycle-coverage gaps, propose a tiered segment structure, draft the segment definitions, and generate a send-volume calendar to sanity-check volume before anything goes live.
The same conversation supports two supporting plays that pair naturally with program design: campaign-coverage heatmaps that show which segments are over- or under-contacted, and a rolling send-volume calendar that reveals peak days and coverage gaps at a glance across large send volumes.
What you need to run this on the Claude branch.
| Ingredient | What to use |
|---|---|
| AI assistant | Claude (Desktop or Cowork) |
| Connector | Optimove MCP |
| Optimove data | Lifecycle stages, Streams, Target Groups, campaign and send history |
| Optimove products | Optimove Orchestrate (Streams, Target Groups) |
Copy this into your assistant with the Optimove connector on. Replace anything in [brackets].
Using the Optimove MCP, help me design a win-back program for lapsed players. 1. Pull lifecycle-stage counts and show me where our current Streams leave coverage gaps 2. Propose a tiered segment structure (aim for ~12 tiers) based on recency, value, and prior activity, and draft the segment definitions 3. Generate a 30-day send-volume calendar so I can see peak days and gaps before we launch
A clickthrough that maps coverage gaps, tiers the segments, and previews the send-volume calendar.
The flow, step by step:
Map the current coverage. Ask Claude for lifecycle-stage counts and a coverage read across your existing Streams. It highlights stages with little or no active journey.
Define the tiers. Claude proposes a tiered segment structure across recency, value, and prior activity. Refine the number of tiers and thresholds in chat until it fits your program.
Draft the segments. For each tier, Claude drafts a segment definition you can review and adjust before creating it in Optimove.
Build the send-volume calendar. Ask for a 30-day calendar of projected sends across the new tiers. Claude surfaces peak days and gaps so you can rebalance.
Hand off to build. Once the design is approved, use the drafts to create the Target Groups and Streams in Optimove.
A gaming operator defined 12 tiered segments in about 90 seconds and produced 17 segment drafts in a single morning, all in chat. The same team built campaign-coverage heatmaps and a Streams lifecycle-coverage map to spot gaps, then generated a 30-day send-volume calendar covering more than one million sends across roughly 349,000 unique players — seeing peak days and coverage gaps at a glance.
defined in ~90 seconds
segment drafts in one morning
mapped on a 30-day calendar across ~349K players
Does Claude create the segments automatically?
It drafts the definitions for you to review. You stay in control of what actually gets created in Optimove.
How accurate is the send-volume calendar?
It is based on the segment sizes and cadence you define, so treat it as a planning projection to catch peaks and gaps before launch, not a guaranteed send count.
Can I use this for onboarding or reactivation instead of win-back?
Yes. The same pattern — map coverage, tier the segments, project the calendar — works for any lifecycle program.