# Instantly email warmup

> Understand what Instantly email warmup measures, what its health signal can show, and why it is not proof of real campaign placement.

Instantly email warmup is an account-level feature that exchanges automated warmup messages within Instantly's pool and reports activity through a health signal. It can show how those warmup exchanges performed, but it does not prove the authentication or inbox placement of a real campaign. [Google's sender guidelines](https://support.google.com/a/answer/81126) treat sender authentication as a separate requirement. Use warmup as context, then inspect a message from the production sending path before changing a campaign.

## Quick takeaways

- Instantly describes Warmup as automated exchanges among enabled accounts in its pool.
- Its health score concerns recent warmup activity, not every message you send.
- Instantly's readiness guidance is useful operational advice, not a mailbox-provider guarantee.
- Production-message evidence remains separate from the Warmup signal.
- Investigate a real message when the problem is spam placement, rejection, or poor campaign response.

## What Instantly Warmup is

According to [Instantly's Warmup documentation](https://help.instantly.ai/en/articles/5975329-how-warm-up-works-and-why-it-s-important), an enabled account sends warmup emails to other accounts in its pool and receives them in return. Instantly says the exchanges are automatically opened and that many receive replies. That describes the feature's own pool activity. It does not describe how a specific mailbox provider will classify a production campaign sent to your recipients.

This distinction matters because [email deliverability](/learning/what-is-email-deliverability) covers more than whether a message was accepted by a server. A Warmup result describes the feature's exchanges, while a production message supplies evidence about the sending path a reader actually needs to assess.

## What the health signal can and cannot tell you

Instantly describes the score as the share of warmup emails that reached the inbox instead of spam during the previous seven days. That makes it an account-level signal about the Warmup exchanges it observed, not a measurement of a real prospect campaign.

![Two-column evidence boundary separating Instantly Warmup activity from real campaign authentication and placement evidence.](/images/editorial/instantly-email-warmup/instantly-email-warmup-evidence-boundary.svg "1440x820")

*Source: Original Palisade deterministic diagram based on [Instantly's Warmup documentation](https://help.instantly.ai/en/articles/5975329-how-warm-up-works-and-why-it-s-important) and [Google's Email sender guidelines](https://support.google.com/a/answer/81126). It explains an evidence boundary and does not represent a vendor interface or mailbox-provider scoring formula. [Open the full-size diagram](/images/editorial/instantly-email-warmup/instantly-email-warmup-evidence-boundary.svg).*

The diagram is intentionally an evidence boundary, not a model of an inbox provider. Google separately requires senders to authenticate mail and gives senders their own spam-rate guidance in its [Email sender guidelines](https://support.google.com/a/answer/81126). The conclusion that a Warmup score cannot prove campaign placement is an inference from those separate scopes, not a claim that Google evaluates Instantly Warmup in a particular way.

```text
WARMUP REVIEW RECORD

Signal: Warmup health score
Scope: Instantly pool activity during the stated recent window
Not established: SPF, DKIM, DMARC, list quality, recipient consent, or campaign inbox placement
Next evidence: a delivered production-path message and its authentication results
Decision: investigate the real message before changing campaign volume or copy
```

## How to use the signal without treating it as proof

[Instantly's campaign-readiness guidance](https://help.instantly.ai/en/articles/13938078-when-your-email-account-is-ready-for-campaigns) recommends at least two weeks of warmup and a health score above 90%, with an exception for its pre-warmed accounts. Use that as the vendor's current operating guidance for its feature. Do not turn it into a promise that a campaign will reach the inbox or get replies.

When a real campaign is filtering, rejected, or underperforming, collect a delivered message from the same sender and route. Check its authentication results and the recipient-provider evidence available for that message. For an evidence-led repair path, see [why outbound email goes to spam](/learning/why-do-your-emails-go-to-spam-and-how-can-you-fix-it). If the question is whether warmup is even the service category you need, the [email deliverability service guide](/learning/best-email-deliverability-service) separates authentication monitoring, placement monitoring, list validation, and consulting.

## Where warmup fits beside authentication

Warmup activity does not publish, sign, or align your domain's mail. Those are separate technical controls. As [RFC 7489's DMARC overview](https://www.rfc-editor.org/rfc/rfc7489.html) describes, receivers compare the visible From domain with available SPF and DKIM results and the published DMARC policy. A healthy warmup signal cannot show what happened for a particular production message.

That is why the most useful next evidence is a message from the production path. If the real message fails authentication or lands in spam, work from the headers and the receiver response instead of changing settings based only on an account-level warmup metric. A warmup feature can be active while another sender, campaign, or configuration still needs separate investigation.

## Sources and further reading

- [Instantly: How Warm-Up Works and Why it's Important](https://help.instantly.ai/en/articles/5975329-how-warm-up-works-and-why-it-s-important)
- [Instantly: When Your Email Account Is Ready for Campaigns](https://help.instantly.ai/en/articles/13938078-when-your-email-account-is-ready-for-campaigns)
- [Google: Email sender guidelines](https://support.google.com/a/answer/81126)
- [RFC 7489: Domain-based Message Authentication, Reporting, and Conformance](https://www.rfc-editor.org/rfc/rfc7489.html)

## Frequently asked questions

### What is Instantly email warmup?

Instantly email warmup is a feature that exchanges automated warmup messages among enabled accounts in Instantly's pool. It is intended to create account activity before or alongside outreach, but the feature's activity is not the same thing as a production campaign result.

### Does a high Warmup health score guarantee inbox placement?

No. The score describes recent warmup-pool activity. A real campaign can still have separate authentication, reputation, content, list-quality, engagement, or receiver-specific filtering issues that the health signal does not establish.

### Should I rely on warmup instead of SPF, DKIM, and DMARC?

No. Warmup does not publish or validate authentication records and it cannot establish DMARC alignment for a real message. Keep authentication evidence separate and inspect the production message when you need to verify its results.

### How long does Instantly recommend warming up an account?

Instantly currently recommends at least two weeks of warmup for standard accounts and advises checking the health score, while noting an exception for its pre-warmed accounts. Treat that as Instantly's product guidance rather than a delivery guarantee.

### What should I check if a real campaign goes to spam?

Start with a delivered message from the same sender and route, then review its authentication results and any receiver evidence for that message. A Warmup score can add context, but it cannot identify the cause of a recipient's spam-folder decision.