Pre-send QA checklist

Validate every row

Run the full list through the public Email Validation API before any send decision. Every row should end with one canonical status from the validation contract.

• Canonical statuses are valid, valid_role_based, invalid, risky, and unknown.
• Do not collapse statuses into local aliases like good or bad.
• Use the public API base URL with X-API-Key authentication, not website-internal routes.

Separate personal from role-based

valid_role_based is a first-class status, not a subtype of valid. Personal and role-based addresses usually deserve different outbound treatment.

• Count only valid personal results as High-Value Validations.
• Decide explicitly whether role-based addresses belong in the campaign.

Give risky catch-alls a recovery decision

Risky catch-all rows should not be silently dropped or blindly sent. Opt-in Premium Catch-All Recovery adds confidence and recommended action fields on a completed validation job without changing the canonical risky status.

• Route recovery output into send, manual review, or suppress segments.
• Recovery is non-intrusive and does not send verification emails.
• Recovery fields never overwrite the canonical validation status.

Handle unknown outcomes deliberately

unknown means the validation could not produce a confident outcome. It is treated as non-chargeable uncertainty under the documented credit policy, and it deserves an explicit routing rule rather than a default send.

Reconcile credits before launch

Before declaring the list send-ready, reconcile credits_reserved, credits_consumed, and credits_refunded from the validation economics summary. credits_charged remains a compatibility alias for consumed credits.