Agency campaign launch checklist: separate client approval from execution

Define the decision

An agency may control the sequence while the client controls the mailbox, offer and sales response. That split creates gaps unless the handoff is concrete. A client approving copy does not necessarily approve a particular list, a volume increase or a promise about response time. State those decisions separately.

Work through the procedure

1. Have the client verify offer details, claims, named examples and the sender's authority to represent the business.
2. Define the target segment and exclusions, including customers, active opportunities and prior opt-outs. Agree who supplies updated exclusion data.
3. Assign reply review and escalation ownership, with a practical coverage schedule. Specify who handles interested replies, complaints and technical failures.
4. Agree the launch cohort and reporting dictionary. Distinguish contacted people, human responses, interested responses and meetings instead of presenting one ambiguous conversion rate.

Worked example

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

Client launch approval
Offer owner: client operations lead
Audience owner: agency researcher; exclusions supplied by client
Sender owner: client mailbox administrator
Reply owner: named salesperson
Report: unique contacted people and reviewed human outcomes
Expansion: requires review of the initial cohort

Read the result

This record makes accountability visible before a prospect replies. It also prevents a later dispute where one party assumed the other was watching the inbox. The initial cohort is a review boundary, not a claim that small volume alone guarantees appropriate targeting or successful delivery.

Check before moving on

1. Confirm the approved sender signature and destination links belong to the intended client.
2. Store the approved version so later copy edits can be traced.
3. Test the reply handoff with an internal example before launch day.

Limits and next action

This checklist is an operating aid, not a legal approval form or a substitute for the client's policies. It does not imply native client-approval automation in Zintara. Use the sequence product flow for execution and maintain a separate approval record when needed.

Source: Zintara sequence product context