Reply rate vs positive reply rate vs meeting rate: how do they differ?

The short answer

Reply rate is any response at all, positive reply rate is just the people who sound interested, and meeting rate is calls that actually land on the calendar. Only the last one pays. In our invented example below, two campaigns share a 3% reply rate and one books three times as many meetings because more of its replies are positive, so track all three, and write down the denominator for each.

Updated

What does each metric measure?

Metric Formula What it tells you What it hides
Reply rate Replies ÷ emails sent (or delivered) Whether anyone responds at all Unsubscribes, "not interested" and auto-replies count if you don't filter them
Positive reply rate Replies that show interest, as a share of all replies (or of emails sent) Whether the offer and audience fit Interest isn't intent to buy
Meeting rate Meetings ÷ emails sent (or delivered) Whether the ask converts Booked isn't held; no-shows count until you separate them

Formulas vary by source, and that's the main source of confusion. In Instantly's 2026 benchmark report, overall reply rate is every reply, follow-up replies included, as a share of every email sent. Instantly's own guide to calculating reply rates counts only unique human replies and divides them by delivered emails (sent minus hard bounces); it treats positive reply rate as a share of all replies, and divides meetings by delivered emails. Same vendor, different denominators, and "positive reply rate" there is a share of replies, not of sends.

How do you keep the three consistent?

Pick one denominator and report everything per 100 emails sent. Here is the layout we'd use (our recommendation):

Number Per 100 sent How to read it
Replies 3.0 Reply rate
Positive replies 1.8 60% of replies are positive
Meetings booked 0.9 Half of positive replies book
Meetings held 0.7 The ones that show up

Those figures are illustrative, not benchmarks. The table shows the shape: each row is a smaller number than the one above, and the gaps between rows tell you where to work.

Why do two campaigns with the same reply rate book different meetings?

Because replies aren't equal. Here is an invented example, per 1,000 emails sent, with the same 3% reply rate:

Campaign A Campaign B
Replies 30 30
Share that are positive 60% 20%
Positive replies 18 6
Share of positive that book 50% 50%
Meetings 9 3
Meeting rate 0.9% 0.3%

Campaign B probably reaches the wrong people or makes an offer that triggers "not interested". At our house volume of about 2,520 emails a month for one rep (4 inboxes × 30 sends × 21 days), A books about 23 meetings and B about 8 (our math). A reply-rate dashboard shows no difference between them.

What do the calculator's starting numbers mean?

Our calculator estimates the sends, replies and meetings you need. It starts at a 3% reply rate and a 35% reply-to-meeting rate. Multiply them: 3% × 35% = 1.05 meetings per 100 emails, or about 10 per 1,000 (our math). That's why the difference on this page matters: use the same definition in both boxes. If you track positive replies, enter your positive reply rate per email sent (positive replies ÷ emails sent) in the reply-rate box and the share of those that book in the next one. If you track all replies, enter your raw reply rate and the share of all replies that book. Don't pair a raw reply rate such as the 3.43% average on Instantly's platform with a booking rate measured on positive replies only.

The calculator's reply-rate box expects a per-email rate: replies divided by emails sent, with follow-up replies counted, the same unit as Instantly's 3.43% average and not the share of prospects who ever reply. With 5 touches per prospect, a 3% per-email rate works out to roughly 14% of prospects replying at some point if every email had the same chance (our math: 1 minus 0.97 to the 5th power). Both defaults are assumptions you should replace with your own numbers.

What benchmarks exist?

For reply rate only. Instantly's 2026 report gives an average of 3.43%, a top-quartile rate of 5.5% and an elite tier of 10.7% or more. As far as we could read, the report doesn't break replies into positive and negative or give meeting rates. We found no public benchmark for positive reply share or meeting rate that we could trace to a named sample, so we're not going to quote one. Build your own baseline from the last 1,000 or more sends. If a vendor gives you a "typical" meeting rate, ask for the sample, the year and the denominator.

How many sends does each metric need to be reliable?

More as you go down the funnel, because the numbers get smaller. Our math, using the standard two-proportion test at 95% confidence and 80% power, for detecting a doubling:

Metric you test Baseline to double Sends per version
Reply rate 3.43% to 6.86% 650
Reply rate 3% to 6% 749
Meeting rate 1.05% to 2.1% 2,207

So a meeting-rate test needs about three times the sends of a reply-rate test to catch the same relative lift. A practical split: use reply rate for fast copy tests, then confirm the winner on positive replies over several weeks. The full sample-size table is in how to A/B test cold emails.

How do you track all three?

  1. Set reply statuses in your sending tool. Instantly counts an opportunity when a lead is marked Interested, Booked meeting, Completed meeting (not closed) or Closed, or carries a positive custom status, per its help center.
  2. Sort replies by hand until volume is high. Auto-replies, out-of-office and "remove me" shouldn't count as replies at all. Count unsubscribes separately.
  3. Log the meeting. Mark it booked when it's scheduled and held when it happens, so you can see no-shows.
  4. Review weekly (our weekly SDR metrics sheet shows the layout). Any row that falls below your baseline tells you where to fix: reply rate points to deliverability, list or subject; positive share points to audience and offer; meeting rate points to your ask.
  5. Feed the results back into your math. If your meeting rate per 100 sent is 0.9, the calculator tells you how many you need to hit a target.

When should you skip each metric?

  • Reply rate: skip it as your only number. Instantly's benchmark counts every reply, and as far as we could read it doesn't separate positive from negative.
  • Positive reply rate: skip it as a test metric on small lists. With a few hundred sends, a handful of replies swings the percentage. Use it for weekly diagnosis instead.
  • Meeting rate: skip it for A/B tests under a couple of thousand sends per version. It needs the most data to be reliable.
  • Open rate: skip it as a winner metric. Smartlead lets you pick it as a winner metric, next to reply, positive-reply and click rates, but an open isn't a conversation.

See also: How do you cut no-shows, and what is a good show rate?; What words get a prospect to put a time in the calendar?

The sending days, sends per inbox, inboxes per rep and touches per contact on this page are our house assumptions, with one line on why we use each.

Sources

Research and vendor pages accessed October 1, 2026.

Frequently asked questions

Which positive reply share should you target?

We found no sourced benchmark. Measure your own: positive replies divided by total replies, over at least a few hundred replies, and track the trend.

Is reply rate the same as response rate?

Usually, yes. Check the formula: some sources divide by emails sent, others by delivered emails, and some count only human replies.

How do I count out-of-office and unsubscribe replies?

Leave them out of reply rate and count unsubscribes separately. Instantly's guide counts unique human replies, which excludes auto-responses.

Which metric should I optimize first?

Meetings held, then work backward. Use reply rate for quick copy tests and positive replies to check the audience and offer. For copy structure, see cold emails that work.

How many meetings should 100 emails book?

It depends on your numbers. At the calculator's starting inputs, 3% of emails getting a reply and 35% of those replies booking, it's about one meeting per 100 emails (our math). Replace both inputs with your own.

Keep reading