Email warmup

# Email warmup

Email warmup is the process of gradually increasing send volume on a new email domain to build sender reputation with major inbox providers. A brand-new domain has zero reputation, which means receiving providers default to skepticism. Sending fifty cold messages from a fresh domain on day one puts most of them in the spam folder and trains the provider to treat the domain as suspicious for the foreseeable future. Warmup avoids that.

The mechanism is simple to describe. A warmup service exchanges low-volume, friendly-looking messages between the user's new mailbox and a network of cooperating mailboxes. The messages get opened, replied to, and marked as important. The receiving providers see consistent positive engagement signal and incrementally raise the trust score on the domain. After enough engagement, the provider's filter classifies the domain as a normal-looking sender and allows real outbound to flow into the inbox.

Why it matters

Without warmup, deliverability on a new domain is permanently capped at a low number. The first hundred cold messages train the provider that this domain sends cold mail with no engagement, and the spam classification follows. Recovery from this state is harder than getting it right initially.

Warmup is also the bottleneck on how fast a new outbound motion can start. A team that decides on Monday to launch outbound on a new domain cannot send meaningful volume until roughly the following month. Operators who plan around this constraint do not get caught by it. Operators who assume the sender will "just work" tend to discover the constraint by burning a domain or two.

The math is what makes warmup unavoidable for serious volume. A typical cold campaign needs to send a few thousand messages per week to produce useful pipeline. Distributing that across mailboxes at safe per-mailbox volumes requires more mailboxes than most teams initially plan for. A single mailbox running at safe volume sends roughly thirty to fifty messages per day. Five thousand messages per week requires twenty to thirty mailboxes minimum, all of them properly warmed.

The good news is that warmup is now mostly automated. The bad news is that the automation is only as good as the warmup network's reputation, and shady warmup services can hurt the domain rather than help it.

Common pitfalls

The first is skipping warmup entirely on a new domain. A founder buys a domain, configures SPF/DKIM/DMARC, and starts sending. Even with perfect authentication, the lack of reputation puts most messages in spam. The fix is starting warmup at least four weeks before the planned launch date.

The second is over-aggressive volume ramping. Most warmup services let the user configure ramp speed. The temptation is to set it high so volume scales quickly. The cost is fragile reputation that breaks at the first sign of bad list quality. Conservative ramps that start at five messages a day and add two or three per day over six weeks produce more durable results.

The third is using a low-quality warmup network. Warmup networks where the cooperating mailboxes are themselves spammy do not help. They actively hurt. The right networks consist of legitimate-looking business mailboxes with positive engagement patterns. The major senders curate this carefully. The standalone warmup-only services vary wildly.

The fourth is letting the domain go cold after the initial warmup. A domain that warms up over six weeks and then sits idle for two weeks during a launch delay will have lost some of its accumulated trust. Continuous low-volume warmup activity in the background keeps the reputation healthy. Most modern senders run this automatically.

How it shows up in agent-driven workflows

In Coil specifically, warmup is outside the product boundary. A configured SmartLead connection supports a separate direct handoff, and an admin-published webhook can deliver approved fields to an allowed destination. Coil does not schedule sends, warm mailboxes, measure inbox placement, or integrate generally with every sender. Those responsibilities remain with the downstream sending system.

Coil does not currently ingest sender warmup status or automatically throttle, pause, or reroute campaigns. Operators review and act on warmup state in the sending system.

Related concepts

Deliverability is the broader problem warmup solves a piece of. Warmup builds reputation. Reputation enables deliverability. Deliverability enables reply rate.

Cold outreach cannot start in earnest until warmup is done. Most timeline slippage in outbound launches traces to underestimating this.

Sequence cadence is constrained by warmup state. A warming domain cannot run the same cadence as a mature one.

Reply rate is the downstream metric that warmup unlocks. A campaign on an unwarmed domain has a ceiling regardless of message or list quality.

For more on Coil's boundary between reviewed data operations, the separate SmartLead handoff or explicit webhook path, and sender-owned warmup, see the Coil methodology pillar.