How to Review ASR and ACD in Outbound Voice Traffic
An ASR or ACD change is useful when it leads to a specific question about your calls. Start with the traffic behind the number, identify a pattern and test one explanation at a time. This workflow helps outbound teams and resellers make decisions from evidence.
Table of contents [Show]
Build a baseline you can compare
Use the same reporting window, timezone and counting method. Keep destinations and traffic profiles separate. Include the number of attempts, answered calls, total answered duration and corresponding charges.
ASR is the answered share of the counted attempts; ACD is the average duration of answered calls. Keep the underlying counts beside both metrics. A small sample can move sharply after only a few calls, while a larger total can hide a problem in one destination.
Inspect the calls behind a change
If ASR falls, check which outcomes increased. Busy, unanswered and failed attempts need different investigation. If ACD changes, look at representative conversations and termination records. The call's purpose and the recipient's behavior matter alongside audio and connection stability.
Choose a few affected examples and a few successful comparisons. Record the call identifier, timestamp with timezone, destination, device and observed behavior. This is a more useful support case than an account-wide percentage on its own.
Check the originating setup
- Confirm the destination format used by the application.
- Verify that the configured route matches the intended test.
- Check the device, headset and local network when symptoms affect one workstation.
- Compare call-attempt bursts with the capacity agreed for the setup.
- Review the caller identity where caller-ID presentation is part of the workflow.
Use identities you are authorized to present. Keep the test configuration consistent so the next comparison answers a clear question.
Test a route decision on representative traffic
SIPEASY focuses on outgoing calls with CLI, nCLI and TDM route offerings. Discuss the relevant option for your destinations, expected volume and caller-ID requirements. Use a controlled sample before moving more traffic.
Compare two-way audio, call setup, call outcomes and charges under similar conditions. Record any configuration change and keep a rollback plan. A useful improvement is one your team can reproduce in its actual workflow.
Use team tools where they help the review
SIPEASY's paid PBX packages include recording, SPY and Whisper. Minimum provides three SIP devices and 1 GB of recording storage at $50/month. Standard provides five devices and 2 GB at $100/month, with BLF. Pro provides up to twenty devices and 5 GB at $250/month, with BLF and recording delivery by email or Telegram.
Try Standard for one month free. Sign in to your SIPEASY panel and activate the offer yourself using its dedicated button. Standard normally costs $100/month. Outgoing calls remain chargeable at the applicable tariff. See current packages and call rates.
Choose the package according to the people, devices and recording workflow involved. Keep supervision and recording access aligned with the responsibilities of the team.
End the review with an action and a check date
Write down what changed, what evidence supports the explanation and what will be measured next. Repeat the same comparison after the change. Preserve results that did not improve as well as those that did; both help refine the next decision.
Registration and outbound route access are KYC-free. Contact SIPEASY with your traffic brief or call examples, or create an account to prepare an outbound test.
For metric definitions, read the SIPEASY guide to ASR, ACD, PDD, NER and MOS.