Deliverability for Instantly
Know exactly which deliverability layers Instantly handles natively, where it stops, and which external tools cover the gaps before your bounce rate costs you sender reputation.
TL;DR
The short version
Instantly covers warmup, bounce detection, and reputation protection natively on every plan. What it does not cover: domain authentication setup, list verification before upload, and inbox placement testing. Teams that skip those three external steps burn sender reputation that warmup alone cannot rebuild.
How to set up SPF, DKIM, and DMARC before connecting any inbox to Instantly. How to verify your list before uploading to avoid bounce-triggered reputation damage. How Instantly's native warmup and reputation protection actually work, and where their limits are. How to run inbox placement tests so you know whether your emails are hitting the inbox or spam folder. Which external tools slot into each layer without duplicating what Instantly already does.
Deliverability Layers
What Instantly handles vs what you still need
| Layer | What Instantly provides | What needs external tools | Priority |
|---|---|---|---|
| Domain & Authentication | Connects any inbox via SMTP/OAuth; does not configure DNS records | SPF, DKIM, DMARC setup on each domain; dedicated sending domains per campaign | Critical — do before anything else |
| List Hygiene | Bounce detection + global block list after sending | Email verification before upload to prevent bounces in the first place | Critical — verify before every upload |
| Inbox Warmup | Unlimited native warmup on all plans | Optional: external warmup tool for higher daily volumes or supplemental coverage | High — activate before first send |
| Sending Behavior | Reputation protection, A/Z testing, scheduling, send limits per inbox | Sending volume SOP; per-inbox daily cap discipline | High — configure before scaling |
| Placement Testing | No built-in inbox placement testing | External inbox placement tool (GlockApps, MailReach, Folderly) to test before campaigns | Medium — run before new domains go live |
Layer 1
Authentication first: SPF, DKIM, and DMARC before connecting any inbox
Instantly does not configure DNS records for you. Before connecting any inbox, every sending domain needs a valid SPF record authorizing the ESP you send through, a DKIM signature matching the domain, and a DMARC policy set to at least p=none with a monitoring email address.
Teams running Instantly at scale typically use dedicated secondary domains rather than their root company domain. The pattern is one or two sending domains per campaign cluster, each with full authentication. This separates reputation risk: a single domain landing in spam does not affect campaigns running on other domains.
Freshly registered domains have no sender history, which makes spam filters suspicious regardless of authentication. Register sending domains at least 14 days before adding them to Instantly. During that window, set DNS records and run warmup. Start actual outbound sends only after warmup has been active for a minimum of two weeks on each domain. Skipping this step is the most common cause of immediate spam placement on new Instantly accounts.
Layer 2
List hygiene: verify before uploading to Instantly, not after bouncing
Instantly's bounce detection catches bad emails after they have already been sent and bounced. A high bounce rate on the first campaign from a new inbox damages sender reputation before the warmup has time to offset it. The correct sequence is: verify the list externally, then upload only clean contacts.
For cold email lists, a bounce rate above 2% signals to Gmail and Outlook that you are sending to unverified contacts. Instantly's global block list prevents re-sending to known bad addresses, but it cannot retroactively repair reputation damage from a 10% bounce rate on a first campaign. Verification before upload eliminates the problem at the source.
Catch-all domains accept any email at the SMTP level, so standard verification returns them as "unverifiable" rather than invalid. Cold email lists typically contain 20 to 40% catch-all addresses. Use a verification tool that provides catch-all risk scoring (Bouncer's toxicity check or ZeroBounce's activity data enrichment) and filter high-risk catch-alls out of the initial send. Limit catch-all sends to a separate inbox cluster with a lower daily send cap to protect your primary domains.
Layer 3
Warmup and sending behavior inside Instantly
Instantly includes unlimited warmup on every plan, activated per inbox. The warmup runs automatically once enabled: Instantly exchanges emails with its warmup network to build sender reputation signals before outbound sends start. Warmup and outbound sending can run simultaneously, which is by design. The warmup activity partially offsets the reputation impact of cold outreach.
Reputation protection is a separate native feature. Instantly monitors bounce rates and stops a campaign if the rate exceeds a defined threshold. Combined with the global block list, this prevents known bad addresses from re-entering sequences. These two features cover the reactive side of deliverability. They react to problems after the first send; they do not prevent a high-bounce first send from happening.
Even with warmup active, limit new inboxes to 20 to 30 emails per day for the first month of outbound sending. Increase by 10 to 15 emails per day each week if bounce rates stay below 2% and spam reports stay near zero. Instantly allows you to set per-inbox daily limits directly in the mailbox settings. Set this limit explicitly rather than relying on the platform default, which may be higher than new inboxes can handle without reputation impact.
Layer 4
Inbox placement testing: verify where emails actually land before scaling
Instantly does not include an inbox placement test. You can send campaigns, monitor reply rates, and watch Unibox for replies, but none of these confirm whether emails are hitting the inbox or the spam folder for recipients who never open them. A campaign with a 1% reply rate might have a 60% inbox placement rate or a 20% inbox placement rate. Without an external placement test, you cannot tell the difference.
Run a placement test before launching any new domain into full-volume outbound. The test sends to a seed list across major email providers and reports inbox vs spam vs promotions placement per provider. A result below 85% inbox placement on Gmail or Outlook warrants a pause to diagnose the cause before scaling.
Spam filters evaluate the full email: subject line, body content, link count, image-to-text ratio, and HTML structure, not just the sending domain. Run placement tests using the actual email template you plan to send, not a blank or generic test message. A domain that passes a blank-message placement test may still hit spam if the campaign email contains multiple links, aggressive subject lines, or heavy HTML formatting.
Recommended Tools
Tools that fill the deliverability gaps Instantly does not cover
Each tool below addresses a specific layer in the Instantly deliverability stack. Bouncer and ZeroBounce cover list verification. GlockApps and MailReach cover inbox placement testing. MailReach and Warmbox add external warmup for teams running high sending volumes across many inboxes.
Common Questions
Frequently asked questions
For most teams, yes. Instantly's native warmup covers the core function on every plan and runs alongside outbound sends by design. A separate warmup tool adds value mainly when running very high sending volumes across many inboxes simultaneously, or when you need placement monitoring and Slack alerts that native warmup does not provide. Start with Instantly's native warmup and add an external tool only if placement tests show degrading inbox rates.
Keep hard bounce rates below 2% per campaign. Gmail's Postmaster Tools triggers reputation warnings above approximately 0.1% spam complaint rate, which is a separate but related metric. Instantly's reputation protection pauses campaigns that exceed its configured bounce threshold, but setting that threshold correctly, and verifying lists before upload, is the team's responsibility rather than a platform guarantee.
Start new inboxes at 20 to 30 emails per day for the first month of outbound sends, regardless of how long warmup has been running. Increase in weekly increments of 10 to 15 emails per day as long as bounce rates stay below 2%. Established, warmed inboxes with 3 to 6 months of clean send history can handle 50 to 80 emails per day. Higher daily volumes are possible but carry proportionally higher reputation risk if any campaign hits a bad list segment.
Use separate secondary domains rather than your root company domain or subdomains. Secondary domains (e.g., getcompanyname.com, trycompanyname.com) isolate outbound reputation from your main brand domain. Subdomains share the root domain's reputation in most spam filter evaluations, so they do not provide meaningful isolation. Register secondary domains at least two weeks before connecting them to Instantly and run full authentication and warmup before any outbound sends.
Stack covered. Now pick the right verification tool.
Compare the best email verification tools by accuracy, catch-all handling, credit pricing, and fit for high-volume cold email workflows.