Sending domain warm-up schedule for a new email domain
Builds a day-by-day warm-up plan for a new sending domain or IP, starting with the most engaged contacts and raising volume only while bounce and complaint rates stay low. Use it when moving to a new email platform, a new domain or a dedicated IP before the first large campaign.
The output this prompt produced, unedited.
The prompt
What to give
New domain or IP, and platform: [e.g. a subdomain such as mail.[domain], a dedicated IP on an email platform]
Total list size: [e.g. 60,000]
Engagement groups available: [e.g. opened in last 30 days 8,000; 31 to 90 days 15,000; older 37,000]
Target daily volume after warm-up: [e.g. 20,000]
Planned first big send and date: [e.g. festive sale on a fixed date]
Mailbox provider mix, if known: [share of the largest providers, or unknown]
Check before day one
SPF, DKIM and DMARC records set and passing for the sending domain.
Custom tracking and return-path domains aligned with the From domain.
One-click unsubscribe header and a visible unsubscribe link.
Bounces and past unsubscribes suppressed.
Postmaster or reputation dashboards from the main mailbox providers registered.
Output format
| Day | Daily volume | Segment sent to | Content type |, covering about four weeks, starting with the most engaged group.
Thresholds: hard bounce above 2 percent or complaints above 0.1 percent means pause; deferrals rising means hold the volume for two days.
What to send in the first week: content people expect and like, never the hardest-selling campaign.
When the older groups may be added, and a re-permission email for contacts older than a year.
Daily checks during warm-up in five bullets.
Guardrails
If the first big send falls before warm-up can finish, say so and suggest a smaller send to engaged contacts only.
Never suggest buying lists or rotating domains to avoid reputation problems.
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.