## Test email flows before launch
1. Send your first tests to the documented Resend test addresses, for example the delivered address, to confirm the API path works without touching real inboxes. Docs: https://resend.com/docs/knowledge-base/what-email-addresses-to-use-for-testing
2. Test the failure paths too: send to an address that will bounce and confirm your webhook ingester records the bounce and the address lands suppressed. A launch-day bounce storm with no handler is a deliverability disaster.
3. Click every unsubscribe link in a test mail and confirm the contact state changes. Then send the same marketing mail again to that address and confirm it is skipped, not delivered.
4. Render-check every template in the major clients: Gmail web, Outlook, Apple Mail, and one mobile client. React Email helps, but always eyeball the output; table layouts still surprise people.
5. Fire each automation's trigger event in staging and watch the run complete in the dashboard. Confirm delays fire on schedule and conditional branches take the right path before real users trigger them.
6. Verify the from domain shows correctly and authentication passes (SPF, DKIM, DMARC aligned). A test mail that lands in spam in staging will land in spam in production.
7. Do a final suppression cross-check on your launch list, then send. Keep the first production send small and watch the webhooks; if anything looks off, you have only affected a few recipients.