◆ Mailchimp

Send internal test emails

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSend an internal test email of the new welcome series to the product and support leads for…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I send internal tests, make the review easy: surface any personalization tokens and…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI sent the test welcome email to Alice and Marco; Alice reports seeing raw token text instead…+
Alice replied with inconsistent personalization in the test
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?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe lose time because internal tests repeatedly reveal personalization tokens and image-hosting…+
We keep discovering token and rendering issues during reviews
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?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Mailchimp's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.