Email QA Gates Skill

When to Use

Prior to activating new nurture or lifecycle programs.
After major changes to segmentation, personalization tokens, or deliverability settings.
During post-incident reviews to ensure fixes remain in place.

Content & Personalization – placeholders resolved, links tracked, dynamic content fallback tested.
Data & Routing – trigger logic, smart lists, suppression rules, CRM fields synced.
Compliance – footer language, preference center links, consent status, regional routing.
Tracking & Analytics – UTM/tagging consistency, BI/warehouse pipes, alert webhooks.
Monitoring Hooks – dashboards referenced, alert thresholds set, rollback plan documented.

QA runbook with owner, status, evidence links for each checklist item.
Proofing matrix (persona × email × device × ISP) for screenshot validation.
Launch readiness form requiring sign-off from marketing, ops, legal, and RevOps.

Pair with deliverability-ops to confirm authentication and inbox monitoring.
Automate regression tests via API where possible (token validation, link health).
Store QA evidence (screenshots, logs) alongside sequence assets for audits.