Consent and boundaries

1.1 Define one primary business job

Give the flow one primary job. A flow can support several outcomes, but one outcome should govern the sequence.

Choose one:

• Orient new subscribers to a topic and point of view.
• Help qualified subscribers evaluate one offer.
• Move free-resource readers toward a relevant paid next step.
• Prepare customers to use a product they already bought.
• Route subscribers into the right ongoing content path.

A useful goal statement names the person, the observable action, and the time horizon without inventing a target:

Help new checklist subscribers understand the core planning method and decide whether to review the paid implementation system during the first welcome cycle.

Avoid goals such as "maximize revenue" or "nurture leads." They do not tell a writer what to include or an operator what to measure.

1.2 Record the subscriber promise

Write down the exact promise made at signup:

• What did the person request?
• What sending identity was shown?
• Was promotional email disclosed?
• What frequency expectation was stated?
• Which privacy notice and consent language applied?
• How can the person unsubscribe or change preferences?

Your welcome flow should not exceed the reasonable scope of that promise. A resource request is not blanket permission for unrelated promotions. Laws and platform requirements differ by location and context. Obtain qualified legal advice for your situation.

1.3 Establish operating rules

Before drafting, decide:

• Suppression rules for unsubscribed, bounced, complained, or ineligible contacts.
• Entry and re-entry rules.
• Exit rules after purchase, reply, or preference change.
• Delay logic and local-time constraints.
• Sender name, reply route, and monitored inbox.
• Data retention and access practices.

Decision gate: Do not draft until you can explain why each person is eligible to receive every message in the flow.