Rechurn
Customers lapsed beyond 24 months - treated closer to acquisition than to retention.
Vertical: Program · Status: ⬜ Planned Back to Program · workflows index
Who it targets
A2 inactive base, over 24 months. The whiteboard keeps them in retention, but operationally the relationship has ended.
Trigger
Promotion out of Closure at 24 months. No upper bound is defined on the roadmap.
Flow
select inactive >24m
|
consent re-confirmation <- the gate that matters here
|
treat as cold: full value proposition, not a reminder
|
generate message [Creative Agent]
|
compliance review [Compliance Agent]
|
dispatch, low frequency [A5 dispatcher]
Data it needs
| Needs | Have |
|---|---|
| Original relationship record | ⬜ |
| Consent still valid at this age | ⬜ |
| Suppression against current active base | ⬜ |
Agents involved
Creative Agent - Compliance Agent.
Blocked on
CRM integration and the BTL channel layer - neither started.
Additionally: consent at this age is the real blocker, not the channel.
Roadmap source
Page 2 - A2 Inactive -> Rechurn -> >24m — see roadmap_ref_extracted.md.
Design notes
- Consent obtained three years ago may not be valid to message against today. This needs a legal answer before the workflow is designed, not after.
- Expect the lowest response rate of any Program workflow. Size the effort accordingly - this is the bucket most likely to fail a cost-per-response test.