← Blog
Outbound·18 min read

Replies but No Meetings: What Your Cold Email Reply Rate Is Hiding

On 61,770 classified replies, 45.1% were out-of-office and 29.9% were rejections. And below ~150 sends, zero meetings is the expected result anyway.

TathagataFounder, ParaphrasePublished September 28, 2026
Three quartersof your repliesare robots.AND 33 SENDS TELLS YOU NOTHING.REPLY RATEWHICH ONE?

Last updated: 28 September 2026

Someone posted this on r/Coldemailing last week: 33 cold emails delivered, one in seven replied, zero closed. Where's it breaking?

It is a good question, asked by someone doing the right thing: counting. The same week, in a different subreddit, a founder posted 565 visitors, 85 signups, $0 revenue, and asked the same question about a different machine.

Both deserve a better answer than "improve your copy". But the honest answer starts somewhere annoying, and it is not a diagnosis.

This is the part nobody wants to hear, so it goes first.

Run the binomial arithmetic on 33 sends and zero meetings and you get a 95% exact confidence interval of 0% to 10.58%. That range includes "your campaign is fine". It also includes "your campaign is exceptional". The observation does not distinguish between them.

33 SENDS, ZERO MEETINGSHow often a healthy campaign shows you nothingProbability of observing zero meetings in 33 sends, by the campaign’s true booking rate.1% true rate71.8%a weak but working campaign2% true rate51.3%a rate most teams would take5% true rate18.4%strong10% true rate3.1%exceptionalExact binomial (Clopper–Pearson) computation on n=33. The 95% interval around 0 of 33 is 0% to 10.58%.
Read the second row. At a booking rate most outbound teams would happily take, a run of 33 sends produces zero meetings more often than it produces one. The zero is the most likely single outcome, not a fault.

Read the middle row again. At a true booking rate of 2%, which most outbound teams would take, a run of 33 sends produces zero meetings more often than it produces one. The absence is the most likely single outcome. It is not evidence of a fault.

So before diagnosing, get to a number where a zero would be surprising:

THE VOLUME BEFORE THE DIAGNOSISSends needed before a zero is evidenceEmails to one consistent segment, at two assumptions about the true booking rate.80% chance ofseeing a meeting80at 2%160at 1%95% chance ofseeing a meeting148at 2%298at 1%33: where the question was asked
The Reddit post that prompted this had 33. Below roughly 150 sends to one consistent segment, an absence of meetings is not information, and changing the subject line in response to it is a way of feeling busy.

Worth noting who else says this. lemlist, a company that sells sequencing software and has every commercial reason to encourage optimism about small campaigns, publishes its own guidance as "at minimum 100 sends per variant, ideally 200+" and "at minimum 2 weeks and 100+ sends. Less than that and you don't have enough data to draw conclusions."

When the vendor and the statistics agree against the vendor's interest, that is usually the number.

None of this means stop. It means the first job is volume, not diagnosis, and that a consultant who hands you a six-point audit at n=33 is reading tea leaves with you.

This is the single most useful finding I came across, and it reframes the original question entirely.

61,770 REPLIES, CLASSIFIEDThree quarters of your replies are not people saying yesShare of all cold email replies, by sentiment.45.1%29.9%14.1%Auto-reply / out-of-officeNegative, not interestedPositive / interestedthe only bucket that can bookEffective interested rate: 0.64% of contacts, about 1 in 157.Sales.co, 61,770 replies from 2M+ cold emails across 161 campaigns. Published 4 Feb 2026. Sells cold email services and lists.
The largest sentiment-classified sample published. Three quarters of everything counted as a “reply” is a robot or a refusal, which is why an unusually high reply rate on a small send is a warning rather than a win.

Go back to the Reddit post. A 15% reply rate is far above every published benchmark: Belkins reports 0.45% across 7.53 million emails, Sales.co 2.09%, Saleshandy 3.7% across 53.1 million, Lavender 3.4–5.2% across 231,818.

A 15% reply rate is not a triumph in that company. It is a signal that something else is being counted. Given that 45.1% of replies in the largest sentiment-classified sample are automated, the most probable explanation for an unusually high reply rate on a small send is that out-of-office bounces are in the numerator.

Which means the answer to "one in seven replied, zero closed" may be that roughly one in seven did not reply. A machine did.

The fix is free and takes an afternoon. Split your reply count four ways (automated, negative, neutral, positive) before you look at anything else. Belkins excludes auto-replies and bounces from its reply rate. Lavender excludes automated replies but includes negative ones. Those two definitions produce different numbers from identical campaigns, and neither is wrong. Yours needs to be written down.

Since February 2024, Google has required SPF or DKIM authentication, TLS, valid forward and reverse DNS, and a spam rate below 0.3% in Postmaster Tools. Senders of 5,000+ messages a day to personal Gmail accounts need SPF and DKIM, plus DMARC and one-click unsubscribe. Yahoo's rules run in parallel, though Yahoo declines to publish a volume threshold at all: "We will not specify a volume threshold."

The useful part is not the rules. It is what Google says happens when you break them.

WHERE THE ENFORCEMENT HAPPENSA reply is proof the gates openedThe documented mechanisms, and the point at which a human enters.AuthenticationSPF / DKIM / DMARCSpam ratebelow 0.3%Rate limitingvolume throttledSpam folderingdelivered, unseenA human reads itand only now can replyevery documented enforcement mechanism sits hereThe one real exception: multi-domain sending where one domain is burned. Replies keep arriving from the healthy ones.Google Workspace Admin Help (sender guidelines, eff. 1 Feb 2024; requirements FAQ) and Yahoo Sender Hub best practices.
Google documents its enforcement as failure codes, spam foldering and rate limiting. All of it happens to the left of the reader. Nothing in that list can take a human who replied to you and stop them booking.

Failure codes, spam foldering, rate limiting. Every one of those acts on the message before it reaches a person. None of them can take a human who replied to you and prevent that human from booking a meeting.

So if replies are arriving at a normal rate, bulk-sender compliance is not your primary fault. Cross it off. This is the cleanest elimination available, and it is documented by the two parties doing the enforcing rather than inferred from a vendor's blog.

Three caveats I am not going to bury. First, partial failure is real: mail can land in Gmail and be foldered at Microsoft 365, and an aggregate reply rate hides a per-provider collapse. If you send across multiple domains and inboxes, one burned domain can vanish silently while the healthy ones keep replying. Second, Yahoo computes its spam rate on mail delivered to the inbox, so a sender already in the spam folder can show a flattering complaint rate. Third, Belkins reports that open-pixel tracking was abandoned across the industry during 2024 because it hurt deliverability, which removed the tool most people used to check inbox placement in the first place.

If you want the full version of that diagnosis, it is a separate problem with a separate method.

I went looking for this specifically, because it is the exact question in the Reddit post. Here is what ten sources report.

REPLY → BOOKED MEETINGThe number everyone needs and nobody publishesWhat each vendor dataset actually reports for the reply-to-meeting step.Sales.co61,770 replies classifiedno meeting figure at allLavender231,818 emailsno meetings-booked rateInstantlyno dataset disclosedrecommends tracking it, publishes noneWoodpecker“20M+”, no date rangeone blended reply rate onlyBelkins7,530,489 emails≈ 3.49% (derived from their two figures)lemlistno sample size stated30–60% of repliesThose two figures differ by roughly 10 to 17 times. Neither publishes the method that would reconcile them.Belkins (7.53M emails, 34,393 replies, “over 1,200 appointments”, Jan–Dec 2025); lemlist benchmarks, 5 Mar 2026. Both sell outbound.
Ten sources, one derived number and one unsourced assertion, differing by ten to seventeen times. The single step the question is about is the step the industry does not publish.

Sales.co classifies 61,770 replies by sentiment and reports no meeting figure at all. Lavender publishes the clearest reply definition anywhere and no meetings-booked rate. Instantly recommends tracking meetings per thousand sends, then publishes no benchmark. Woodpecker reports one blended reply rate with no date range.

Belkins is the only company whose published numbers let you derive it: 34,393 replies and "over 1,200 appointments" from 7,530,489 emails. That is 3.49% of replies becoming appointments, and about one meeting per 6,275 emails. I should flag that this is my arithmetic on their two figures, not a number Belkins publishes, that "over 1,200" may be a floor, and that Belkins also runs calls and LinkedIn so the attribution is not clean.

Against that, lemlist asserts 30–60%. Both are vendors. They differ by more than tenfold, and neither publishes the methodology that would reconcile them.

The benchmark spread is mostly a definition artefact, not a performance gap. Belkins says so themselves, which is unusually honest for a vendor: "A 5% reply rate against openers and a 0.45% reply rate against total sends can describe the same campaign."

THE SAME CAMPAIGN, FIVE NUMBERSA tenfold spread, mostly definitionalPublished average reply rates, with what each one counts.Belkins0.45%7.53M emailsexcludes auto-replies and bouncesSales.co2.09%2M+ emailsall replies, then classifiedWoodpecker3.43%no date range givennot separatedSaleshandy3.7%53.1M emailsAI-classifiedLavender5.2%231,818 emailsexcludes OOO, includes negativesSaleshandy’s own report contradicts itself here by about thirtyfold. Use its table, not its prose.Vendor-published platform data, each primary as to its own numbers. All five sell cold email products or services.
Belkins states the problem themselves: a 5% reply rate against openers and a 0.45% rate against total sends can describe the same campaign. You cannot locate yourself in this to better than an order of magnitude.

It gets worse if you look closely. Saleshandy's report states an average positive reply rate of "3% to 5%" in its prose while its own channel table puts email-only positive replies at 0.11%, and 99% of its sequences are email-only. That is a thirty-fold contradiction inside one document. Use the table, not the prose. And the figure "3.43%" is attributed by different aggregators to two different vendors, which is a circular-citation smell.

So you cannot locate yourself against these numbers to better than an order of magnitude. Anyone showing you a tidy benchmark table for reply-to-meeting is showing you something that does not exist.

I sell outbound systems. The frame I use is that outbound is several distinct jobs (list, infrastructure, message, sequence, qualification, handoff) and that most teams own some of them well and none of them completely.

I went looking for evidence that the six-way split is real, and I did not find it.

OUR FRAME, NOT A FINDINGSix jobs is how we look, not what was measuredThe frame used in this post, beside what has actually been published.ListInfrastructureMessageSequenceQualificationHandoffWHAT IS ACTUALLY PUBLISHEDA two-way splitinbound vs outbound, Bridge Group 2014A three-step diagnostictechnical → targeting → copy, from a vendorAnd the competing explanation: 29.9% of replies are explicit rejections. That may be the offer, not the process.Bridge Group, “Separating Inbound & Outbound SDR Roles”, 9 Jul 2014; lemlist benchmarks, 5 Mar 2026; Sales.co, 61,770 replies.
Drawn by hand deliberately. The post argues this six-way split has no empirical backing, so rendering it as a clean measured chart would claim a precision the evidence does not support.

What exists is thinner. The Bridge Group documented in 2014 that roughly 40% of companies separate inbound and outbound SDR roles, with a single-company case study reporting 20–30% higher production after the split. That is a two-way division, twelve years old, with no cross-dataset performance comparison. lemlist publishes a three-step order: technical setup, then targeting, then copy. Neither is six.

I should also name the figure that gets quoted at me. Several aggregator pages attribute "16% higher performance for specialised teams" to The Bridge Group. I checked the source report and could not find it there. The same pages report the 2025 edition's ramp as 3.2 months, attrition as 34% and quota attainment as 57%. The primary document says 3.0 months, 40% and 60%, across 351 companies. Do not use the aggregators.

The honest version of the frame: use the six jobs to organise where you look, not as a claim that the fault is definitely among them.

This is the part that is against my interest. An agency whose offer is "outbound is six jobs and nobody owns all six" has a commercial reason to want the answer to be a job is broken. Predictable Revenue makes a version of the same argument about saturation, and sells outbound coaching built on the playbook it is defending. Nobody selling a fix is a neutral judge of whether the fix is the right one.

The competing explanation is simple: the offer does not warrant a meeting. Sequence tuning, list hygiene and handoff speed do not touch that.

And it has data behind it. If 29.9% of the humans who reply are saying no outright, that is a market answering your question directly. It is the cheapest research you will ever be handed, and it arrives whether you asked for it or not.

The practical test is to read the rejections rather than count them. Rejections that say "wrong time" or "not my remit" point at targeting, which is a process problem. Rejections that say "we already solve this" or "we do not have this problem" point at the offer, which is not. Twenty rejections read carefully will separate those two faster than any audit, including mine.

1. Define your terms, in writing. Does your reply rate include out-of-office? Bounces? Rejections? Belkins excludes automated replies and bounces. Lavender excludes automated but includes negative. Until yours is written down, your number cannot be compared to anything, including your own number from last quarter.

2. Re-count what you already have. Four buckets: automated, negative, neutral, positive. If you have 5 replies and 3 are out-of-office, you have 2 data points, not 5, and you now know the campaign has not actually been tested.

3. Get to volume before you get to opinions. About 148 sends to a consistent segment before a zero means anything at a 2% assumption, roughly 298 at 1%. Below that, changing the subject line and re-reading the tea leaves is a way of feeling busy.

4. Measure the step nobody publishes. Reply → positive → booked → held, with your own definitions attached. Given that no credible public figure exists for reply-to-meeting, your own number is worth more to you than every benchmark in this post combined. It is also, unusually, worth publishing.

Two things that are worth doing while you wait for volume, both from primary platform data. Saleshandy found 44% of positive replies come from follow-ups, with the first follow-up alone accounting for 26.4%, so a sequence that stops at one email is leaving close to half the positive replies unsent. And Gong found that cold calls which did not connect still lifted email reply rates from 1.81% to 3.44%, measured across 300 million calls.

If you are paying someone else to run this, the same four steps are the audit, and what a real reporting pack should contain is a separate question with a more settled answer. If you are deciding whether to hire an agency at all, the cost comparison is here.

Why do my cold emails get replies but no meetings?
Most often because the reply count includes replies that were never going to become meetings. On 61,770 replies classified by sentiment by Sales.co, 45.1% were auto-replies or out-of-office and 29.9% were explicit rejections, leaving 14.1% positive. Their effective interested rate was 0.64% of contacts, about 1 in 157. Split your replies four ways before concluding anything about the step after them.
How many cold emails do I need to send before zero meetings means something?
Roughly 148 sends to have a 95% chance of seeing at least one meeting if your true booking rate is 2%, or 80 sends for an 80% chance. At a 1% true rate those become 298 and 160. At 33 sends, zero meetings occurs 51.3% of the time even at a healthy 2% rate, so it carries no diagnostic information. lemlist's own published guidance says 100 sends per variant minimum, 200 or more ideally.
Can a deliverability problem cause replies with no meetings?
Not as the primary fault. Google documents its bulk-sender enforcement as SMTP 4.7.x and 5.7.x failure codes, spam foldering and rate limiting, all of which act before a human reads the message. A normal reply rate is evidence of inbox placement. The one real exception is multi-domain sending where a single domain is burned: replies keep arriving from healthy domains while the burned one silently disappears from the aggregate.
What percentage of cold email replies turn into meetings?
No credible public figure exists. Across ten vendor datasets the only explicit number is lemlist's 30-60% of replies, published with no sample size, date range or methodology. Belkins' own two published figures, 34,393 replies and over 1,200 appointments from 7,530,489 emails, imply about 3.49%. Those differ by 10 to 17 times. The step is not measured comparably in public.
What is a good cold email reply rate in 2026?
The published range runs from 0.45% to about 5.8% across primary vendor datasets, and the spread is mostly a denominator artefact rather than a performance difference. Belkins states it directly: a 5% reply rate against openers and a 0.45% reply rate against total sends can describe the same campaign. Belkins reports 0.45% on 7.53 million emails, Sales.co 2.09%, Saleshandy 3.7% on 53.1 million, Lavender 3.4-5.2% on 231,818.
Is the "respond within 5 minutes" rule true for cold outbound?
It is not evidence about cold outbound. The 2007 InsideSales.com and MIT study that produced the 100x and 21x figures explicitly studied leads captured through a web form and the speed of phone callback to them. Its own document states that each of the six companies defined "qualified" differently, that contact meant a call lasting two to six minutes, that the multipliers are odds ratios rather than rates, and that the study did not address close ratios.
Should I add cold calling or follow-ups first?
Follow-ups, on the available data. Saleshandy found 44% of positive replies come from follow-ups across 53.1 million emails, with the first follow-up alone accounting for 26.4%. Gong separately found that cold calls which did not connect still lifted email reply rates from 1.81% to 3.44% across 300 million calls, so calling helps too, but a sequence that stops after one email is leaving the larger share on the table.

The question "where is it breaking" assumes a break. Before accepting that assumption, three cheaper explanations have to be cleared: the sample is too small to show anything, the reply count is measuring robots, and the offer is being rejected on its merits by nearly a third of the humans who answer.

Only after those does a process diagnosis earn its keep. And when it does, the evidence supports eliminating deliverability first. Not because deliverability rarely fails, but because this particular symptom is the one thing that proves it did not.

One thing I could not establish, and it matters. Nobody publishes a credible reply-to-meeting conversion rate, and nobody publishes a primary B2B meeting no-show rate either. The "56.9%" widely attributed to Gong does not appear in Gong's own 300-million-call document. I looked. If you are running outbound and you measure your own chain with stated definitions, you will hold a number that genuinely does not exist anywhere in public.

That is worth more than this post.


#outbound#cold-email#diagnostics#benchmarks#deliverability