What Is a Good Cold Email Deliverability Rate?

Open any cold email platform and you'll see a deliverability number somewhere between 97% and 99.5%. It looks great. It also tells you almost nothing about whether a human being read your email.

That number is the *accepted* rate: the percentage of messages the receiving mail server took without rejecting. A message can be accepted and then filed straight into Junk, quarantined by a security gateway, or dropped silently. It still counts as delivered. This is why teams with a "99% deliverability rate" send 5,000 emails and get four replies.

So when someone asks what a good email deliverability rate is, the honest answer is: pick a better metric. Deliverability for cold email is four separate numbers, each with its own target range and its own failure mode. Here's what to track and where the lines are.

{"h2": "placeholder"}

The four numbers that define cold email deliverability

• Hard bounce rate — addresses that don't exist or servers that refuse the recipient outright. This is a list-quality metric first and a reputation metric second, because high bounces damage your sender reputation fast.
• Accepted / delivered rate — what your tool reports. Useful only as a bounce inverse. Ignore it as a standalone success measure.
• Inbox placement rate — of the accepted mail, what fraction landed somewhere a person will see it (Primary or a normal folder), versus Junk, quarantine, or Gmail's Promotions tab. This is the number people *mean* when they say deliverability.
• Engagement-confirmed reach — verified human replies and genuine link visits. This is the only signal that survives bots, security scanners, and pixel-blocking. If placement is good but engagement is zero, the problem is your offer, not your DNS.

The distinction between the second and third items is the whole game. We wrote a full breakdown in Email Deliverability vs. Inbox Placement — the short version is that delivered means "accepted by the server" and placed means "visible to the person."

Target ranges for cold outbound

These are ranges we consider healthy for cold B2B sequences sent from properly configured domains with verified lists. They are lower than marketing-email benchmarks because cold mail has no prior engagement history to lean on.

A few notes on why these specific lines:

Bounce rate under 2%. Google and Microsoft both treat sudden bounce spikes as a spam-cannon signal. A list that bounces at 6% isn't just wasting sends — it's actively teaching the filters that you don't know who you're emailing. Verifying before send costs a fraction of a cent per address and is the single cheapest deliverability improvement available. See Email Verification for Cold Email.

Spam complaint rate under 0.10%. Google Postmaster Tools flags 0.10% as the "caution" line and 0.30% as the point where filtering tightens hard. At cold-email volumes, 0.30% means roughly 3 complaints per 1,000 sends — which is two bad segments away. Track it per domain, not in aggregate.

Inbox placement 75%+ as acceptable. Nobody hits 100% on cold mail. Corporate security gateways quarantine unknown senders as policy, regardless of your setup. If you send 1,000 emails and 800 reach an inbox, that's a working setup, not a broken one.

Why one average number is misleading

Deliverability isn't a single rate — it's a rate per receiving provider, and the spread is wide. A typical breakdown for a healthy cold-email domain looks something like:

• Google Workspace recipients: 85–95% inbox placement, most in Primary if the copy is clean
• Microsoft 365 recipients: 55–80% placement, with more Junk and more gateway quarantine
• Consumer Gmail/Outlook.com: high placement but frequent Promotions/Other routing
• Domains behind Proofpoint, Mimecast, or Barracuda: 30–60%, largely policy-driven

If your list is 70% Microsoft 365, your blended placement will look worse than a competitor selling to startups on Google Workspace — even with identical infrastructure. Compare yourself to your own baseline over time, not to a number you read in a blog post (including this one). Microsoft in particular is stricter during the first weeks of a mailbox's life, which is why warming up Microsoft 365 mailboxes takes longer than Google.

How to actually measure placement

You can't see placement from your sending tool, because the receiving server doesn't tell you where it filed the message. Two methods get you close:

Seed mailboxes. Maintain a small set of real mailboxes across Google Workspace, Microsoft 365, consumer Gmail, and Outlook.com. Inject them into each campaign and check where the message landed and which folder. Ten to fifteen seeds gives you a directional read; it won't capture corporate gateway behavior, and seeds drift if you never interact with them normally.

Reply-rate deltas. If your reply rate drops from 5% to 1.2% while your copy, list source, and offer are unchanged, placement moved. This is a lagging indicator — you'll notice four days late — but it's the most honest one you have, because it measures humans.

Run both. Seeds tell you *now*, reply deltas tell you *truth*.

The thresholds that should trigger action

Numbers are only useful if they're attached to decisions. Here's a rule set that has worked well in practice:

• Bounce rate above 3% on a campaign → pause it, re-verify the remaining list before continuing.
• Placement drops 15 points week over week on one domain → stop that domain's sends, keep the mailboxes on warm-up traffic only for 7–10 days.
• Complaint rate crosses 0.20% → cut daily volume in half and audit the segment that generated them.
• Reply rate falls below a third of your trailing 30-day average with no copy change → treat it as a placement problem, not a copy problem, and check seeds first.
• One mailbox in a rotation underperforms the others by 2x on reply rate → pull it. Individual mailbox reputation degrades independently of the domain.

The mistake almost everyone makes is reacting to a single bad day. Daily volumes in cold email are small enough that a 40-lead campaign to one industry can swing every metric. Look at 7-day rolling windows, and always segment by receiving provider before concluding anything.

What good looks like at steady state

A well-run cold email operation sending 500 emails a day across 10 mailboxes and 3 domains should see roughly: bounce under 1.5%, seed placement in the mid-80s, Gmail Primary on most Google recipients, complaints near zero, replies in the 4–7% range, and no single mailbox drifting far from the others. Nothing dramatic — just boring, stable numbers that don't move much week to week.

If you're well below that, the cause is almost always one of four things: an unverified list, a domain missing proper authentication, mailboxes pushed past sensible daily limits too early, or copy that trips spam filters. In that order of frequency.

Where Sendvanta fits

Sendvanta was built around the gap between "delivered" and "read." It scores deliverability health in layers — mailbox, domain, DKIM alignment, and IP — and automatically slows or pauses sending when a layer crosses a risk threshold, instead of reporting 99% while your placement quietly collapses. Drafts get SpamAssassin-scored before send, seed-mailbox tests measure real inbox placement per provider, and engagement classification separates verified human replies and visits from security-scanner clicks and bot opens, so your reply-rate baseline means something.

You connect your own Gmail, Microsoft 365, or SMTP mailboxes — free on every plan, including the $0 Free tier (1,000 active leads, 3,000 emails/month, up to 10 of your own SMTP mailboxes). Paid plans run $29, $59, and $99/mo, with managed mailboxes at $4/mo each if you'd rather not provision your own. Mail always goes through your infrastructure, never a shared IP pool.

Benchmarks in this post reflect ranges observed across cold B2B outbound programs and were reviewed on 18 February 2026; provider filtering behavior changes, so treat them as starting points and track your own baseline.