Prepare the account before warmup begins

Warmup should start only after the mailbox and domain are correctly configured. Confirm the account can send and receive normally, authentication passes, the sender identity is consistent, and the account is not already carrying an unresolved reputation problem. Warming a broken configuration simply creates more activity on top of the problem.

Document the start date, warmup settings, provider, domain, and intended campaign date. If several accounts are being prepared at once, label them by cohort so you can tell whether a problem is isolated to one mailbox, one domain, or one setup batch.

Use gradual ramping instead of treating warmup as a switch

Warmup systems generally simulate mailbox activity and gradually build a sending pattern. The practical goal is consistency, not a magic score. Increase activity slowly, allow time for signals to accumulate, and avoid abrupt jumps from warmup traffic to heavy campaign traffic.

Instantly's current documentation recommends preparing new accounts for at least two weeks before campaigns and distinguishes its warmup health score from campaign placement. That distinction matters: a healthy warmup network result can coexist with poor real-world campaign performance if the list, message, or sending behavior is weak.

Monitor account health while preparing

Watch for changes rather than one isolated number. Useful signals include warmup inbox/spam placement, provider errors, authentication status, account connection failures, unusual bounce behavior once real campaigns start, and any mailbox-specific alerts.

If one account's warmup health falls while others on the same domain remain stable, inspect the account. If an entire domain cohort deteriorates, inspect shared DNS, provider, and sending patterns. Diagnosis is easier when accounts are not all configured identically on the same day without labels.

Know what warmup can and cannot solve

Warmup may help withWarmup does not fix
Introducing new mailbox activity graduallyInvalid or poorly targeted lists
Establishing a consistent sending patternBroken SPF/DKIM/DMARC
Providing an account-health signal inside the platformIrrelevant offers or spam complaints
Reducing the shock of a zero-to-volume launchSudden aggressive campaign volume

Warmup is one layer of preparation. It should not be used to justify sending to people who do not fit the campaign or to ignore provider feedback.

Transition from warmup to real campaigns conservatively

Before launch, re-check authentication, account status, sender names, daily caps, and a small sample of actual leads. Start campaign sending below the account's theoretical maximum and let volume rise gradually. Keep warmup and campaign volume conceptually separate so the team knows which activity is generating which signal.

If early campaign bounces, spam placement, or account warnings appear, reduce real sending while diagnosing. Do not assume a high warmup score overrules live campaign evidence.

When to reduce or pause sending

Reduce pressure when several indicators move in the wrong direction at once: elevated bounces, worsening placement, provider errors, authentication failures, or an unusual spike in negative recipient feedback. A pause is especially reasonable after a major infrastructure change because it gives you a clean point from which to validate the new configuration.

Warmup readiness checklist

  • Authentication validated on live mail
  • Preparation period completed according to the provider/platform guidance
  • Warmup health trend is stable, not just a one-day spike
  • Campaign caps start conservatively
  • Lead sample passed QA
  • Monitoring owner knows when to reduce or pause sending

Sources & verification

Product details can change. We used first-party sources for unstable claims on this page.