How to Keep Your Instantly Bounce Rate Under Control in 2026

Keep an Instantly bounce rate low by verifying leads before upload, separating catch-all and risky leads into their own campaigns, ramping new inboxes slowly, and never resuming an auto-paused campaign until the list is fixed. Instantly pauses at 5% by default, but only after 200 sends, and then not again for 7 days after you resume.

Those three numbers decide how much damage a bad list can do before anything stops it. They come from Instantly's help centre, read on 1 October 2026.

How Instantly's bounce protection works

Instantly has two safety nets: an auto-pause on bounce rate, and BounceShield, which skips known high-risk recipients. Both are on by default.

From Instantly's High Bounce Auto-Pause Feature and Campaign Error articles:

Setting	Behaviour
Default threshold	Pauses "when the bounce rate exceeds 5%"
Minimum volume	"Campaigns must send at least 200 emails before this check runs"
Basis	Bounce rate of "recent emails"
Customisable	Threshold can be changed in Preferences; feature can be disabled
After you resume	"It won't be automatically paused again in the next 7 days, even if the bounce rate remains high"
Status shown	A "Bounces" error on the paused campaign

And from BounceShield - Skipped leads: the system "analyzes bounce data in real-time to automatically skip any known high-risk recipients", based on Instantly's logs. Skipped leads show a "Skipped" status. Leads are also skipped if they are on your blocklist or hit a per-company send limit.

The two gaps in the safety net

The 200-email minimum and the 7-day grace period are where a bad list does its damage. Neither is a flaw; they stop the feature pausing on noise. But you need to plan around them.

Gap 1: the first 200 sends are unprotected

At a 5% threshold, the check needs 10 bounces in 200 sends to fire. A list that is 3% invalid produces about 6 bounces in that window and never trips it. That is below Instantly's line, and still well above what you want on a fresh domain. Instantly's pause is built to stop disasters, not to keep you healthy.

Gap 2: resuming switches the protection off for a week

This is the one that catches people. If you resume a paused campaign without changing the list, Instantly will not pause it again for 7 days. We worked through what that means at ordinary cold email volumes, assuming invalid addresses are spread evenly through the remaining leads:

Inboxes on campaign	Sends in 7 days at 30/day each	Bounces if 3% invalid	Bounces if 8% invalid
5	1,050	about 32	about 84
10	2,100	about 63	about 168

Thirty a day per inbox is Instantly's own suggested ceiling: its bounce troubleshooting article gives "30 cold emails + 10 warmup emails per account per day" as safe limits. The arithmetic is simple, and the method is in our research notes, but the conclusion is the useful bit: the moment after a bounce pause is the worst time to click resume without cleaning.

Step 1: Verify before upload, not after the pause

Verify every lead list before it reaches a campaign, and remove invalid addresses rather than letting the platform skip them. Instantly's own first step after a bounce pause is "Run email verification on all leads before resuming the campaign."

You can do this inside Instantly or outside it:

• Inside Instantly. Its How to Verify Leads guide prices verification at "0.25 Instantly Credits per lead" (1,000 leads use 250 credits), with 100 free credits on a trial. You can tick Verify leads on upload. Results show as Valid, Invalid or Risky.
• Outside Instantly. Verify the CSV first and upload only what you intend to send. This also gives you a file you can reuse in other tools.

Whichever you use, deduplicate on a lower-cased copy of the email column first, so you are not paying to verify the same person twice.

Step 2: Decide what "risky" means for this campaign

Instantly does not contact Invalid or Risky leads unless you allow it, and you should only allow it deliberately. The setting is Campaign > Options > Allow risky emails > Enable risky emails.

Risky usually means one of two things:

• Catch-all domains, which accept every address and so cannot be confirmed by an SMTP check. Our catch-all explainer covers why.
• Servers that would not give a clear answer at the time of the check.

Instantly offers a catch-all verification step and, in its own article, claims it can "reclaim 300-400 additional contacts from every 1000 leads". That is Instantly's figure, not an audited one, and it is worth testing on your own data before relying on it.

A safer pattern than enabling risky emails on your main campaign:

1. Put risky and catch-all leads in a separate campaign.
2. Use your most established inboxes for it, not new ones.
3. Send a small first batch and read the bounce report before scaling.

Our decision framework for catch-all addresses gives batch sizes and stop rules.

Step 3: Ramp new inboxes slowly

A new inbox sending at full volume on day one invites throttling and rejections, whatever the list quality. Instantly's bounce article sets a "minimum warmup requirement: at least 2 weeks before using accounts in campaigns".

Its Campaign Slow Ramp starts at 2 campaign emails on day 1 and adds 2 per day until it reaches your limit, so an inbox capped at 30 reaches full volume after day 15. It is off by default and set per account, so check it on every new inbox.

The same article lists causes of soft bounces that have nothing to do with the list: "Sending Too Much, Too Fast", "Copy repetition" and "Links in Step 1". Send the first email in plain text without links if you are seeing deferrals.

Step 4: Read the bounce reasons, not just the rate

A bounce rate tells you something is wrong; the bounce reasons tell you what. In the campaign, open Analytics, scroll to the Bounces tab and review the types (Hard, Soft, Unknown) and reasons, using View on individual leads.

Read the full SMTP response, then group:

Pattern in bounce text	Likely cause	Fix
"user unknown", "mailbox not found", 550 5.1.1	Dead address	List quality; re-verify
Many rejections from one company or one security gateway	Recipient's filter	Their policy, not your list
Authentication or policy wording, 550 5.7.1	Your SPF, DKIM or DMARC	Check your domain
Temporary codes such as 421 4.7.0	Throttling	Slow down

Instantly's article notes that recipients behind security gateways "such as Proofpoint, Mimecast, or Microsoft Defender for Office 365" can bounce even when the address is valid. If most of your bounces come from one gateway, re-verifying the list will not help. If they are authentication related, check your sending domain with the deliverability audit.

Step 5: Stop bounced leads reappearing

Instantly stops follow-ups to a bounced lead in that campaign, but you have to block it from future ones. Its Managing Bounced Leads article gives the steps: filter the campaign's leads by Bounced, download them, then upload that CSV under Settings > Blocklist. Those addresses are then excluded from all future campaigns.

Do this after every campaign. The same lead lists tend to be re-uploaded months later, and without a blocklist entry the dead address goes out again.

A pre-launch checklist

1. Leads deduplicated and verified within the last few weeks.
2. Invalid removed from the file, not merely skipped.
3. Risky and catch-all leads in a separate campaign, if at all.
4. Inboxes warmed for at least two weeks, with slow ramp on for new ones.
5. Daily limits at or below 30 cold emails per inbox.
6. SPF, DKIM and DMARC passing on every sending domain.
7. Previous bounces uploaded to the workspace blocklist.
8. Auto-pause left on, at a threshold you have chosen rather than the default.

The takeaway

Instantly's auto-pause is a backstop that fires at 5% after 200 sends and then stays quiet for a week once you resume. Treat it as the last line, not the plan. Verify and deduplicate before upload, keep risky leads apart, ramp inboxes slowly, read the bounce text, and blocklist what bounces. If a campaign does get paused, clean the remaining leads before you resume, because for the next 7 days nothing else will stop them.