Is your connection good enough for a softphone?
A browser speed test answers "how fast", but for voice calls the questions that matter are latency, jitter and packet loss. A home agent on a 300 Mbps connection can still have choppy Amazon Connect calls if the Wi-Fi is congested or a VPN adds 150 ms. Here is how to read the result for contact centre work.
What each number means
- Download and upload: a voice call uses very little bandwidth. The Opus codec used by the Amazon Connect softphone needs roughly 100 kbps in each direction. Bandwidth only matters when the same line is also streaming video, syncing files or running a VDI session.
- Ping (latency): the round-trip time to the test server. Below about 150 ms one-way, conversations feel natural. Above that, people start talking over each other.
- Jitter: how much latency varies between packets. Jitter buffers smooth out small variation, but sustained jitter above about 30 ms causes robotic or clipped audio.
- Packet loss: even 1–2% loss is audible on voice. It is the most common cause of "words dropping out".
How to test properly
- Test from the agent's actual setup: the same device, browser, Wi-Fi or cable, and VPN state they use on shift.
- Run it three times, including once at a busy time of day. A single good result in the morning proves little.
- Close streaming, cloud backup and large downloads first, or test with them running to see the worst case.
- If the results are poor on Wi-Fi, test again on a cable. If cable fixes it, the problem is the wireless setup, not the provider.
Rough readiness guide for home agents
- Good: latency under 100 ms, jitter under 20 ms, no packet loss, and at least 5 Mbps upload left over after other household use.
- Usable with care: latency 100–200 ms or occasional jitter spikes. Use a wired connection and avoid heavy use of the line during shifts.
- Not ready: repeated packet loss, jitter consistently above 30 ms, or latency above 250 ms. Fix this before the agent takes live calls.
These are working rules of thumb rather than AWS requirements. For the official network requirements, see the AWS reference below.
A speed test doesn't test the path to AWS
This test measures the connection to a public test server. Amazon Connect media travels to the AWS region that hosts your instance, often over different routes, and firewalls or proxies may block the ports it needs. For a real readiness check, use the Agent Workstation Validator, which tests the CCP endpoints and media path. If agents work through Citrix, WorkSpaces or another virtual desktop, also run the VDI Compatibility Tester, and use the Allowlist Auditor to give your network team the exact domains to allow.
Common causes of poor call quality
- Wi-Fi interference: distance from the router, thick walls and the crowded 2.4 GHz band. Move closer, switch to 5 GHz or use a cable.
- VPN routing: a full-tunnel VPN sends voice to a corporate office before it reaches AWS. Ask whether split tunnelling for Connect is allowed.
- Bufferbloat: latency shoots up when someone else on the line uploads. A router with SQM or QoS settings fixes this.
- Browser and device: an old laptop running at 100% CPU drops audio regardless of the network. The CCP Log Parser shows whether the softphone reported problems.