How many cold calls does one meeting actually take?
The honest answer is more than most benchmarks imply, because the widely quoted rates are per conversation and get read as per dial. Put in your own funnel, or start from one of the two published ones — they disagree by about three times, and neither is hidden behind a form.
Turning meetings into pipeline
Both of these are guesses at the top of a cold funnel, which is why the pipeline figure sits below the meeting figure rather than above it.
382
that is 0.26% of dials, or 1.0 meetings per rep per day
Where the two funnels come from
There is no consensus number, and a page that gives you one is averaging two studies that measured different teams. Both published funnels are below, unaltered.
| Belkins | SkipCall | |
|---|---|---|
| What it is | A measurement across 175,000+ dials in 2025 | A worked example in a 2026 benchmarks article |
| Connect rate | 9.9% of dials | 10% of dials, with 8–12% cited as the generic range and 18–22% on verified mobile |
| Conversation rate | 58% of connects reach a real conversation | Not separated — "live conversations" is used for connects |
| Meeting rate | 4.6% of conversations | 10% of live conversations |
| End to end | About one meeting per 370 dials | About one meeting per 100 dials |
Why our own figure used to be wrong. Until this tool was built, our guide and glossary both said dial-to-meeting conversion runs around 2–3% — roughly one meeting per 40 dials — and cited Belkins for it. Belkins reports about one per 370. The error was reading a per-conversation rate as a per-dial one, which is the same denominator mistake our compliance guide warns about for the 3% abandonment rule. Both pages are corrected. It is on this page because a tool that exists to fix that exact confusion should say where it found it.
Does better data move this number?
Yes and no, and the difference is the one most worth understanding here, because two unrelated things both get called "better data" and only one of them changes the ratio above.
| Coverage — do you have a number at all | Accuracy — is the number right and current | |
|---|---|---|
| What it changes | How much of a list is dialable | The connect rate on every dial |
| Effect on dials per meeting | None. Each dial performs exactly as before | Roughly proportional. Double the connect rate and halve the dials per meeting |
| Effect on meetings | Going from 60% to 80% coverage makes a third more of the same list dialable, so a third more meetings come out of it | On the published ranges, moving from generic data at 8–12% to verified mobile at 18–22% takes roughly 380 dials per meeting to roughly 200 |
Both are worth having and they compound: more of the list reachable, and each of those calls twice as likely to reach a person. But only accuracy shows up in the number at the top of this page. Coverage shows up one level higher, in how many meetings a given list is worth — which is why a vendor quoting a match rate has not told you anything about your connect rate, and a vendor quoting a connect rate has not told you how much of your list they can even reach.
The connect-rate figures above are SkipCall's published ranges; the coverage arithmetic is just arithmetic. We are deliberately not putting a market-average match rate on this page, because we have not found one published to a standard worth citing.
What the number does not tell you. Dials per meeting is a ratio, not a target. Halving it by calling a more reachable but less qualified segment is a step backwards that every activity dashboard will report as progress. It is worth tracking against your own history rather than against anyone else's benchmark, including these two.
Sources B2B cold calling benchmarks, 175,000+ dials — Belkins B2B cold call connect rate benchmarks 2026 — SkipCall What dial-to-meeting rate measures Abandonment rate calculator
Common questions
How many cold calls does it take to book one meeting?
Between roughly 100 and 370, on the two published funnels. Belkins measured about one meeting per 370 dials across 175,000+ dials; SkipCall’s worked example implies about one per 100. The spread is real — they measured different teams with different data — so the calculator ships both rather than averaging them into a number neither source supports.
Why is my dial-to-meeting rate so much lower than the benchmarks I see quoted?
It probably is not. Most quoted figures are per live conversation, not per dial, and the two differ by ten to twenty times. A 10% meeting rate sounds like one meeting per ten calls and actually means one per hundred, because only about one dial in ten is answered at all. If a benchmark does not say what it is divided by, it is not a benchmark.
Does better data change these rates?
Only one kind does. Coverage — whether you have a phone number for a contact at all — changes how much of a list is dialable, not how a dial performs, so going from 60% to 80% coverage yields about a third more meetings from the same list at exactly the same dials-per-meeting. Accuracy is the one that moves this page’s number: on the published ranges, generic data at 8–12% connect against verified mobile at 18–22% is roughly 380 dials per meeting against roughly 200. A vendor quoting a match rate has told you nothing about your connect rate, and vice versa.
Does a parallel dialer change these rates?
No, and that is the honest limit of the argument. Connect rate, conversation rate and meeting rate are properties of your data, your list and your opener. A dialer changes how many dials fit in a day. More dials at the same rates is more meetings; it is not a better funnel.
What counts as a "conversation" rather than a connect?
A connect is anyone picking up. A conversation is one that gets past the opener — the wrong person, an immediate hang-up and a gatekeeper are all connects and none of them are conversations. Belkins found 58% of connects reached a real conversation. SkipCall does not separate the two, which is why its preset puts the conversation stage at 100% and the whole drop on the meeting rate.
Why is pipeline shown below meetings rather than above?
Because it is the least reliable number on the page. Pipeline needs an average contract value and a meeting-to-opportunity rate, both guesses at the top of a cold funnel, and multiplying two guesses produces a figure that looks precise and is not. Dials per meeting needs neither.
Get started
Ready to eliminate dead dials and marked-up credits?
Seven days, 1,000 credits, no credit card. Or thirty minutes with the two people who would do the work.