Instantly.ai Guide 2026: Setup, Warmup, Health Score & Limits Done Right
Instantly.ai is the standard sending layer for cold email in 2026. This guide covers the setup checklist with SPF/DKIM/DMARC, configuring warmup correctly, understanding the Health Score, email verification, and sensible sending limits — plus common mistakes.
What Instantly is — and what it stands for in the stack
Instantly.ai is, in 2026, one of the most widely used cold email sequencers on the market: inbox management, automatic warmup, campaign sending, and deliverability monitoring in one tool, starting at roughly €30-37 per month on the entry plan. Its strength lies in scaling across many inboxes — unlimited sender accounts per plan are the main reason teams switch away from more expensive per-seat tools.
Important for context: Instantly is the sending layer, not the outbound system. It answers the question “How do my emails reliably reach the inbox?” — not “Who do I write to, with what, and what happens with the replies?” In a clean stack, research and personalization come from an upstream research layer like research-agent.net (company enrichment, buying signals, ICP scoring), while orchestration and reply handling come from a system like GTM Goat. Instantly executes what these layers prepare.
Setup checklist: domains, DNS, inbox count
The most common mistake happens before the first email: the setup. Get sloppy here and you’ll fight spam folders for months.
1. Separate sending domains. Never send from your main domain. Cold outreach runs through secondary domains (e.g. company-inc.com instead of company.com, or .net/.co variants) that redirect to the main site. This keeps the main domain’s reputation protected.
2. DNS records — all three, correctly set up:
| Record | Function | Mandatory status 2026 |
|---|---|---|
| SPF | Authorizes sending servers (v=spf1 include:_spf.google.com ~all) | Required by Google/Microsoft |
| DKIM | Cryptographic signature on every email | Required by Google/Microsoft |
| DMARC | Policy for what happens on SPF/DKIM failures (v=DMARC1; p=none; as a starting point) | Required for bulk senders since Feb 2024 |
Since Google’s and Yahoo’s bulk sender rules (February 2024), these records are no longer best practice — they’re a prerequisite. Without DMARC, emails to Gmail addresses increasingly don’t even land in spam anymore — they get rejected outright. Instantly checks the records when you connect the inbox; double-check externally anyway (e.g. via MXToolbox).
3. Plan inbox count. Maximum 2-3 inboxes per domain. Anyone wanting to send 600 emails per day, at a conservative 20 emails per inbox, needs: 30 inboxes across 10-15 domains. Google Workspace inboxes cost roughly €6-7 per month, plus domains at €10-15 per year — infrastructure for a serious setup runs €200-400 per month before the first email goes out.
4. Complete inbox profiles. Profile picture, signature, filled-in sender names. Empty accounts are a spam signal.
Configuring warmup correctly
Instantly’s warmup lets inboxes communicate with each other automatically: emails are sent, opened, replied to, pulled out of the spam folder, and marked as important. This builds reputation before real campaigns run.
Proven configuration for new inboxes:
- Enable ramp-up: start at 3-5 warmup emails per day, increase daily by 1-2, target 25-40 emails per day.
- Reply rate in warmup: set to 30-50% — realistic conversation patterns instead of 100% reply rates.
- Duration before campaign start: at least 14 days, recommended 21-28 days. New domains need the full program.
- Never turn warmup off: warmup stays active even during running campaigns, at reduced volume. The ratio of warmup to campaign emails should be roughly 1:1 initially; once established, a 20-30% warmup share is enough.
A note on being honest with yourself: warmup networks are a grey area that Google can — and increasingly does — detect. Warmup doesn’t replace clean sending practice — it complements it. No amount of warmup will rescue high bounce and spam rates caused by bad lists.
Understanding and improving the Health Score
The Health Score in Instantly shows, per inbox, what share of warmup emails land cleanly in the inbox (instead of spam or category tabs). How to read it:
| Health Score | Meaning | Action |
|---|---|---|
| 98-100% | Healthy | Keep sending normally |
| 90-97% | Early warning | Hold volume, check DNS and blacklists |
| 80-89% | Problem | Halve campaign volume, increase warmup share |
| < 80% | Critical | Pull inbox from all campaigns, warmup only for 1-2 weeks |
Typical causes of falling scores and their fixes:
- DNS errors — re-validate SPF/DKIM/DMARC, especially after domain or provider changes.
- Blacklist entry — check via MXToolbox; for a Spamhaus listing, request delisting and fix the cause (usually bounces or spam complaints).
- Scaling up too fast — pull limits back, restart ramp-up.
- Poor list quality — a bounce rate above 2% drags down every inbox on a domain. Review the verification process.
- Spam-prone content — disable tracking pixels, reduce links, remove spam-trigger phrasing.
The Health Score is an early indicator, not a perfect picture of actual deliverability. It’s worth complementing with a monthly placement test using real seed addresses at Gmail and Outlook.
Email verification: mandatory, not optional
Every list gets verified before import — no exceptions. Hard bounces are the fastest way to destroy a domain’s reputation.
- Instantly’s own verification: right at lead import, cost roughly 0.25-1 cent per address depending on volume.
- External providers: MillionVerifier (from ~$37 for 10,000 checks), NeverBounce, ZeroBounce — worthwhile at large volumes.
- Thresholds: only use addresses with “valid” status in campaigns. Test “catch-all” at most in separate, low-volume campaigns. Consistently exclude “invalid” and “risky”.
- Target bounce rate: below 2%, well-managed setups run below 1%.
Anyone enriching leads via research-agent.net gets validation as part of the enrichment step — the verification step moves out of the manual workflow and into the pipeline.
Sending limits: conservative wins
The most important lever in Instantly is the daily limit per inbox. Recommendation for 2026:
| Parameter | Conservative (recommended) | Aggressive (risky) |
|---|---|---|
| Campaign emails/inbox/day | 15-30 | 50+ |
| Warmup emails/inbox/day | 20-30 | disabled |
| Wait time between emails | 5-15 minutes | < 1 minute |
| New leads/day (ramp-up) | +5-10 per week | maximum immediately |
| Inboxes per domain | 2-3 | 5+ |
Scaling runs horizontally: more domains, more inboxes, rotation across the inbox pool — not higher volume per inbox. Instantly automatically distributes campaigns across all assigned senders; that’s exactly what the tool is built for. A campaign with 50 inboxes at 20 emails each sends 1,000 emails per day without any single inbox standing out.
Common mistakes
- Starting a campaign without a warmup phase — the first week decides the domain’s reputation.
- Using the main domain as a sending domain — a spam listing then also hits normal business communication.
- Leaving open-tracking enabled — tracking pixels measurably worsen deliverability and, in 2026, are unreliable as an open metric anyway. Switch to reply rate as the core KPI.
- Importing unverified lists — see above, bounce rates above 2% are self-inflicted.
- Cranking up limits once things are working — reputation damage shows up with a 1-2 week delay. Double the limit on Monday, and you won’t see the damage until the week after next.
- Misunderstanding Instantly as a complete system — sending is solved, but without clean lead research, personalization, and reply handling, it remains mass sending with better deliverability. Reply quality is created before the send.
Conclusion: sending layer strong, the surrounding stack decides
In 2026, Instantly solves the sending part of cold email as well as almost any tool in its price bracket: warmup, health monitoring, inbox rotation, and verification in one interface. Respect the setup checklist (secondary domains, SPF/DKIM/DMARC, 2-3 inboxes per domain), conservative limits (15-30 emails per inbox per day), and a real warmup phase, and the deliverability problem is under control.
What actually decides meetings booked happens before and after: who you contact (research and qualification, e.g. via research-agent.net), what message you send (personalization based on real signals), and what happens to replies (reply handling, follow-up, CRM sync). At CegTec, the GTM Goat system handles this orchestration — Instantly remains the reliable sending channel within it.
Next step
Want to not just set up Instantly, but run it as part of a system that flows from lead research all the way to a booked meeting? In a free consultation we’ll show you what the complete stack — research layer, orchestration via GTM Goat, and Instantly as the sending layer — looks like for your use case. After that, you can test the system for 4 weeks, free.
Common questions
How long should Instantly warmup run before I start campaigns?
At least 2-3 weeks for new domains and inboxes, ideally 4 weeks. Warmup builds sender reputation with Google and Microsoft through simulated conversations. Starting too early risks having your first real campaign emails land in spam — and that reputation damage is hard to repair. Warmup should also stay active after a campaign starts, at reduced volume (e.g. 20-30 warmup emails per day per inbox).
What does the Instantly Health Score mean, and what's a good value?
The Health Score measures, per inbox, how many warmup emails land in the inbox instead of the spam folder. 100% means every warmup email arrives cleanly. Values above 95% are considered healthy; below 90%, you should reduce sending volume and check the cause (DNS records, blacklists, limits set too aggressively). Below 80%, the inbox should be pulled from all campaigns until the score recovers.
How many emails per day can I send per inbox with Instantly?
Technically Instantly allows far more, but a conservative 15-30 campaign emails per inbox per day is the safe range for 2026. Google and Microsoft have become significantly stricter since the 2024 bulk sender rules. Scale volume through more inboxes and domains, not higher limits per inbox. Rule of thumb: 1,000 emails per day need roughly 35-65 inboxes across 12-22 domains.
Do I need email verification if my leads come from a database?
Yes, always. Even data from Apollo, ZoomInfo, or LinkedIn scrapes typically contains 5-15% invalid addresses. Every hard bounce damages sender reputation. Instantly has built-in verification (roughly 0.25-1 cent per address depending on volume); alternatives are MillionVerifier or NeverBounce. Target: bounce rate below 2%, ideally below 1%. Handle addresses with 'catch-all' or 'risky' status separately, or exclude them.
Is Instantly enough on its own for complete outbound?
No. Instantly is the sending and warmup layer — it solves deliverability and sequence sending. What it doesn't solve: lead research, account qualification, individual personalization, and intelligent reply handling. That requires upstream research (e.g. research-agent.net for enrichment and signals) and an orchestration layer that qualifies leads, personalizes messages, and processes replies — at CegTec, the GTM Goat system takes on that role.