The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+We have a high-volume campaign for the product launch. Limit the send to 10,000 emails per hour and…
Execute — do the immediate task
+We have a high-volume campaign for the product launch. Limit the send to 10,000 emails per hour and pause after each batch until deliverability checks pass. Start the first batch at 08:00 on Monday. Before each batch releases, check that our sending domain has no new bounce spikes and that the ESP reports healthy engagement the previous hour.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I set hourly send limits for the launch, make the plan easy for the head of deliverability…
Improve — make it easier to accept
+Before I set hourly send limits for the launch, make the plan easy for the head of deliverability to approve: show projected hourly volume, current sender reputation score, and the rationale for 10,000/hour. Flag thresholds that should automatically stop the campaign—bounce rate over 2%, complaint rate above 0.1%, or ISP throttling signs—and recommend a backoff rate if any trigger fires.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+We scheduled a product launch with a 10,000/hour cap. Early metrics show engagement higher than…
Decide — diagnose the stuck moment
+Traffic spiked and I need to decide whether to raise the hourly cap
We scheduled a product launch with a 10,000/hour cap. Early metrics show engagement higher than expected and limited bounces, but the CEO wants faster reach. I worry raising the cap could trip ISP throttling. What is the likely immediate risk if I double the cap, what quick checks decisively show it's safe, and what is the safest incremental change to propose now?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across three launches we set conservative per-hour caps and still hit ISP throttling or delayed…
Become — change the pattern
+We keep hitting ISP throttles during big launches
Across three launches we set conservative per-hour caps and still hit ISP throttling or delayed deliveries. I own campaign pacing and coordination with product. Where am I losing control: inaccurate list hygiene forecasts, inconsistent ISP relationships, or poor early engagement gating? Recommend one habit to stop ISP throttles in the next launch and one team change to reduce this risk permanently.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other email marketing work people do in Mailchimp.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.