Campaign preflight checklist: approve the first real send

Define the decision

Separate copy approval from operational approval. The copy owner checks what the recipient will read; the operator checks who can receive it and what happens after a response. If either decision is unresolved, keep the campaign inactive. This prevents a polished message from concealing an incorrect audience or an unattended reply mailbox.

Work through the procedure

1. Choose the first cohort and record its source, selection rule and exclusions. Inspect individual records, including a missing first name and a long company name.
2. Preview every step using representative values. Follow each link and read the rendered signature and opt-out instruction. Remove claims that lack evidence.
3. Confirm the selected sending mailbox can send and receive. Assign a person to inspect replies during the launch period rather than relying only on a connected badge.
4. Record the campaign timezone, allowed days, window and capacity constraints. Ask the owner to approve the first cohort size explicitly.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Launch record
Cohort: 24 eligible operations contacts
Excluded: customers, suppressed addresses, uncertain company matches
Sender: named, tested mailbox
Review: copy approved; replies assigned to Maya
Schedule: Tuesday, campaign timezone
Decision: start only this cohort; review before adding more

Read the result

The number 24 is illustrative, not a universal safe volume. The useful feature is that every person belongs to a known cohort and someone owns the feedback. If the first messages expose broken variables or incorrect targeting, pause and repair the cause before broadening the audience. An absence of errors in one test does not establish future inbox placement.

Check before moving on

1. Keep the approved copy and cohort definition together so later edits can be compared with the launch decision.
2. Verify that opt-outs received during preparation are excluded from the actual launch.
3. Set a review time and a stop condition, such as any repeated rendering defect or unexplained send failure.

Limits and next action

This is an operator checklist, not a deliverability guarantee. In Zintara, selected accounts, enrollment state, due time and delivery controls all affect sending. Use the sequence overview to understand the product flow, and investigate a blocked enrollment before changing limits.

Source: Zintara sequence product context