Assign an Owner to Every Lifecycle Email Exit Condition

Do not launch a lifecycle sequence until every exit condition has a named system owner and an in-flight test. Content ownership is not enough: conversion, cancellation, churn, refund, opt-out, bounce, complaint, and support escalation must each stop or reroute the next message predictably.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Sources were refreshed on September 6, 2026.

Migma's lifecycle recipes cover welcome, onboarding, product update, re-engagement, payment failure, and win-back messages. The same guide says event-triggered flows should be exported to the ESP or automation tool that owns the trigger. That boundary matters: the system that drafts the series may not own eligibility at delivery time.

Create the ownership table#

Scroll table →

State transition	Source of truth	Detection path	Sequence action	Maximum latency	Owner
Lead → customer	Billing or CRM	Verified event or field change	Exit nurture; enter onboarding if consent allows	Named bound	Lifecycle operations
Trial → paid	Billing	Subscription event	Cancel trial reminders	Named bound	Billing automation owner
Active → cancelled	Billing/CRM	Cancellation event	Exit renewal; consider bounded save flow	Named bound	Retention owner
Payment failed → recovered	Billing	Payment success	Cancel remaining dunning messages	Named bound	Revenue operations
Any → unsubscribed	Preference system	One-click, center, mailto, or API	Suppress marketing immediately	Fail closed	Consent owner
Any → hard bounce/complaint	Delivery provider	Provider event	Global or scoped suppression	Fail closed	Deliverability owner
Any → legal/support hold	Case system	Approved hold record	Pause specified messages	Named bound	Compliance/support owner

The source-of-truth field must identify a concrete object and value, not a department name.

Separate event from permission#

Migma's events guide says events can record trials, upgrades, cancellations, purchases, and refunds but never change subscription status. Keep lifecycle and consent as separate axes. A cancellation can make a win-back message relevant, but it does not create permission to send one.

Use the most restrictive state across the preference center, source CRM, destination ESP, and suppression store. Reconcile disagreement before queuing the next message.

Test exits while messages are in flight#

Create synthetic contacts for each transition. Enter the sequence, then apply the exit:

before audience evaluation;
after audience snapshot but before scheduling;
after scheduling but before provider queueing;
after one message sends but before the next delay ends;
during a retry or destination outage.

Record whether the platform removes the contact, cancels queued messages, merely blocks future evaluation, or requires an explicit cancellation action. “Exited automation” does not prove a message already handed to a provider was recalled.

Bind content to state#

For each email, record the allowed entry states, prohibited states, required consent or service basis, maximum data age, and the transition that invalidates its copy. A payment-failure reminder becomes false after recovery; a trial-expiry warning becomes misleading after conversion.

email: "trial-expiry-02"
allowed_states: ["trial-active"]
prohibited_states: ["paid", "cancelled", "refunded"]
consent_basis: "documented per message class"
state_source: "billing.subscription.status"
max_state_age_minutes: 15
exit_action: "cancel remaining trial reminders"
owner: "billing lifecycle"

Migma's integration overview separates preparation from final send or export approval. Preserve the state record when handing content to the execution platform.

This page complements the campaign capacity waiting-state runbook. Include destination cancellation semantics directly in the sequence test because a platform waiting state and a customer eligibility exit are different controls.

Stop conditions#

Stop when one system owns entry but nobody owns exit, consent is inferred from lifecycle state, latency has no bound, scheduled messages cannot be enumerated, provider-queued mail is assumed recalled, or a state change can make the remaining copy false or harmful without triggering review.

Evidence limits#

Marketing Wiki did not run a Migma series or destination automation. Documentation supports content recipes, events, segments, preferences, and handoff boundaries. Exit semantics depend on the actual CRM, billing system, ESP, queue, and provider configuration.