◆ Mailchimp

Send a test email

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 taskBefore the full send, email a test version to me and to Priya in content on Thursday by noon.…+
Before the full send, email a test version to me and to Priya in content on Thursday by noon. Use three test addresses that represent a Gmail inbox, an Outlook desktop, and an iPhone Mail app. Confirm that links, images, personalization and the unsubscribe link all work, and note any rendering issues.
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 acceptMake the test email make approvals fast. Include a screenshot of how the message appears on…+
Make the test email make approvals fast. Include a screenshot of how the message appears on desktop and mobile, report missing alt text and any links that go to staging instead of production, and list any merge tags left unresolved. Highlight one issue that would make a reviewer hold the send.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy test email looked fine on desktop but the mobile preview stacked blocks badly and the CTA…+
Test email displayed broken layout on mobile
My test email looked fine on desktop but the mobile preview stacked blocks badly and the CTA was off-screen. I’m worried we’ll lose clicks and trigger complaints. I don’t know which content block or CSS is causing it or whether it affects only certain devices. What quick diagnostic pinpoints the offending block, what immediate fix gets the CTA visible, and how do I rerun a focused test before Friday?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep sending after quick tests and later find rendering problems across clients. That…+
We run informal tests that miss key viewports
We keep sending after quick tests and later find rendering problems across clients. That creates rework and small but recurring revenue loss. Suggest a standard testing checklist for desktop, mobile, and major clients, one small automation or workflow to capture screenshots automatically, and a required approval gate so nothing goes live without these checks.
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.