Choose one customer action the flow should support.
Define entry, exclusions, exit and re-entry before writing messages.
Draft a useful message for the first unmet need.
Check late events, unsubscribe and repeated entry with synthetic cases.
WORKED EXAMPLE
What a useful result looks like
Fictional example: a free resource visitor separately opts into updates. Entry is a confirmed subscription, not the download request. Segment: English-speaking users interested in campaign measurement. Message 1 helps them check one conversion journey; it does not immediately push a broad paid offer. Exit on unsubscribe or complaint; re-entry is disabled. Before each send, check the latest suppression status. QA cases include an unconfirmed subscriber, a duplicate confirmation and an unsubscribe arriving after the message was queued. Outcome: completed measurement worksheet, with clicks recorded separately. This plan does not configure or send a real flow.
Scope and compatibility
Planning documents and draft instructions. No mail system, subscriber list, sending service or implemented automation is included.
The files are editable Markdown and CSV. The optional original plugin contains one skill for Codex; its instructions can also be used in a regular AI chat. No accounts are connected automatically.
Want help applying it?
Review one flow, map its events and agree implementation requirements with Mark. Sending and CRM access require separate agreement.