A pre-send check should follow the message from audience selection through suppression, rendering, links, and the action after the click. A successful test send to one inbox does not verify the campaign audience or destination.
Use a release sequence
- Audience: confirm segment definition, consent basis, exclusions, suppression, and send count.
- Content: verify offer, prices, eligibility, dates, language, and every claim against the approved source.
- Links: open each destination on mobile; check redirects, language, UTMs, and fallback text links.
- Rendering: test representative email clients, Arabic direction and shaping, dark mode, and blocked images.
- Action: submit the form or complete the next step using a test path; confirm the event and follow-up.
- Ownership: confirm sender identity, reply inbox, schedule, time zone, and who can pause the send.
Send an internal proof with test labels before the real audience. Verify that test addresses cannot contaminate production reports or trigger fulfillment. For a high-risk or large send, use an approved staged rollout rather than assuming a small proof catches every issue.
Record the release
Save the approved version, audience count, reviewer, test evidence, scheduled time, and rollback owner. After sending, inspect delivery and errors promptly, then review complaints, clicks, and downstream actions with clear denominators. If a critical link or claim is wrong, use the incident process; do not send another campaign until the cause is contained.
Optional AI-assisted work brief — Campaign preflight checklist
Check audience eligibility and suppression, rendered text in supported clients, Arabic direction, links and tracking, personalization fallbacks, accessibility, sender identity, time zone, and approval. Send test cases for missing fields and long names. Confirm the destination and unsubscribe path. A successful test send is not proof the live audience or scheduling rules are correct.
Worked example — Find the Arabic rendering failure
A test email may show the Arabic greeting correctly but render a mixed Arabic-English tracking link in the wrong direction. Inspect the actual mobile client, long names, missing personalization, alt text, link tracking, and unsubscribe. Save evidence from the rendered message. A desktop preview alone does not verify the live send.
AI disclosure: AI tools assisted with drafting. This QA sequence is an operating aid, not a guarantee of inbox placement.