◆ Mailchimp

Manage bounced 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 taskThis morning the automations show 312 hard bounces from yesterday’s newsletter. Forward the…+
This morning the automations show 312 hard bounces from yesterday’s newsletter. Forward the bounce list to Priya in ops and to our ISP contact, ask Priya to confirm which addresses match recent purchase records, and request that the ISP investigate DNS and sending quota issues. Ask for replies by 3pm today so I can suppress them before the next 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 hand the bounce file to operations, make it actionable: group bounces into hard and…+
Before I hand the bounce file to operations, make it actionable: group bounces into hard and soft with counts, flag addresses that belong to active customers in the CRM, highlight any domains with repeated failures, and suggest the exact suppression list to apply so ops can run it without questions.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentYesterday’s newsletter produced 312 hard bounces; some are customers who bought within the last…+
Newsletter returned many hard bounces.
Yesterday’s newsletter produced 312 hard bounces; some are customers who bought within the last month. I don’t know if these are stale addresses, a sending reputation hit, or a credential/DNS problem. What sequence of checks should I run immediately to decide whether to suppress, retry, or escalate to our ISP?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe repeatedly get spikes in hard bounces after big blasts and I spend hours coordinating manual…+
I keep getting bounced lists after big blasts.
We repeatedly get spikes in hard bounces after big blasts and I spend hours coordinating manual cleans with ops. What process or habit change would cut that cycle so bounces are caught earlier and our delivery reputation doesn’t crater every quarter?
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.