- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
A first send of thirty thousand messages from a name nobody has seen looks exactly like the pattern the filters exist to catch.
An email list warm up plan: earning the right to be delivered
Mailbox providers decide whether your mail reaches an inbox based largely on how recipients have reacted to your mail before. A brand-new sending domain has no such history, so it starts neutral at best — and a first send of thirty thousand messages from a name nobody has seen looks exactly like the pattern the filters exist to catch.
Warming up is the process of building that history deliberately: small volumes to the people most likely to engage, growing steadily, while the technical foundations underneath are correct from the first message.
Get the foundations right before sending anything
No amount of careful volume ramping compensates for unauthenticated mail. Publish and verify the authentication records for the sending domain before the first send — SPF, DKIM and DMARC covers what each one does — and confirm the sending subdomain is configured in the platform rather than assuming it inherited something, which is the failure described in the workflow sender domain.
Check the wider zone at the same time. A single SPF record listing every service permitted to send, correct DKIM for the platform you are using, and a DMARC policy that starts permissive and tightens later: that combination is the minimum, and the inventory it sits inside is in the full set of records a domain holds.
Who to send to first
| Group | When to include | Why |
|---|---|---|
| People who confirmed recently | First | Most likely to open and reply, which is the signal being built |
| Recent customers | First | They recognise the name and expect to hear from you |
| Engaged in the last quarter | Early | Reliable engagement without much risk |
| Engaged within a year | Middle | Mixed, and worth watching closely |
| Older than a year, no engagement | Last, or never | Highest bounce and complaint risk, lowest return |
| Never confirmed, purchased or scraped | Never | Bounces and complaints that damage everything else |
Order matters more than speed. Sending to your most engaged recipients first produces exactly the pattern providers reward — high open and reply rates, almost no complaints — and that record is what allows later volume to be accepted. Starting with the oldest portion of the list does the reverse, and the damage takes far longer to repair than the ramp would have taken.
The confirmed segment is worth building deliberately for this reason among others; a double opt in step is what makes that group meaningful rather than nominal.
Ramping the volume
- Start small and increase gradually. A rough shape is to begin with a few tens or hundreds of messages a day and increase by a modest proportion daily, rather than doubling. The exact numbers matter less than the principle: no sudden step changes.
- Send consistently. A steady daily rhythm builds history faster than the same volume sent in occasional bursts, and bursts look like exactly what you are trying not to look like.
- Ramp per mailbox provider. Reputation is per provider, so a list weighted heavily toward one of them will warm unevenly. Watch the results by domain rather than in aggregate.
- Slow down on bad signals. Rising bounces or complaints mean stop increasing and, if necessary, step back. Pushing through is what turns a temporary problem into a lasting one.
- Do not use the ramp for a broadcast. A bulk send during warm-up defeats the exercise; where you must use bulk workflow triggers, schedule it well after the ramp has finished.
What to send while warming
Content that gets a response. The point of the exercise is to demonstrate that people want your mail, so the messages during a warm-up should be the ones most likely to be opened and replied to: a genuinely useful welcome sequence, an answer to a question, a plain message from a person.
Plain and short performs better here than a heavily designed template, both because it is more likely to be read and because minimal markup is less likely to be filtered. The construction is the same as a nurture sequence that ends in a reply, and the platform behaviours that interrupt a sequence part-way are in sequence limits and the pause trap.
Avoid promotional broadcasts during the ramp entirely. They generate the complaints you cannot afford yet, and there is nothing to gain from running them a fortnight earlier.
Clean the list, and keep it clean
Verify addresses before sending to any segment you have not mailed recently. Removing invalid addresses in advance is the difference between a clean ramp and a bounce spike, and bounces are the single fastest way to lose ground during warm-up.
Suppress permanently anything that hard bounces, and act on complaints immediately. Build the check into your routing rather than into individual campaigns — the layer in routing and suppression — so nothing can accidentally mail a suppressed address later.
The old, unengaged portion of the list is the part to leave alone until the ramp is complete. Where you want to attempt it at all, that is a separate, carefully batched exercise with its own rules, which is what a reactivation campaign describes.
Measuring, and what “done” looks like
Track bounces, complaints, and the proportion of mail reaching an inbox rather than a spam folder, per provider and per day. Aggregate figures hide the one provider where things are going wrong, and that provider is often the one your list is most concentrated in.
Keep the record outside the platform — a durable record outside the platform — so you can compare this ramp with the next one and with the state before a domain change. Warm-up is finished when your normal sending volume produces the same engagement and complaint rates as the small volumes did, which is a measurement rather than a number of days.
Two last notes for agencies. Reputation attaches to the sending domain and to the shared infrastructure behind it, so a client sending badly can affect neighbours — and where you resell under your own brand, that consequence is yours to manage, as a white-label arrangement describes. And a domain does not stay warm on its own: a long gap in sending decays the history, and resuming at full volume after months of silence needs a ramp much like the first one.
Frequently Asked Questions
Why does a new sending domain need warming up?
Because mailbox providers decide delivery largely on how recipients have reacted to your mail before, and a new domain has no such history. A first send of tens of thousands of messages from an unknown name matches the pattern the filters exist to catch.
Who should receive the first messages?
The people most likely to engage: recently confirmed subscribers and recent customers, then contacts engaged within the last quarter. Sending to the oldest, least engaged portion first produces bounces and complaints that take far longer to repair than the ramp would have taken.
How quickly can volume be increased?
Gradually and consistently — increasing by a modest proportion daily rather than doubling, and sending every day rather than in bursts. The exact numbers matter less than the absence of sudden step changes, and rising bounces or complaints mean stop increasing.
What should be sent during a warm-up?
Messages most likely to be opened and replied to — a genuinely useful welcome sequence, an answer to a question, a plain note from a person. Plain and short outperforms a heavily designed template. Avoid promotional broadcasts entirely until the ramp is finished.
Does authentication matter during warm-up?
It is the precondition. No amount of careful volume ramping compensates for unauthenticated mail, so publish and verify the authentication records for the sending domain before the first message, and confirm the sending subdomain is configured rather than assumed.
When is a domain finished warming up?
When normal sending volume produces the same engagement and complaint rates as the small volumes did — a measurement rather than a number of days. Track it per mailbox provider, since aggregate figures hide the one provider where things are going wrong.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.