Answer Seizure Ratio is the percentage of outbound calls that result in a successful connection. It sounds simple. In practice, it's the single most important performance metric in high-volume outbound voice — and most operations are losing on it without understanding why.
The industry average for outbound answer rates sits between 50 and 60 percent. We consistently deliver above 85 percent on the same traffic. That gap doesn't come from luck. It comes from where you measure, what you can see, and how your voice infrastructure is built.
How ASR Is Calculated
An "answered" call in the SIP context means the network returned a 200 OK — the call connected at the carrier layer. This is different from a human answering. A 200 OK can be returned by a voicemail system, an IVR, or a live agent. It confirms the session established. It does not confirm a productive conversation happened.
This distinction matters. A dialer optimizing for human-answered calls needs to go one layer deeper than raw ASR — but ASR is still the foundational metric, because if the call never establishes, nothing else matters.
Why ASR Degrades — and Where Most Operations Lose
There are several layers where calls die before they ever reach a consumer.
The first is number reputation. Carrier analytics engines — Hiya, First Orion, and TNS — evaluate outbound numbers in real time. A number labeled Spam Likely or blocked by a carrier may be terminated silently before it rings. The 487 SIP response code is the signal that this happened. Most dialers don't surface it clearly. Most operations have no idea how many calls are dying at this layer.
The second is STIR/SHAKEN attestation. Calls that can't achieve A-level attestation face elevated termination rates at downstream carriers, particularly wireless. This is increasingly consequential as carrier enforcement tightens.
The third is routing quality. Not all carrier paths are equal. Some wholesale routes are cheaper and worse — higher latency, more post-dial delay, higher failure rates on specific NPA-NXXs. If your voice network isn't monitoring carrier performance at this level, you may be routing traffic through paths that are quietly degrading your answer rates.
The fourth is call velocity. Dialers pushing high calls-per-second rates on a number pool that hasn't been rotated will accelerate flagging. The numbers burn fast, and ASR craters.
Each of these layers is measurable. Most operations only see the aggregate result — their answer rate — without knowing which layer is causing the problem.
The Gap Between 50% and 85%
The difference between a 50 percent and an 85 percent connected rate on a high-volume outbound operation is not a minor optimization. At scale, it changes unit economics entirely.
If you're running 100,000 dials per day at a 50 percent answer rate, you're connecting on 50,000 calls. The same 100,000 dials at 85 percent connects on 85,000 calls — a 70 percent increase in productive conversations without a single additional dial.
That improvement flows directly to revenue, cost per contact, and agent utilization. It also means you need fewer dials to hit the same production targets, which reduces carrier spend.
We achieve 85 percent not by doing one thing differently, but by having visibility across every layer where calls fail and addressing each one. Early Media Analysis identifies calls being killed at the carrier layer before they ring. Number Reputation Management monitors how number pools are being scored by the major analytics engines in real time. Carrier-level routing intelligence ensures traffic moves on the paths that perform. These systems work together.
What to Do If Your ASR Is Below 70 Percent
Start by asking whether you have visibility into your 487 rate. That alone will tell you whether number reputation is a factor. If you have no answer, your voice infrastructure isn't giving you the data you need.
Next, look at your STIR/SHAKEN attestation rates by carrier. A-level attestation is not automatic. It depends on how your number inventory is provisioned and how your carrier is handling the attestation chain. Gaps here are fixable, but only if you can see them.
Third, examine your number rotation strategy. How frequently are pools cycling? Are numbers being rested or retired based on carrier signal data, or on time-based schedules? Time-based rotation is a guess. Carrier-signal-based rotation is precision.
An ASR below 70 percent on a healthy outbound operation is almost always a data problem before it's a strategy problem. The calls are failing at the network layer. You need to see what's happening there before you can fix it.
The Bottom Line
Answer Seizure Ratio is how outbound voice performance gets measured. But the carriers and analytics engines that determine whether your calls succeed don't operate inside your dialer. They operate in the network layer your dialer can't see.
Getting to 85 percent means bridging that gap — between what your dialer knows and what the carrier network is doing.
