The Instantly Deliverability Ceiling (and How to Fix It Without Switching)

TLDR. Instantly's deliverability ceiling is almost always an infrastructure ceiling, not a campaign-tool ceiling. The fix is to keep Instantly as the sender and swap the mailbox layer underneath for dedicated infrastructure — isolated Azure tenants, dedicated IPs, automated SPF/DKIM/DMARC, and a hard cap of 2 outbound + 2 warmup per mailbox per day. Per-mailbox pricing on dedicated infrastructure runs $1.00/$0.85/$0.70/$0.55 by volume tier. Two- to four-hour setup, 14-day money-back. Campaigns, sequences, and the unified inbox in Instantly stay exactly as they are.

Instantly built one of the best campaign managers in cold email. The sequence editor, the unified inbox, the reporting, the AI-suggestion features — all real product work. If you've used it past a few campaigns, you know the team ships.

What Instantly doesn't build is the infrastructure underneath your mailboxes. The sending IPs, the dedicated domain reputation, the DNS authentication stack — those are either bundled-but-shared or BYO. Either path hits a ceiling at scale that looks like an Instantly problem but is actually an infrastructure problem.

This article explains exactly what breaks past ~200 mailboxes, how to tell whether you're hitting it, and the infrastructure fix that doesn't require leaving Instantly.

The 30-second answer

The common thread: Instantly as an application is solid. The infrastructure tier underneath it is what's bottlenecking deliverability at cold-email scale.

What Instantly is, what it isn't

Instantly's product is the campaign builder + sequence engine + unified inbox + AI features. The team is good at all of this.

What Instantly uses but doesn't fully control:

• The mailboxes — connected from your Google Workspace, Microsoft 365, or third-party SMTP. Instantly authenticates against them.
• The sending IPs — when using Instantly's bundled SMTP option, the IPs come from a shared pool. Other Instantly customers send through them too.
• The DNS / SPF / DKIM / DMARC setup — Instantly documents what to add but doesn't provision DNS on your domains.
• The warmup network — Instantly's bundled warmup runs across all customers; shared signals.

The shared parts work at small scale. Past a few hundred mailboxes, the seams show.

The Google Workspace + Instantly combo (most common path, hits walls fastest)

The standard Instantly setup pairs it with Google Workspace mailboxes ($6/user/month × N mailboxes). Instantly authenticates as your Workspace users and sends through Gmail's SMTP.

This works fine at small scale. Past ~150 mailboxes, three things break:

1. Cost compounds fast. 500 mailboxes × $6/mo Workspace = $3,000/mo just on user licenses, before Instantly subscription or list cost. The infrastructure isn't even isolated for that price.

2. Domain reputation pools across all senders on your Workspace domain. Multiple campaigns running on one Workspace domain share reputation. One bad campaign → everyone's deliverability drops. There's no isolation per campaign or per mailbox.

3. Workspace suspension risk. Google's TOS explicitly prohibits "spam-like" sending behavior, and Google's classifier treats cold email as spam-like regardless of intent. Past a certain volume, individual accounts (or the whole tenant) get flagged. Suspension recovery takes days; sometimes accounts never come back.

When Instantly customers say "deliverability is dropping at scale," they almost always mean Google Workspace deliverability is dropping at scale. Instantly is the application reporting the symptom, not the cause.

The shared-SMTP wall (different path, same destination)

The alternative — Instantly's bundled SMTP provisioning — has the parallel issue. Multiple customers send through the same SMTP infrastructure. Sending IPs are shared across the pool. One customer's bad campaign drives down the IP's reputation for everyone using it.

You can be doing everything right and watch your inbox placement collapse because of someone else's mistake on the same IP block. This is the neighbor problem — you don't control your neighbors, and you wear their reputation.

Diagnostic test: open Google Postmaster Tools, check IP Reputation. If you see Medium or Low when your own sending is clean, you're sharing an IP with bad actors. (Reading Postmaster Tools for cold email →)

Instantly-specific failure modes (beyond shared infrastructure)

Beyond the two infrastructure walls above, Instantly users hit four configuration-specific failure modes that compound the underlying problem. Each one is silently invisible in Instantly's reports — you only see the symptom (lower reply rate) and not the cause.

1. Warmup toggled on at the workspace level but never flipped on per-mailbox. Instantly's warmup is configured workspace-wide, but each individual mailbox must also have warmup explicitly enabled. Operators see the workspace-level toggle as "on" and assume every connected mailbox is warming. New mailboxes that never had per-mailbox warmup activated cold-start on the first send and get evaluated as cold senders by Gmail and Outlook. The fix is auditing every mailbox in Settings → Email Accounts and confirming the warmup status badge per mailbox, not just at the workspace level.

2. IP rotation cadence set too aggressive on bundled-SMTP sends. Instantly's bundled SMTP option lets you configure how often the sending IP rotates across messages. The default is balanced for low-volume sends; operators sometimes raise the rotation frequency thinking it spreads reputation more evenly. In practice, aggressive IP rotation prevents any single IP from accumulating positive reputation history — every send looks like a "new sender" event to Gmail's classifier. The fix is leaving IP rotation at the default cadence and isolating reputation at the dedicated-IP layer instead. On dedicated infrastructure each mailbox has a single stable IP, eliminating the rotation question entirely.

3. Custom tracking domain (CTD) misconfiguration breaking link reputation. Instantly recommends configuring a custom tracking domain for link clicks and open pixels — instead of using instantly.email/track defaults that show up in spam-trigger checkers as a shared domain. But the CTD setup requires CNAME records and SSL provisioning, and operators who skip steps end up with broken tracking links that 404 or serve HTTP-only content. Spam classifiers flag broken links and HTTP-only assets aggressively. The fix is validating the custom tracking domain end-to-end — CNAME resolves, SSL valid, redirect chain clean — before any campaign uses it. The Email Deliverability Test surfaces broken CTD configs as part of the link-audit step.

4. Sub-account vs main-account routing mixing reputation pools. Agencies running Instantly's sub-account feature for multiple clients sometimes route sends from one sub-account's mailboxes through another sub-account's IPs by accident — usually when mailbox assignments and SMTP routing are configured separately. The result is reputation pooling across clients, which is exactly what dedicated infrastructure is supposed to prevent. The fix is auditing sub-account → mailbox → IP routing for every client and confirming hard isolation. On dedicated infrastructure each sub-account gets its own Azure tenant and its own IPs, making this physically impossible.

5. Bulk-import mailbox CSV with credential drift. When operators add 50+ mailboxes via Instantly's bulk import, a typo in the CSV (wrong IMAP port, wrong host casing, wrong password) causes individual mailboxes to silently fail authentication. The unified inbox shows the campaign sending but never receives any replies because IMAP polling fails for the broken mailboxes. The fix is running Instantly's "Test Connection" on every imported mailbox before launching campaigns.

Diagnostic checklist: run before contacting Instantly support

Before opening a support ticket, run through this ordered checklist. Most Instantly deliverability problems trace back to one of these — and Instantly support will ask about them anyway.

1. Confirm Instantly's warmup is on per-mailbox. Workspace-level toggle is necessary but not sufficient. Every mailbox needs warmup active in its own settings panel.
2. Run the Email Deliverability Test on your sending domain. SPF, DKIM, and DMARC misconfigurations stop deliverability work before any campaign tweak can help. Fix authentication first.
3. Check the sending IP against the Blacklist Checker. Spamhaus, Barracuda, SORBS — any blocklist hit explains the inbox-rate drop without further diagnosis. If listed, follow the blocklist removal playbook.
4. Open Google Postmaster Tools. Look at Domain Reputation and IP Reputation. Anything below High on a sending domain that previously hit High is the infrastructure-side signal.
5. Pull bounce rate per mailbox over the last 30 days. Above 3% on stable list quality means the receiver is rejecting reputation-driven, not address-driven. Cross-reference any 5xx codes you see in Instantly's logs against the SMTP error library — codes like 550 5.7.1 SPF fail at Gmail or 550 5.7.1 DKIM fail at Gmail point to authentication; 550 5.7.1 unusual rate of unsolicited mail points to reputation.
6. Audit per-mailbox daily send caps. Instantly's defaults are higher than the safe cold-email ceiling. The deliverability-safe cap is 2 outbound + 2 warmup per mailbox per day. Anything above 5/day is burning mailbox reputation.
7. Verify the custom tracking domain. CNAME resolves, SSL valid, redirect chain clean. Broken CTDs trigger spam classifiers reliably.
8. Sample 10 messages through Mail-Tester.com. Score below 8/10 means content or authentication issues need work before infrastructure work helps.
9. Check Sub-Account → Mailbox → IP routing if you're on the Agency tier. Reputation pooling across clients undoes any dedicated-infrastructure work.
10. Confirm domains are no younger than 14 days. Brand-new domains have no reputation; campaigns from them inevitably hit spam folders. Either wait or use ColdRelay's pre-warmed domain inventory.

How to know you're hitting Instantly's infrastructure ceiling

Five diagnostic signals. Two or more present = you're hitting it:

1. Inbox rate at 50 mailboxes was 85%+; at 200 mailboxes it's 60% or below. The classic shared-infrastructure scaling curve. Individual mailbox tests look fine because Gmail rates the message; pooled-sender tests degrade because Gmail rates the pool.

2. Reply rate dropped while open rate stayed the same. Counterintuitive but diagnostic. Opens come from prefetch and skim-readers. Replies need primary-inbox placement plus a message that feels legitimate. Same opens + fewer replies = more spam-folder placement.

3. Google Postmaster Tools Domain Reputation drifted from High to Medium. Without a campaign content change, that drift means infrastructure-side reputation is sliding. (What to do when Postmaster says Medium →)

4. SMTP "temporary deferral" errors on a meaningful share of sends. Visible in Instantly's logs. A percent or two is normal; double digits = receivers are throttling you.

5. Bounce rate creeping above 2% despite stable list quality. Reputation-driven rejections look like bounces but are infrastructure problems wearing list-quality clothing. (Reading the SMTP codes →)

Related deliverability fixes

The shared-infrastructure ceiling shows up across every cold-email sender. The fix architecture is the same; the connection-path details differ per platform:

• Smartlead deliverability fix — canonical long-form on campaign-vs-infrastructure decoupling.
• Lemlist deliverability fix — same fix architecture, different connection flow for Lemwarm interplay.
• EmailBison deliverability fix — AI-first sender with the same shared-IP ceiling underneath.
• Saleshandy deliverability fix — cost-conscious sender, infrastructure layer dominates total cost.

The fix: dedicated infrastructure under Instantly

The architecture is a clean split:

The layers compose. Instantly stays the campaign manager. ColdRelay becomes the deliverability backbone. Instantly's UI is unchanged; the mailboxes Instantly sends through are different.

The migration: keep Instantly, swap the infrastructure

Concrete steps:

1. Provision domains + mailboxes through ColdRelay. Setup is fully automated — 60 minutes from purchase to ready-to-send. Domains bought, DNS configured, IPs allocated, mailboxes provisioned on dedicated infrastructure.
2. Push the new mailboxes into Instantly with one click. ColdRelay's dashboard hits Instantly's add-account API directly. Provider type set to Custom SMTP/IMAP, warmup auto-enabled, daily caps configured (2 outbound + 2 warmup per mailbox per day, the volume that keeps Postmaster Tools Domain Reputation pinned at High).
3. Run new campaigns on the new mailboxes. Or migrate existing campaigns over — Instantly handles parallel mailbox sets fine.
4. Pause sending on the old infrastructure for 7 to 14 days. New domain reputation builds independently; ColdRelay's per-customer isolation means new mailboxes don't inherit any reputation from the old shared-pool history.

Cost math vs. Workspace + Instantly:

The deliverability lift comes on top of the cost reduction. Same Instantly subscription, same Instantly campaigns, ~90% lower infrastructure cost, dedicated-IP reputation control.

What about Instantly's bundled warmup?

Instantly's warmup network is useful in the first few weeks of a brand-new domain when any warmup signal helps. At scale, the shared-network signals dilute. ColdRelay's infrastructure-level warmup (running at the SMTP layer with your dedicated IP) accumulates reputation faster because the SMTP and IP signals matter more than the warmup-network exchange volume alone.

You can run both in parallel — Instantly's warmup contributes to message-exchange volume, ColdRelay's infrastructure-level warmup makes sure the IP and domain history accumulate cleanly. No conflict.

What changes for the customer (basically nothing)

The only thing that changes: in Instantly's "Email Accounts" page, you swap the old Workspace-connected mailboxes for the new ColdRelay-provisioned ones. Reassign campaigns to the new mailboxes. Done.

FAQ

Will I lose my Instantly campaigns or contact data?

No. Campaigns, sequences, contacts, reporting history — all stay in Instantly. You're only changing which mailboxes Instantly sends through.

Does Instantly support custom SMTP/IMAP mailboxes?

Yes. Instantly has explicit support for Custom SMTP/IMAP (provider_code: 1 in their API). When you add a mailbox via Instantly's UI, "Custom IMAP/SMTP" is one of the provider options. ColdRelay's dashboard pushes mailboxes into Instantly with this provider type set correctly + warmup auto-enabled.

How long until I see deliverability improvement?

7 to 14 days for the first signal. Postmaster Tools Domain Reputation reaching High is the leading indicator. Reply rate improvement typically lands in week 3 to 4 as the new mailboxes' reputation matures.

What if I'm using Instantly's bundled mailbox provisioning, not Workspace?

Same fix — the underlying shared-IP infrastructure has the same neighbor problem regardless of whether you bring your own Workspace or use Instantly's bundled provisioning. Dedicated per-customer infrastructure is the architectural answer.

Can I run Instantly bundled mailboxes AND ColdRelay-provisioned mailboxes in parallel?

Yes. Many customers split traffic for the first 30 days — existing campaigns continue on old mailboxes, new mailboxes provision on ColdRelay, traffic gradually shifts. No hard cutover required. Side-by-side reply-rate comparisons let you verify the lift before fully migrating.

Is there a contract or commitment?

ColdRelay's billing is monthly. The pricing tier (based on mailbox count) updates automatically as you scale up or down. 95% deliverability guarantee with refund in your first 14 days — if the infrastructure doesn't hit that bar, you're out at no cost.

What about other sending tools — Smartlead, Lemlist, EmailBison, Saleshandy?

Same pattern. ColdRelay has one-click push integration with Smartlead, Lemlist, EmailBison, and Saleshandy. The infrastructure layer underneath is identical regardless of which sender sits on top.

What's the per-mailbox daily cap on dedicated infrastructure, and why isn't it higher?

The cap is 2 outbound + 2 warmup = 4 emails per mailbox per day. The reason isn't infrastructure capacity — it's Gmail's and Outlook's complaint-rate tolerance. Above 5 sends per mailbox per day, the rate of spam complaints (even at low single-digit percentages) crosses the threshold where Gmail's classifier flags the mailbox as a spam source. Below 5, complaint volume per mailbox stays under the threshold even if your list quality occasionally dips. The cap is what protects deliverability; scale comes from adding more mailboxes, not raising the cap.

How is Microsoft 365 different from Google Workspace for Instantly cold sending?

Both have shared-domain reputation pools, but the failure modes differ. Microsoft 365's strict outbound throttling kicks in at lower volumes — Microsoft will silently rate-limit before any individual mailbox is over its hard cap. Google Workspace has higher hard limits but more aggressive TOS enforcement — Google occasionally suspends accounts whose sending patterns match their spam classifier, regardless of whether you stayed under daily limits. The structural fix for both is the same: separate cold-prospecting infrastructure on dedicated mailboxes outside the corporate tenant.

Which metrics should I monitor weekly once I'm on dedicated infrastructure?

Five metrics, weekly cadence. (1) Postmaster Tools Domain Reputation — should hold High. (2) Per-mailbox bounce rate — alert at 3%. (3) IP reputation via the Blacklist Checker on every sending IP. (4) Reply rate by campaign — drops signal content or deliverability issues. (5) IMAP polling status in Instantly — drift breaks reply detection silently. The Email Deliverability Test consolidates the first three into one weekly run.

When is it time to consider switching infrastructure providers (not just within Instantly)?

When you see three or more of: domain reputation Low for 21+ days, multiple sending IPs on a major blocklist, bounce rate consistently above 5%, account-level suspensions, or a sustained reply-rate decline below 1% on previously-working campaigns. Tactical fixes inside Instantly don't recover from these — fresh domains on dedicated infrastructure is the structural move. The 14-day money-back window covers the migration trial.

Instantly is a good campaign manager. Pair it with infrastructure purpose-built for cold email at scale, and the deliverability ceiling moves out by an order of magnitude.

See ColdRelay + Instantly in action → Try ColdRelay free · Test your current deliverability → Free test