How Many Bounces Can One Cold Email Inbox Take? A Bounce Budget in Real Numbers

Your bounce budget is your bounce-rate limit multiplied by the sends it covers. One inbox sending 30 cold emails a day with a 2% target can afford 0.6 bounces a day, which in practice means about one bounce every two days, or three in a 150-send week. At a 5% stop line it is 1.5 a day, or seven or eight a week. Those numbers are small, which is the point: a single batch of unverified or catch-all leads can use up a week's budget in one morning. Judge each inbox over a week, and fill the budget deliberately rather than by accident.

What the published limits are, platform by platform, is in our bounce rate thresholds by platform post. This post turns those percentages into counts you can plan with.

The formula

bounce budget = bounce-rate limit × sends in the period

Daily sends per inbox	2% target, per day	2% target, per 5-day week	5% stop line, per week
20	0.4	2	5
30	0.6	3	7.5
40	0.8	4	10
50	1.0	5	12.5

The 2% and 5% lines are planning choices, not provider rules. Mailbox providers such as Google do not publish a bounce threshold for cold senders; Google's limits page only says that sending to "a large number" of non-existent addresses can block an account (Gmail sending limits). Five percent is Instantly's default auto-pause threshold (Instantly help). Many teams aim well under it.

Why one bounce looks like a disaster

Small daily volumes make single bounces look enormous.

Sends counted	One bounce is
20 (one inbox, one day)	5.0%
100 (one inbox, under a week)	1.0%
140 (one inbox, one week)	0.7%
1,000 (one campaign)	0.1%

So a dashboard showing "5% bounce rate" for one inbox today may be one bad address. Before you pause anything, check the rolling seven-day number for that inbox and the campaign total. If both are low, the single bounce is noise. If the weekly number is high, it is a pattern.

The same logic is why sequencers wait before auto-pausing. Instantly's auto-pause applies after a campaign has 200 or more sends; lemlist alerts at 10% once 100 or more leads have been contacted (lemlist help). A campaign-level budget is the one your tool enforces. The inbox-level budget is the one you should watch.

Late bounces count against the day you sent

Some bounces arrive hours or days after the send, especially from catch-all domains and security gateways. They belong to the send that caused them, not the day they arrived. If you only look at today's sends, late bounces from Monday make Tuesday look bad. See why follow-ups bounce more than step 1 for how this skews step-level numbers.

Spend the budget on purpose

Different lead types use the budget at very different rates.

Lead type	Typical share of the budget it uses	How to treat it
Verified valid, recent	Very little	The bulk of every inbox's day
Verified valid, months old	More, as people leave	Re-verify before reuse
Catch-all, higher grade	Some	A capped share, sent after the valid leads
Catch-all, lower grade	A lot	Small test or skip
Unverified	Unpredictable	Don't send; verify first

A worked version for one inbox sending 40 a day with a 2% weekly target (4 bounces a week):

Segment	Sends per day	Sends per week	Assumed bounce rate (illustrative)	Expected bounces per week
Verified valid	34	170	0.5%	0.85
Catch-all, higher grade	6	30	8%	2.4
Total	40	200		3.25

The inbox stays under its 4-bounce budget, with a little room for bad luck. If the catch-all share went up to 15 a day at the same rate, that segment alone would produce six bounces a week and blow the budget. That is why the catch-all share is capped per inbox, not per campaign. Our catch-all leads in sequences guide covers the rest of the setup.

The bounce rates in that table are assumptions for the example. Measure your own: run a new lead source or a catch-all segment as a small test first, as described in testing a new lead source.

When the budget runs out

1. Stop the segment that caused it, not the whole inbox, if you can tell which one it was.
2. Read the bounces. Bad addresses are a list problem. Policy, spam or reputation text is a sending problem and needs a different fix. Paste them into Bounce Doctor.
3. Check for concentration. If most bounces came from one company domain, drop that domain and carry on. See bounces from one domain.
4. Suppress every bounced address globally, so another campaign does not send to it.
5. Resume at a lower volume for a few days once the list is cleaned.

Track it in one sheet

Per inbox, per week:

Inbox	Sends	Bounces	Rate	Budget at 2%	Left
anna@sendco.io	200	3	1.5%	4	1
ben@sendco.io	200	6	3.0%	4	-2

The bounce rate calculator does the percentages, and the cold email volume calculator helps plan sends per inbox.

Where SimpleVerifier fits

Verification is what keeps the valid segment's share of the budget near zero. SimpleVerifier only marks an address valid when a mail server confirmed the mailbox, and grades catch-alls instead of passing them as valid, so you can decide how much of each inbox's budget they get. Upload a list on the verify page; the first 100 checks are free with a Google sign-in. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing.