Amazon Connect echo is one of the most common audio complaints in a contact center. Someone on the call hears their own voice coming back a moment later, and the conversation falls apart. The good news: echo almost always has a simple, physical cause. This guide shows you how to find which side is causing it and how to fix it, step by step.
Amazon Connect Echo: Quick Fix
Try these five things first. They fix most echo cases in minutes.
- Use a wired headset. Not laptop speakers, not a speakerphone, and not Bluetooth if you can avoid it.
- Use the same device for microphone and speaker. Don’t take the mic from the headset and the sound from the laptop.
- Lower the headset speaker volume and move the mic just below the chin.
- Close other tabs or apps using the mic (Teams, Zoom, a second CCP tab).
- Test in an incognito window with extensions turned off. Reset any WebRTC settings in
chrome://flagsto Default.
First: Who Hears the Echo?
This is the most important question. Echo is created at the other end of the call from the person who hears it. A microphone picks up sound from a speaker and sends it back.
| Who hears it | Where the echo is created | Most likely cause |
|---|---|---|
| Customer hears their own voice | Agent side | Agent’s mic picks up the customer’s voice from the agent’s speakers or a leaky headset |
| Agent hears their own voice | Customer side or phone network | Customer on speakerphone, car hands-free, or a cheap phone; sometimes a carrier or forwarding leg |
| Both hear echo, only on some calls | A specific call leg | Transfers, conferences, external quick connects, or calls forwarded from another system |
| Everyone at one site hears it after a date | Shared change | Browser or OS update, new headset model, new audio software pushed to machines |
AWS describes echo as the agent hearing their own voice back with a delay, caused by feedback between a microphone and a speaker. The fix is always to break that feedback loop at the side that creates it.
How to Prove Where the Echo Comes From
Don’t guess. Use these checks before you change anything.
1. Listen to the call recording
Amazon Connect records calls inside the service, so the recording is the dividing line between the agent side and the customer side. In the recording, the customer audio is on the left channel and the agent audio is on the right channel.
- Customer’s voice repeats on the right (agent) channel → the agent’s mic is picking up the speaker. Fix the agent side.
- Agent’s voice repeats on the left (customer) channel → the echo comes from the customer’s device or the phone network.
- Recording sounds clean but someone heard echo → the problem is after Connect, on the listener’s own device or network.
For multi-party and conference calls, check each leg (each contact ID) separately.
2. Check the contact record
Run this in AWS CloudShell, replacing the two IDs with your own instance ID and contact ID:
aws connect describe-contact --instance-id YOUR-INSTANCE-ID --contact-id YOUR-CONTACT-ID --query "Contact.QualityMetrics"
Look at QualityScore (1 = poor, 5 = excellent) and PotentialQualityIssues. Important: AWS only flags HighPacketLoss, HighJitterBuffer and HighRoundTripTime. There is no “echo” flag, so an empty list does not rule out echo. It does tell you whether network delay is making the echo worse.
3. Download the CCP logs
CCP logs only exist in the current browser session, so download them right after the bad call. Open them in the AWS CCP Log Parser and check jitter buffer and round-trip time. See our guide: How to Download and Read Amazon Connect CCP Logs.
4. Check the network numbers
| Metric | Healthy | Problem |
|---|---|---|
| Round-trip time (RTT) | Under 300 ms | Over 300 ms |
| Jitter buffer | Under 30 ms | Over 30 ms |
| One-way delay (end to end) | Under 150 ms | Over 150 ms |
| Packet loss to instance (CloudWatch) | Near 0% | Over 20% is severe |
Delay doesn’t create echo, but it makes existing echo much more noticeable. A small echo at 50 ms sounds like a “hollow” voice. The same echo at 400 ms sounds like talking to yourself.
Causes of Amazon Connect Echo and How to Fix Each One
Cause 1: Speakers or a leaky headset at the agent side
| Symptom | Check | Fix |
|---|---|---|
| Customer hears echo; agent uses laptop speakers | Sound output in CCP settings and in the OS | Switch to a headset. Never use built-in speakers for calls. |
| Echo only with one headset model | Test with a different headset | Use a wired, contact-center headset. Cheap headsets leak sound from the ear cup into the mic. |
| Echo when volume is high | Headset volume level | Lower the speaker volume and position the mic just below the chin. |
| Echo with a USB hub or adapter | How the headset is connected | Plug the headset directly into the computer. Update headset firmware. |
Cause 2: Mic and speaker on different devices
The browser’s built-in echo cancellation compares what is playing on the speaker with what the microphone hears, then removes the match. If the mic is the headset but the sound plays on the laptop or a monitor, the browser may watch the wrong output and fail to cancel the echo.
- In the CCP settings, pick the same headset for both microphone and speaker.
- Check the Windows or macOS default device matches, too.
- Set the microphone sample rate to 48 kHz in the OS sound settings. Mismatched sample rates can cause humming and audio artefacts.
Cause 3: Browser settings, extensions and other apps
| Symptom | Check | Fix |
|---|---|---|
| Echo started after a browser update | Browser version in the contact record (DeviceInfo) |
Test another supported browser; roll back if needed. |
| Echo only in one browser profile | Test in incognito with extensions off | Turn extensions back on one at a time to find the culprit. |
| Someone changed WebRTC flags | chrome://flags or about:config |
Reset WebRTC settings to Default. |
| Echo while Teams or Zoom is open | Other apps using the mic | Close other calling apps and extra CCP tabs. Only one CCP per agent. |
| Custom CCP or CRM-embedded softphone | Test the default CCP | If the default CCP is clean, check your custom code for disabled audio processing. |
Cause 4: Bluetooth and wireless headsets
AWS notes that wireless headsets can add delay and lower quality because of radio interference and transcoding. Extra delay makes any echo louder to the listener. If echo appears only on wireless, test the same agent with a wired headset before you change anything else.
Cause 5: VDI (Citrix, Amazon WorkSpaces, Omnissa, AVD)
In VDI without audio optimization, sound travels from the headset to the virtual desktop and back, which adds delay and processing.
- Turn on Amazon Connect audio optimization (WebRTC redirection) using the
VDIPlatformsetting, so media goes straight from the agent’s local device to Connect. - Keep the same headset for the whole call. In VDI, the media device is set when the contact starts.
- Don’t combine Audio Enhancement with VDI audio optimization. AWS says the two are not supported together, and having both configured is a likely cause of audio problems.
Full VDI steps: Amazon Connect VDI Audio Quality Fix for Citrix & WorkSpaces.
Cause 6: Customer device or phone network
If the agent hears themselves, the agent’s setup is usually fine. You cannot fix the customer’s phone, but you can confirm it:
- Ask the customer whether they are on speakerphone or car hands-free, and ask them to switch to the handset.
- Check whether echo follows one carrier, one phone number, or one country.
- If calls are forwarded into Connect from another system, test a direct dial. If the direct dial is clean, the forwarding leg is the problem.
- On transfers and conferences, check each leg’s recording. External parties on speakerphone often add echo for everyone.
Cause 7: Room acoustics
Large, empty rooms with hard walls bounce sound back into open microphones. AWS recommends covering hard surfaces and adding barriers between desks. This matters most for agents working from home in empty rooms.
Does Amazon Connect Audio Enhancement Fix Echo?
Not directly. Audio Enhancement (launched February 2026) has two modes: Noise Suppression removes background noise, and Voice Isolation also removes background speech. Voice Isolation needs a wired headset. Both need at least a 4-core CPU (4 vCPUs on a virtual machine).
It’s built to clean noise from the agent’s mic, not to cancel echo. If echo started right after you enabled it, turn it off for one agent and test. That is one of the first checks AWS recommends.
Prevent Echo at Scale
- Standardize headsets. One approved wired model, tested with Connect.
- Lock audio settings. Same device for mic and speaker, 48 kHz, default WebRTC flags.
- Pre-shift check. Agents run the Agent Workstation Connectivity Validator or the AWS Endpoint Test Utility before logging in.
- Control updates. Pilot browser and OS updates on a small group first.
- Track it. Ask agents to note the contact ID whenever echo happens, so you can check the recording and logs within 24 hours.
What to Send AWS Support
If the echo continues after these fixes, open a case with:
- Instance ARN and 3–5 contact IDs (less than 24 hours old) with UTC times
- Who hears the echo (agent, customer or both)
- Call recordings and CCP logs
- Endpoint Test Utility results, headset model, browser, VDI and VPN details, and Audio Enhancement setting
FAQ
Why does the customer hear an echo on Amazon Connect calls?
Usually because the agent’s microphone picks up the customer’s voice from the agent’s speakers or a leaky headset. Switch the agent to a wired headset, using the same device for mic and speaker.
Why does the agent hear their own voice?
The echo is created at the customer end, often by speakerphone or car hands-free, or by a forwarded call leg. Check the left channel of the recording to confirm.
Can network problems cause echo?
Network delay doesn’t create echo, but it makes existing echo much louder and more annoying. Keep round-trip time under 300 ms and jitter under 30 ms.
Does the contact record show echo?
No. QualityMetrics only flags packet loss, jitter and round-trip time. Use the stereo call recording to find echo.
Do I need special software to stop echo?
Usually not. Modern browsers already include echo cancellation. Most fixes are a better headset, matching audio devices, and clean browser settings.