Email marketing

How to Create Automated Domain Warmup Schedules for New Sending Accounts

Build a warmup schedule driven by how recipients respond. Engaged contacts first, per-provider throttles and written pause rules, so the ramp slows itself when it should.

A man drawing an email marketing workflow strategy diagram on a whiteboard
Photo by Campaign_Creators

Thirty days on a spreadsheet won't warm a domain. Recipients warm it. Mailbox providers decide how to treat a new sending domain by watching what real people do with its mail: who opens, who clicks, who deletes it unread, who marks it as spam. An automated domain warmup schedule is only worth running if it reacts to those signals. It should speed up when people engage and slow down the moment they stop.

The calendar still has a job. Days and daily volumes give you a starting estimate and something concrete to show the client. Three inputs protect the client's sales emails, and you set them before the first send. You warm with the most engaged contacts first. You throttle per mailbox provider. You write pause rules that slow the ramp as soon as bounces or complaints rise. Set those well and you can let the automation run. Set only a daily volume curve and you're guessing.

We've covered why warmup prevents new accounts landing in spam in a separate article, so this one is the build. There are eight steps. Each one gives you the action, what you should see when it's done, and the mistake that catches agencies out at that point.

By the end you will have a warmup schedule that runs itself and stops itself when it should

Here's what you'll have when you finish. A new sending domain that's fully authenticated. A cleaned list split into engagement tiers. A volume curve that moves from one tier to the next only when the current tier performs. Dispatch speeds limited per mailbox provider. A written set of pause rules the client has agreed to. And the client's real campaigns slotted into the ramp, so the warmup weeks bring in sales instead of costing six weeks of silence.

Get these together before you start. Each one takes longer to chase halfway through than it does to collect now.

  • Access to the client's DNS, or a named person on their side who can publish records the same day you send them.
  • A brand-matched secondary sending domain, or the budget and approval to register one.
  • The client's existing contact list, with whatever open and click history they have from past sends.
  • The client's campaign calendar for the next four to six weeks, so real sends can be placed into the ramp.
  • One decision-maker at the client who signs off the pause rules before anything goes out.

So what's left for you if the platform handles warmup? On SendTo, warmup is applied automatically to new sending domains. Addresses are verified before sending, dispatch speed is governed per provider and per domain, and campaign volume is spread across brand-matched sending domains. Your agency still makes the decisions that shape the result. You choose who goes in the first tier, which campaigns go out in which week, where the pause thresholds sit, and what you tell the client when a hold happens. The automation carries out your inputs. It doesn't choose them for you.

Step 1: Authenticate the domain before a single email leaves it

The action is to publish three records on the sending domain. SPF names the servers allowed to send for it. DKIM signs each message so receivers can tell it wasn't altered on the way. DMARC tells receivers what to do when the other two fail, and where to send reports. Start DMARC at p=none with reporting switched on. You want visibility first, enforcement later.

Host: _dmarc.mail-clientbrand.com
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@mail-clientbrand.com; adkim=r; aspf=r

Then check alignment. The domain in the visible From address has to match, or share an organisational domain with, the domain that passes SPF or DKIM. If the From line says the client's brand but the DKIM signature belongs to some other domain, DMARC fails even though each record passes on its own.

You'll know it worked when a test send to an inbox you control shows spf=pass, dkim=pass and dmarc=pass in the message headers, with the From domain matching. Use the original message view, not the preview pane.

This matters more from this week than it did last month. Starting in February 2024, the largest mailbox providers expect bulk senders to authenticate with SPF and DKIM, publish a valid DMARC record, offer one-click unsubscribe, and keep spam complaints below 0.3%. A brand-new domain gets no grace period for being new. It has to meet all four from its first send, which is one more reason to set this up properly before the ramp begins.

Why the first two weeks of DMARC reports matter

DMARC reports show every source sending mail as the domain. On a fresh secondary domain, the only sender should be your platform. If the reports show a forgotten booking tool, a CRM or an unknown server sending as the domain, stop and fix that before you ramp. Otherwise mail you don't control is spending the reputation you're trying to build.

Step 2: Warm a secondary sending domain, never the client's main one

The client's main domain carries their invoices, staff mail, password resets and replies to customers. If a warmup goes wrong there, the damage lands on all of it. So register a brand-matched secondary sending domain and point it at the platform. Something like mail-clientbrand.com or clientbrandnews.com works. For clients who send high volumes, register two or three, so no single domain carries the full load.

When this step is done, the domain shows as set up on the platform, its Step 1 records resolve, and it's ready to receive the warmup schedule. On SendTo, warmup starts automatically on new sending domains and campaign volume is spread across the brand-matched domains you add.

Does every secondary domain need its own ramp? Yes. Reputation belongs to each domain. A domain you warmed in March gives no credit to one you register in April, even when both point to the same brand. Plan each new domain as its own ramp from a small first day, and add domains well before the client's volume needs them.

The mistake here is choosing a domain that looks unrelated to the brand. If a bakery's newsletter arrives from a random string of words, recipients read it as phishing and report it. Those complaints land right when the domain can least afford them. Put the brand name in the domain, keep it short, and use the same From name the client's customers already know.

Step 3: Clean the starter list so the ramp begins with zero bounces

Import the client's list and let verification run before anything goes out. On SendTo, imports map spreadsheet columns automatically and resume if an upload is interrupted. Every address is verified before sending, which removes invalid, role-based and risky addresses, and platform-wide suppression filters out contacts who've unsubscribed or complained before. We've written more on verifying the list before sending if your client doubts that cleaning is worth it.

Expect the list to come out smaller than the client thinks it is. Take Priya, who runs a garden-supply shop. She handed her agency 18,400 contacts collected over nine years. After verification and suppression, 13,100 were left. The rest were dead addresses, typos, shared inboxes like info@ and sales@, and people who'd unsubscribed in a tool she'd stopped using in 2019.

The mistake is arguing the client back into keeping the old addresses. A hard bounce in week one of a new domain does far more damage than the same bounce in month six, because there's no positive history to dilute it. Those 5,300 contacts weren't going to buy anything. Some of them were going to bounce on day one.

Step 4: Tier the audience so the first sends go to people who will open them

This step decides whether the warmup works. Split the cleaned list by how recently each contact engaged, and send to the most engaged tier first. Providers learn what your domain is worth from how its first recipients react. If those recipients open, click and reply, the domain starts out looking like mail people want. Build the tiers from segments built from past campaign clicks and opens. On SendTo, you can segment by clickers, unclicked opens and non-openers from past campaigns.

A four-tier warmup audience, ordered by recent engagement
TierWho's in itWhen they enter the ramp
1Clicked in the last 90 daysFirst sends
2Opened in the last 90 days, no clickOnce tier 1 holds steady
3Opened in the last 6 to 12 monthsOnce tier 2 holds steady
4Everyone else on the cleaned listLast, and in small batches

Expect a small top tier. For Priya's 13,100 contacts, tier 1 came to 640 people. That's normal, and it's a good number. A few hundred people who click are worth more on day one than ten thousand who don't. Ignore any opens recorded by security scanners when you build the tiers. SendTo's reports leave them out, so the tiers are built on human opens only.

Can you warm a domain with a purchased or cold list? No. Those contacts never asked to hear from the client, so they ignore or report the mail, and the domain's first impression is the worst one available. Purchased lists also break the consent rules that the GDPR and similar laws set for marketing email.

With an authenticated secondary domain, a clean list and four tiers ready, you have the inputs the rest of the schedule depends on. Next comes the volume curve, and that's where the calendar finally gets its turn.

Step 5: Set the volume curve as a starting estimate, not a promise

The volume curve is where your automated domain warmup schedule gets its numbers. Use them as a forecast. Lay out a ramp that starts small and grows in modest steps, and tie each increase to a tier. Volume grows when the current tier has performed. The date on the calendar doesn't decide it.

So how many emails should you send on day one? Send to part of tier 1 and nothing else. For a small business list that's somewhere between one and three hundred people who clicked recently. The table below shows how Priya's 13,100 contacts were spread across her ramp. It's an example, not a rule. No mailbox provider publishes a required number for any day.

Example only. One illustrative ramp for a 13,100-contact list. These are not mailbox provider rules.
StageContacts per sendTiers includedMove on when
Week 1, first sends200 to 640Tier 1 (640)Bounces near zero, no complaints, clicks steady
Week 21,000 to 2,700Tiers 1 and 2Same signals hold at the larger size
Week 33,000 to 6,100Tiers 1 to 3No provider deferring or slowing delivery
Week 47,000 to 9,500Tiers 1 to 3 plus first tier 4 batchesTier 4 batches don't push complaints up
Weeks 5 to 6Up to 13,100Full cleaned listTwo normal-size sends land cleanly

How long does warmup take? Plan on four to six weeks for a list like this one. A list with a large, active tier 1 moves faster. A list that's mostly tier 4 moves slower, and that slower pace is the list showing you what it's really like.

When this step is done, you should see volume moving into the next tier only after the current tier has held. If week 2 ends with tier 2 still looking shaky, week 3 waits.

The mistake here is doubling every day because a forum post said so, or jumping from tier 1 straight to the full list because the first send went well. One good send to 640 engaged people tells you very little about how 7,000 colder contacts will react.

Step 6: Throttle by mailbox provider, because each one warms at its own pace

Before the first send, check how the list splits by receiving provider. Group the addresses by the domain after the @, and by the mail service behind each business domain. One large consumer inbox provider often holds half the list or more. Business domains spread across several providers, and each one filters in its own way.

Each provider forms its own view of your domain. A provider that has seen 300 of your emails doesn't care that another has seen 3,000. So dispatch speed has to be limited per provider and per sending domain. Otherwise the biggest provider on the list takes the whole spike at once. SendTo does this automatically. It governs dispatch speed per provider and per domain, so a send to 6,000 contacts goes out at a pace each receiver will accept.

When this is working, you'll see business domains and consumer inboxes receiving at different rates. A send can take an hour or two to finish. That's the throttle doing its job.

The mistake is treating the list as one audience. If one provider holds 60% of the contacts, that provider decides how the warmup goes. Watch its results separately, not blended into the average.

Timing spreads the load too. Delayed delivery and time-zone sending release a campaign in waves, timed to each recipient's local morning. That smooths the volume and puts the email in front of people when they're likely to open it.

Step 7: Write the pause rules that make the schedule safe to leave alone

With pause rules in place, you don't have to check every send by hand. Agree them with the client's decision-maker, write them down, and keep them next to the campaign calendar. Each rule names a signal and says what happens when it trips. Here's the set Priya's agency used.

  • Hard bounces above 2% on any send: hold the ramp and recheck the list source before the next send.
  • Deferrals or slowed delivery from one provider: hold volume to that provider only and send it tier 1 contacts.
  • Spam complaints above 0.1% on a send: hold. Above 0.2%: roll back one stage.
  • Clicks per delivered email down by half from the previous send: hold and review the content before adding the next tier.

Why 0.1% when the new bulk sender rules allow 0.3%? Because 0.3% is the ceiling. A domain that reaches it has already lost ground. Set your working target well below it, so a rule trips while there's still room to spare.

A hold doesn't mean you stop sending. Keep sending at the current volume to the tiers that are already warmed, and don't add the next tier until two sends come back clean. A rollback drops you back to the previous stage's volume and tiers, and you climb again from there.

What happens if you pause halfway through the warmup? A few days of silence costs little. Several weeks of silence costs more, because providers judge a domain on what it's done recently and older history fades. Restart a stage or two lower than where you stopped.

When this step is done, you'll have a short rule set that the client signed off before anything went out. The mistake is having no rules at all. Then a bad Tuesday turns into a bad week, because nobody had the authority to slow down.

Step 8: Slot the client's real campaigns into the ramp instead of sending filler

Warmup weeks don't have to be silent weeks. Use them for the sends the client was going to make anyway. A welcome sequence for new subscribers suits week 1, because those people signed up minutes ago and are expecting it. Newsletters and offers suit weeks 2 and 3, sent only to the tiers already in the ramp.

Run every send through SendTo's AI reviewer before it launches. It checks subject lines, structure, language, links, alignment and basic compliance. That way a broken link or a missing unsubscribe doesn't cost you engagement on a domain that has no history to make up for it.

When this step is done, you'll see real sales coming in during the warmup. Priya's spring seed offer went to tiers 1 and 2 in week 2, 2,740 contacts in all. It brought in 61 orders before the rest of her list had heard from her.

That's also how you handle a client who wants to launch next week. Don't argue about the timeline. Show them the calendar with their own campaigns in it, the engaged customers getting the offer first and everyone else following over the next month. They're not waiting six weeks. They're launching to their best customers now.

The mistake is sending throwaway test content, or a campaign that's one large image. Neither gives recipients a reason to click. Image-only emails also get less engagement and more filtering than text and HTML layouts. Warm the domain with the kind of email you want it known for.

How to tell the warmup worked, and what to do when it did not

How do you know warmup is finished? It's done when the full cleaned list is getting the client's normal campaign size and two sends in a row come back clean at every major provider. Check five signals on each send.

  • Steady inbox placement in the seed or test inboxes you control at each major provider.
  • Hard bounces close to zero, which they should be after Step 3.
  • Spam complaints well under your 0.1% working target.
  • No provider deferring or slowing delivery.
  • Human opens and clicks holding steady as each new tier joins.

Watch the opens closely in the first week. Security scanners at business domains open emails and click links automatically. That inflates early numbers and can make a weak send look strong. SendTo's reports leave scanner opens out, so the opens and clicks you see in the client portal and partner view come from people.

If one provider starts deferring or filtering

Hold that provider's volume and send it only tier 1 contacts until delivery recovers. Keep the other providers on schedule. Check that the last send passed SPF, DKIM and DMARC with alignment. Then look at what changed in the content, such as a new link domain or a heavier layout. Resume sending to that provider one stage lower than where it stalled.

If bounces or complaints climb

Pause the ramp and go back to list hygiene. Find out where the problem contacts came from. The usual cause is a batch added after the clean, or a list the client dug out of an old tool. Then check the opt-in source. If a signup form is collecting fake or mistyped addresses, bots are filling it in. Turn on bot protection for the form and switch on double opt-in, so only confirmed addresses join the list.

If the client needs a big send before the ramp ends

Send it to the warmed tiers only, spread it across the domains that are already warmed, and hold the rest of the list back for the next send. Be straight with the client about this. No shortcut makes a new domain old. A full-list blast in week 2 puts the next few months of sales emails at risk. Holding part of the list back for one send costs far less.

Your next step is the checklist at the top of this article. Collect DNS access, the secondary domain, the list, the campaign calendar and the decision-maker's sign-off on the pause rules. Then set the tiers and let the automation run on the rules you've written.

If you write for agencies that run email for their clients, you can recommend SendTo and earn 20% of the partner subscription each agency you refer pays SendTo, every month it pays. You never get a share of what that agency's own customers pay it. Attribution lasts 90 days from the first click, the first touch wins, and commission is paid monthly by PayPal.

Join the SendTo affiliate programme

Frequently asked questions

How long does it take to warm up a new sending domain?

Plan around four to six weeks, but treat the calendar as an estimate. The ramp only moves to the next engagement tier once the current one holds steady, so strong opens and clicks speed it up and rising bounces or complaints slow it down.

Can I warm a domain using a purchased or cold list?

No. Those contacts never asked to hear from the client, so they ignore or report the mail, and the domain gets the worst first impression it could. Purchased lists also break the consent rules the GDPR and similar laws set for marketing email.

Do I need to warm every secondary domain separately?

Yes. Reputation belongs to each domain, so one you warmed in March gives no credit to one you register in April, even for the same brand. Start each new domain with a small first day, and add domains well before the client's volume needs them.

Do warmup services that fake opens and replies actually help?

Not where it counts. That engagement comes from mailboxes that'll never buy anything, so it tells providers nothing about how the client's real customers treat the mail. Once real sends start, the domain gets judged on those.

What do the February 2024 bulk sender rules mean for a brand-new domain?

There's no grace period for being new. From its first send, the domain needs SPF and DKIM, a valid DMARC record, one-click unsubscribe and spam complaints under 0.3%. Get alignment passing before the ramp starts, even if that pushes the first send back a few days.

If the platform warms domains automatically, what's left for my agency to do?

SendTo applies warmup, verifies addresses and limits dispatch speed per provider for you. You still pick who goes in the first tier, which campaigns go out in which week, where the pause thresholds sit and what you tell the client when the ramp holds.

Everything this blog teaches, on a platform with your name on it.

Email campaigns, websites, landing pages and print for your clients, made from a short brief and sent under your brand. Create your account and look around with a sample workspace loaded.

No contract · Cancel any time · Explore everything before you pay