What One Extra Live Conversation per Agent per Hour Is Worth

Take your average revenue per sale. Multiply it by your close rate. Multiply that by one. That is what a single additional live conversation is worth to you, and you probably know that number already.

Now multiply it by your agent count, then by the conversations one extra per agent-hour represents across a full year. Most owners have never done this calculation. It takes one line. When I finally ran it on my own floor, the number was larger than what I was spending on lead generation at the time, and I had been defending the lead budget in every planning meeting for years.

This article is that calculation, worked three ways, plus where the extra conversations actually come from. Everything is a formula or a labeled assumption. Nothing is a case study, because you should not believe invented case studies and neither should I.

The one-line formula

Here it is, the entire article in one expression:

Annual value = agents × extra live conversations per agent-hour × productive hours per agent per year × close rate × average revenue per sale

Five inputs. You have all of them, or close approximations, in your head right now.

• Agents: seats dialing outbound, not total headcount.
• Extra conversations per agent-hour: this article is about the value of exactly 1, so plug in 1.
• Productive hours per agent per year: dialing hours, not scheduled hours. A common planning figure is around 1,800 hours a year for a full-time agent after PTO, training, and offline time, but use your own.
• Close rate: conversions per live conversation, as a decimal. Be conservative. Use a rate from a bad month.
• Average revenue per sale: gross revenue per closed deal, before any cost.

Two honesty rules when you run it. First, use a conservative close rate, because the temptation is to use your campaign's best week. Second, count only marginally incremental conversations, meaning conversations that would not have happened otherwise. Extra dials into the same tired list generate conversations that displace others. Extra recovered answers, which is where I will land later, genuinely add volume, because the person already picked up and your dialer threw them away.

The worked table

Three example centers below. The close rate and revenue figures are stated assumptions, not measurements of any real center. Swap in your own before quoting any output.

Input	15-seat shop	60-seat center	200-seat operation
Agents	15	60	200
Extra conversations per agent-hour	1	1	1
Productive hours per agent per year	1,800	1,800	1,800
Assumed close rate	3%	3%	3%
Assumed revenue per sale	$400	$400	$400
Extra conversations per year	27,000	108,000	360,000
Extra sales per year	810	3,240	10,800
Annual value	$324,000	$1,296,000	$4,320,000

Even if you halve the close rate and halve the revenue per sale out of pure embarrassment at the output, the 15-seat shop is still looking at roughly $81,000 a year from one extra conversation per agent-hour. The arithmetic does not need to be precise to be directional. It is a multiple of every software line item on your P&L.

Sanity check the per-hour framing too. A full-time agent dials roughly 7 to 8 hours a day. One extra live conversation in that window is a 4-6% lift in conversation volume for an agent holding 18-25 conversations an hour. Not a fantasy doubling. A modest, boring, highly valuable increment.

Headcount planning versus conversion coaching

When owners want that kind of lift, they usually reach for one of two levers: hire more agents, or coach the ones they have. Both are legitimate. Both are expensive and slow, and neither is where the cheapest conversations live.

Hiring your way there

Adding conversation volume by adding seats means paying loaded salary, recruiting cost, ramp time, and additional management load, and the new seats come with the same detection problems as the old ones. Every new agent inherits the same dialer, the same dropped calls, the same misrouted voicemails. You are scaling the waste alongside the output.

Rough hiring math: if a ramped agent generates, say, 20 conversations an hour at a 3% close on a $400 deal, a new seat represents about $240 of gross conversation value per productive hour. Against a loaded cost of $19-30 an hour, hiring looks fine on paper, which is why centers do it. But the same increment available from recovering dropped answers costs no salary at all, and I will show the price of that below. Hiring should be your response to demand you cannot serve, not to conversations your own software is discarding.

Coaching your way there

Coaching moves close rate, which multiplies every conversation you already have, so it is worth doing continuously. But coaching is slow, it saturates, and it depends on managers you may not have spare cycles from. Moving a floor from 3% to 3.5% close is a genuine achievement that takes quarters of call review and role-play.

Notice what the two levers share: neither touches the number of humans who actually pick up. Coaching converts the conversations you reach; hiring adds dials. Neither recovers the person who already said hello and was classified as a machine and dropped. That third bucket is where the cheapest increment lives.

Why recovered answers are the cheapest source of extra conversations

Here is the plain-English technology sentence, once: your dialer has built-in software that guesses from the first seconds of audio whether an answered call is a person or a machine, and if it guesses wrong in one direction, it hangs up on the person.

AMDY's own measurement on real detection traffic puts that error at an estimated 10-20% of live humans dropped by the default detection in stock Vicidial-class dialers. Read that range again with this article's formula in mind. Those are people who picked up. Prospects who were home, who answered, who then heard silence and a hangup, and who now associate your caller ID with exactly that experience.

The recovery arithmetic

You do not need to believe the top of the range. Work the bottom. Suppose your dialer drops only 10% of live answers, you run 20 agents, and each agent-hour currently produces 20 live conversations. Your floor is losing roughly 2 conversations per agent-hour that real humans started.

The subject of this article is the value of 1. Recovering half of the bottom-end estimate gets you there without a single additional dial, hire, or coaching hour. If your floor is at the top of the range, recovering a quarter of it does the same. Compare that to what you would spend on lead gen for equivalently incremental conversations, and remember that a recovered answer costs the same per conversation whether it is your 10,000th this month or your first: a fraction of a cent at detection rates like $0.00025 each in overage, with paid plans from $79 a month for 500,000 included detections (pricing).

I will not tell you AMDY recovers some specific percentage for some specific center, because any such number I quoted without your traffic in front of me would be invented. What I will stand behind is the mechanism and the price. The mechanism: a server-side AI classifier that listens to the answered audio and returns a verdict starting within about 125 milliseconds, instead of fixed timer thresholds. The price: free to test, on your own traffic, at 50,000 detections a month with no card.

Where the hour boundary matters

A fair question about this whole framing: why per hour, and why exactly one? Because per hour is the unit your floor actually operates in. Shifts are scheduled in hours, staffing decisions are made against hourly contact rates, and queue pressure is measured per interval. A conversation increment expressed per hour plugs directly into decisions you already make weekly.

One per hour is also deliberately unimpressive. It is roughly a 4-6% lift in conversation volume for a typical agent, small enough that no vendor would build a pitch around it and no CFO would dismiss it as fantasy. That is the sweet spot for a number you can actually defend. When a claim sounds modest, the arithmetic behind it gets scrutinized less, which is all the more reason to scrutinize it yourself.

The distribution caveat

The per-hour framing hides a distribution. Recovered answers will not arrive as a tidy one-per-hour drip per agent. They arrive in bursts, because contact rates cluster. An agent might get three extra conversations between 10 and 11 a.m. and none for the next two hours. That burstiness is fine for total value but it does two things worth planning for.

First, peak hours get denser, which is good news if your agents have idle capacity at peak, and they usually do between dials. Second, it concentrates the benefit on your best-connected lists, which is where your competition is also dialing. Both effects argue for the same conclusion as the earlier section: the increment lands hardest exactly where a live conversation is worth the most.

The agent-quality multiplier

There is a second multiplication hiding inside the first one, and it favors centers with strong closers. The formula values every conversation at your average close rate times your average revenue per sale. But recovered conversations are not distributed randomly across your floor. They flow to whichever agents are on the dialer when they happen, and if you staff your best people at peak contact times, a disproportionate share of recovered answers lands on your best closers.

That means the floor-average valuation in the table is, if anything, conservative for centers that schedule well. The same recovered conversation is worth more when a top-quartile closer takes it than when a new hire does. I will not put a number on that tilt because agent-quality distributions vary enormously, but the direction is not in doubt: the value of recovered answers scales with the quality of the agents receiving them.

There is a talent-retention echo here too, the same one from the payroll side of this problem. Floors that waste agent time on misrouted voicemails and false starts are floors where closers spend a meaningful slice of peak hours doing nothing sellable. Agents figure out which floors let them sell and which floors bury them in dead calls. When you recover conversations, you are also handing your best people more of the work they are good at, which is the cheapest retention program anyone has ever proposed.

Running it honestly on your floor

The number this article produces is only as good as its inputs, so here is how to gather them without fooling yourself.

Revenue per sale: take trailing 90 days gross revenue divided by closed deals. Include the small deals. Using only your flagship product's ticket size inflates the result.

Close rate: conversations to sales, not dials to sales. Most dialer reports give you both; the conversations-based figure is the honest one for this formula. If your "conversation" definition includes voicemails your agents handled, strip those out first, or your close rate is silently diluted.

Productive hours: pull actual dialing hours from your dialer, not scheduled shifts. The gap is usually 15-25% and always disappoints people the first time they measure it.

Then run the formula twice. Once with your real numbers, once with every input degraded by a third. If the degraded version still clears what you would spend to get there, the decision is made. This is the same discipline I described in cost per number as a life metric: measure at the level where the decision actually lives.

The mistake to avoid

The trap with this calculation is treating the output as found money. It is not, entirely. Recovered conversations consume agent talk time you were previously spending on misrouted voicemails and false starts, which is exactly the swap you want, but your floor does need the capacity to handle the extra volume. On a floor with idle agent time, which describes most outbound floors between peaks, recovered answers absorb cleanly. On a floor running hot, pair the detection change with the headcount conversation from earlier, and note that the added seats now perform better too, because they inherit cleaner routing.

What the fix costs to try

I keep this section short because it should be. Fixing detection is not a migration project. It is one command run by your dialer admin, about 5 minutes, no carrier or hardware change, and agent routing stays exactly as it is. Verdicts start at 125 milliseconds. Every call is logged, so you can watch recovered-answer volume appear in your own export rather than trusting anyone's dashboard, mine included.

The free tier is 50,000 detections a month with no card: start here. On a 15-seat floor that is a meaningful trial window, and on larger floors it is at least proof of the install claim. There is a longer treatment of the mechanics in AMD latency versus accuracy, and if compliance is what finally gets budget signed, the FTC caps abandonment at 3% of live answers per campaign over 30 days (16 CFR 310.4), and dropped-live-humans count against you, a angle I cover in AMD logs as a compliance defense.

For the reader who wants the version of this math with a calculator attached, the ROI page and the writeup on which detection errors cost what do exactly that.

What the number is not

Some honesty about the limits of this calculation, because a number this size attracts misuse.

It is not a forecast. It is the gross annual value of an increment at stated assumptions, before the operational work of absorbing the volume. Treat it the way you treat a pipeline number: real enough to justify effort, not real enough to book.

It is not automatic. The value shows up only if recovered conversations reach agents who can convert them. On a floor with idle capacity between dials, which is the normal state, that condition is already met. On a floor running hot, the increment partially converts into a staffing conversation, and even then the added seats perform better than they would have on the old detection, so the formula overstates nothing, it just splits the benefit.

And it is not the only reason to fix detection. The same misclassification that drops live humans also misroutes machine recordings to agents, burning 15-30 seconds of agent time each, which is a payroll leak in its own right. Compliance exposure from dropped live answers is a third reason entirely. The value of one extra conversation per agent-hour is the headline number, but it rides on top of the payroll and compliance fixes, not instead of them.

One line, one decision

Annual value = agents × 1 × productive hours × close rate × revenue per sale. Run it before your next planning meeting, and notice which line item it dwarfs.

The question worth sitting with: how many conversations did your dialer throw away today, already answered by a live person, while you were reading this?