Skip to content
Dialer & Setup

Answer-Seizure Ratio Explained: The Network-Level Metric Your Dialer Dashboard Is Hiding

Most outbound teams track contact rate and conversion rate. Fewer track answer-seizure ratio (ASR) — and almost none use it diagnostically the way carrier engineers do. That gap is expensive. ASR tells you whether your problem is in the network (calls not completing) or in the behavioral layer (calls completing but not being answered). Mixing up those two failure modes leads to applying the wrong fix.

What ASR Measures and Why It Differs From Contact Rate

Answer-seizure ratio is the percentage of outbound call attempts that are seized (connected to the terminating network) and result in an answer signal — meaning either a live answer or a voicemail pickup. It is a network-layer metric.

Contact rate is the percentage of dialed attempts that result in a live human answer. It is a behavioral metric.

The relationship:

`` ASR = (calls answered, including voicemail) / (calls attempted) × 100 Contact Rate = (live human answers) / (calls attempted) × 100 ``

A team with ASR of 60% and contact rate of 14% is successfully completing calls to a ringing state 60% of the time — but humans are answering at 14%. The gap (46%) is voicemail, no-answer, and answering machine. That is a behavioral targeting problem, not a network problem.

A team with ASR of 30% and contact rate of 12% has a network problem: 70% of attempts are failing before reaching the terminating carrier at all. Carrier routing quality, trunk health, and STIR/SHAKEN attestation are the culprits.

Benchmark ASR by Call Type

ASR benchmarks vary by route type, destination geography, and trunk quality:

Route typeTypical ASR range
US domestic, tier-1 carrier55–75%
US domestic, tier-2/grey route30–55%
Canada domestic50–70%
Western Europe (DE, FR, NL)45–65%
LATAM (MX, BR)35–60%
Southeast Asia30–55%

A campaign running below the lower bound for its route type has a carrier routing problem. A campaign running within range but still producing low contact rates has a behavioral problem. Diagnosing which you have before spending on fixes is the primary value of tracking ASR separately.

What Causes Low ASR

Trunk congestion. If your SIP trunk has insufficient concurrent channel capacity, calls queue and fail at the origination side. Most teams discover this when rapid-fire dialing causes sudden ASR drops — the trunk is dropping calls before they hit the PSTN.

Carrier blacklisting. Terminating carriers block traffic from trunks associated with high complaint or spam volumes. This appears as a sudden ASR drop on specific destination prefixes (NXX codes in US) while other destinations maintain normal ASR. It is distinct from spam labeling — the call does not reach a ringing state at all.

STIR/SHAKEN attestation failures. Some terminating carriers in the US are now blocking or heavily degrading calls without STIR/SHAKEN headers. This produces ASR drops on calls to specific carriers (usually the major ones — Verizon, AT&T, T-Mobile) while other carriers continue to pass calls normally. STIR/SHAKEN compliance is the remediation path.

Route quality degradation. SIP trunk providers use least-cost routing that can shift overnight. A route that had 65% ASR last week may have 35% ASR today because the provider swapped to a lower-quality interconnect. Monitoring ASR daily rather than weekly catches these shifts early.

How to Diagnose ASR Problems Systematically

A structured diagnostic sequence:

  1. Pull ASR by destination NXX (the first six digits of US 10-digit numbers) — route-specific drops indicate carrier blacklisting or prefix-level routing problems
  2. Pull ASR by time of day — uniform drops across the day indicate trunk capacity or provider-side routing issues; peak-hour drops only indicate capacity
  3. Pull ASR by calling number — if specific caller IDs are producing low ASR while others are normal, those numbers are flagged or blocked at the terminating carrier level
  4. Compare against contact list hygiene — if the list contains high volumes of disconnected numbers, ASR will be artificially depressed by intercept responses

If ASR is within normal range and contact rate is still low, the problem is behavioral: time-of-day, local presence, or list quality, not network. Stop there and apply the correct fix.

ASR and the Economics of Your Trunk Capacity

For teams on flat-rate per-seat pricing, trunk capacity is included in the seat cost. UnlimCall's network provisions concurrent channel capacity against the seat count — you are not paying separately for channels. Under older per-channel SIP trunk models, teams frequently under-provision channels to manage cost, which creates artificial ASR ceilings: the trunk runs out of capacity before the list runs out of dials.

The traditional SIP trunking comparison covers the per-channel vs. per-seat model difference in detail. The short version: per-channel pricing means trunk capacity and dialing aggression are in constant financial tension.

Building an ASR Dashboard

Minimum viable ASR monitoring for a 10–50 agent team:

  • ASR tracked hourly (not daily) during active campaigns
  • Breakdown by destination NXX or country prefix
  • Breakdown by calling number (DID)
  • Alert threshold: any hourly ASR drop below 80% of the prior-week average triggers investigation
  • Trend graph: 14-day rolling ASR to distinguish gradual decay from acute drops

Most cloud dialers expose SIP response codes in CDR exports. Map SIP 486 (Busy), 404 (Not Found), 503 (Service Unavailable), and 603 (Decline) to ASR components — they tell you whether failures are prospect-side, network-side, or carrier-side.

Takeaways

  • ASR measures network completion rate; contact rate measures behavioral answer rate — they diagnose different failure modes
  • US domestic tier-1 ASR should be 55–75%; below the lower bound indicates a network problem, not a behavioral one
  • NXX-level ASR drops signal carrier blacklisting; time-based drops signal trunk capacity
  • STIR/SHAKEN attestation failures produce ASR drops on specific terminating carriers independently of list quality
  • Per-channel SIP trunk pricing creates financial pressure to under-provision capacity, which artificially caps ASR
  • Daily ASR tracking catches route quality changes before they become campaign-level failures

Network-Level Quality Built Into Every Seat

UnlimCall routes through tier-1 interconnects with A-level STIR/SHAKEN attestation for US/CA calls and continuous route quality monitoring. See coverage and pricing.