01
Describe the task
Plan one retention flow with a clear entry signal, message sequence, exit conditions, and copy that fits the brand.
Operate any store · Retention
Plan retention flows for your actual sending stack
Design retention sequences around real customer signals, then hand the copy to whichever ESP you use.
The workflow
Bring the truth. Make the next move clear.
02
Provide the working context
- The flow goal and the customer event that should trigger entry
- Your current ESP capabilities, available data fields, and sending constraints
- Brand voice, product proof, approved incentives, and suppression rules
03
Review how Claude handles it
- Maps the entry, wait, branch, exit, and suppression logic before writing messages
- Drafts email and SMS variants without assuming a particular ESP interface
- Keeps product claims and incentives within the supplied approvals
- Creates a QA sheet covering links, fields, timing, overlap, and measurement
What you get
A tool-neutral retention flow specification with ready-to-review messages and a launch checklist.
Before you run it
Questions for this workflow
Does this retention workflow depend on a particular ESP?
No. The flow is specified as triggers, waits, branches, exits, suppressions, fields, and messages before anyone configures it in an interface. That makes the work portable to the email or SMS tool you already use, subject to its actual capabilities.
What context should I provide first?
Start with the flow goal and the customer event that should trigger entry. Then add your current ESP capabilities, available data fields, and sending constraints. Keep the source material current, remove sensitive information that is not needed, and tell Claude which facts are verified so gaps remain visible instead of being filled by assumption.
What should I review before acting on the result?
Review the source facts, assumptions, calculations, and any marked gaps behind this deliverable: A tool-neutral retention flow specification with ready-to-review messages and a launch checklist. Compare it with the live system or responsible teammate, and check before approving any action.
Keep moving
Related use cases
Setup
Connect Claude to the store you already run
Give Claude a trustworthy view of your store without changing platforms or pretending every stack has a connector.
Run this workflow
Product content
Turn one product truth into channel-ready copy
Build distinct product copy for each selling surface from one approved set of facts.
Run this workflow
Reporting
Build a weekly store performance brief
Convert the numbers you already review into a short operating brief with clear follow-ups.
Run this workflow