Send internal test emails

Send an internal test email of the new welcome series to the product and support leads for review. The subject should include TEST and the build name. Send to Alice in Product first, then Marco in Support, and set a 48-hour review deadline. Confirm the tracking link behaves like the live email and that images and personalization tokens render correctly before any external send.

Before I send internal tests, make the review easy: surface any personalization tokens and where they pull data from, list links that need to be checked, call out images that are hosted externally, and flag any timing or audience assumptions that would make a reviewer hesitate to approve.

I sent the test welcome email to Alice and Marco; Alice reports seeing raw token text instead of a first name, and Marco didn’t get the scheduled send time indicated in the header. I don’t know whether this is a template error or a test-address issue. What should I check first to diagnose which problem will block approval and how do I get a quick fix before the 48-hour deadline?

We lose time because internal tests repeatedly reveal personalization tokens and image-hosting problems that should have been caught earlier. I need one small habit to stop this leak of review cycles and missed deadlines. What preflight step or naming convention will surface these issues before the test goes to Product and Support?