Echo, Robot Voice and Cutting Out on Video Calls: How to Find the Real Cause
A video meeting starts normally.
Then somebody says:
“You're echoing.”
A few minutes later another person sounds robotic.
Words disappear from sentences. The picture freezes. People start talking over each other because the delay makes it impossible to tell who has finished speaking.
These problems can sound similar, but they often point to completely different causes.
A useful starting point is:
Echo → usually audio feedback
Robot voice → usually network instability or audio-processing trouble
Cutting out → usually network loss, microphone processing or device problems
Delay → usually latency
The fastest fix is not reinstalling Teams or restarting everything.
It is identifying which layer is actually failing.
First: Ask What Other People Hear
The person with the problem may not hear it themselves.
Ask another participant to describe the symptom precisely.
“I can hear my own voice coming back”
That is classic echo.
Start with:
speakers
microphone
multiple devices in the room
“You sound robotic or underwater”
That strongly suggests:
packet loss
jitter
unstable Wi-Fi
congested network
Bluetooth/audio-device issue
high system load
Microsoft notes that choppy or robotic audio can occur when packet loss results from excessive jitter.
“Bits of your sentences disappear”
Investigate:
noise suppression
microphone gating
weak microphone level
Bluetooth
packet loss
“You disappear completely for a few seconds”
Look at:
Wi-Fi interruption
VPN
USB/headset connection
microphone selection
device power saving
“Everything sounds clear but delayed”
That points more towards latency.
The Five-Minute Test
Before changing advanced settings:
1. Confirm the correct microphone and speaker are selected.
2. Disconnect unnecessary headsets, webcams and audio devices.
3. Test with a wired USB headset if available.
4. Close heavy applications.
5. Move closer to the Wi-Fi access point—or preferably test using Ethernet.
6. Disconnect VPN temporarily where business policy permits.
7. Test the same call from another device.
Change one variable at a time.
Otherwise, if the problem disappears, you won't know what fixed it.
Fixing Echo
Echo usually occurs when meeting audio leaves the speakers and is picked up again by a microphone.
The conference platform tries to cancel this automatically.
It becomes harder when:
speakers are loud
microphone is close to the speakers
several laptops are in the same room
hard surfaces reflect sound
separate speakers and microphones are used
Use a Headset
This is usually the quickest fix.
A headset prevents the meeting audio being projected across the room and picked up again by the microphone.
For regular business calls, a good:
wired USB headset
certified wireless headset
directional boom microphone
is generally much more predictable than laptop speakers and a distant microphone array.
Only One Device Should Handle Room Audio
Two laptops join the same meeting in one office.
Both have:
microphone on + speakers on
You now have an excellent recipe for echo.
On secondary devices:
mute the microphone
mute the speakers
choose Do not connect to audio where available
unless you are using a properly configured meeting-room system.
Check Which Microphone Is Actually Selected
You may think you are using:
Headset Microphone
while Teams is actually using:
Laptop Microphone Array
or:
Webcam Microphone
Open the meeting application's audio settings and verify the selected input and output.
This simple mistake causes a surprising number of echo problems.
Robot Voice: Check the Network
Robotic, metallic or warbling speech is commonly associated with network delivery problems.
Voice is transmitted as a stream of packets.
If too many arrive:
late
out of order
not at all
the conferencing application has to conceal or reconstruct the missing audio.
That produces the characteristic robotic sound. Microsoft's current guidance explicitly links robotic and choppy audio with packet loss.
Test With Ethernet
This is one of the best isolation tests.
Connect the laptop to the business network using Ethernet.
Turn Wi-Fi off temporarily.
Audio becomes clear
Investigate:
Wi-Fi coverage
interference
access-point placement
channel congestion
wireless adapter
distance from AP
Audio remains robotic
Now investigate:
internet connection
firewall/router
VPN
endpoint device
conferencing service
Don't continue blaming the microphone when the same microphone works perfectly over Ethernet.
Check Teams Call Health
Microsoft Teams can display real-time meeting quality information.
During a call, open:
More > Settings > Call health
Microsoft says Call Health can show live information about:
network
audio
video
screen sharing.
This is much more useful than saying:
“Teams sounds bad.”
Look for evidence involving:
packet loss
jitter
round-trip latency
For business support teams, Microsoft also provides Call Analytics for investigating individual users' poor call quality centrally. Microsoft's documentation was updated in March 2026.
Packet Loss vs Jitter vs Latency
These terms are worth understanding.
Packet loss
Some packets never arrive.
Result:
missing syllables
broken audio
frozen video
Jitter
Packets arrive at inconsistent intervals.
Result:
robotic voice
warbling
uneven audio
Latency
Packets take too long to reach the other person.
Result:
awkward pauses
people talking over one another
A connection can have a very fast headline download speed and still perform badly in a call if packet delivery is unstable.
Check What Else Is Using the Network
A connection may be perfectly capable of running a video call until another activity saturates it.
Check for:
cloud backup
OneDrive synchronisation
large uploads
Windows updates
file transfers
CCTV uploads
other video meetings
Upload bandwidth is particularly important.
Someone uploading a large backup can damage call quality even when web browsing still feels reasonably fast.
For businesses, this is where network monitoring and QoS can become more useful than simply purchasing a faster headline broadband package.
VPN Can Make a Difference
A VPN may route your meeting traffic through:
another office
security gateway
cloud filtering service
That adds another network path.
As a controlled test, where business policy permits:
VPN connected → test
then:
VPN disconnected → test
If the problem disappears without the VPN, investigate:
VPN gateway
route design
client
security inspection
capacity
Do not simply leave a required corporate VPN disabled permanently.
Find the bottleneck.
Cutting Out at the Start or End of Sentences
This is often different from ordinary packet loss.
If the first or final word repeatedly disappears, investigate audio processing.
Possible causes include:
aggressive noise suppression
microphone gating
very low microphone volume
microphone too far away
third-party noise-cancellation software
Your PC may have several processing layers at once:
Teams/Zoom noise suppression
Windows audio enhancements
headset software
manufacturer audio software
third-party AI noise cancellation
Those layers can fight each other.
Temporarily disable one processing layer at a time and retest.
Windows Audio Enhancements Can Cause Distortion
If the audio is distorted even outside Teams or Zoom, investigate Windows itself.
Go to:
Settings > System > Sound
Select the relevant device.
Temporarily turn:
Audio enhancements
off.
Microsoft specifically recommends disabling audio enhancements when troubleshooting distorted or crackling Windows audio.
If the problem occurs in:
Teams
YouTube
local music
Windows notification sounds
then a conferencing-service network fault becomes much less likely.
Bluetooth Can Reduce Call Audio Quality
Bluetooth headsets can operate differently during calls because the microphone and speaker need to work simultaneously.
If:
music sounds excellent
but:
calls sound noticeably worse
that may reflect the Bluetooth audio mode being used rather than a fault.
As a diagnostic test:
use a wired USB headset
use the headset's dedicated USB dongle if supplied
test the laptop microphone/speakers
If wired audio is perfect, the Bluetooth path deserves investigation.
For important business calls, a dedicated USB headset or certified wireless headset is generally easier to troubleshoot.
Check CPU Usage
Network problems aren't the only cause of robotic audio.
Open:
Task Manager
and check:
CPU
Memory
Disk
If CPU is constantly:
95–100%
the conferencing application may struggle to process:
audio
video
background effects
screen sharing
Possible heavy workloads include:
virtual machines
video rendering
large spreadsheets
browser tabs
software builds
AI workloads
Close unnecessary applications.
Also temporarily disable:
background blur
animated backgrounds
unnecessary video
and test again.
Test the Microphone Outside the Meeting App
This separates hardware from network issues.
Use:
Settings > System > Sound > Input
or Windows Sound Recorder.
Record yourself speaking.
Recording sounds perfect
The microphone itself is probably functioning.
Investigate:
conferencing application
network
processing
VPN
Recording cuts out or distorts
The issue exists before the audio even reaches Teams or Zoom.
Investigate:
microphone
USB/Bluetooth
driver
Windows audio
If Only One Application Is Affected
Suppose:
Teams sounds terrible
but:
Zoom works perfectly
with the same:
headset
PC
Wi-Fi
room
That makes Teams configuration or installation more interesting.
Likewise, if Teams works perfectly and only Zoom fails, don't spend hours replacing the office Wi-Fi.
Compare using the same device and same connection.
If Everyone in the Office Has Problems
Now think beyond one laptop.
If multiple users simultaneously report:
robot voice
call drops
frozen video
investigate shared infrastructure:
broadband
firewall
switch
wireless access points
VPN
network saturation
Ten headsets rarely fail simultaneously.
Look for the common dependency.
The Quick Symptom Guide
Symptom Start here
Echo Speakers, microphone, multiple room devices
Robot voice Packet loss, jitter, Wi-Fi
Audio cuts in/out Network, microphone processing, headset
Words clipped Noise suppression/gating
Long delay Latency
Distortion everywhere Windows/audio device
Only one meeting app affected Application settings/client
Entire office affected Shared network/ISP/firewall
The Best Troubleshooting Order
For poor video-call audio:
1. Ask exactly what other people hear.
2. Verify the correct microphone and speaker.
3. Test a wired headset.
4. Test the microphone locally.
5. Check Task Manager for CPU saturation.
6. Test Ethernet instead of Wi-Fi.
7. Check Teams Call Health where applicable.
8. Test without VPN where permitted.
9. Pause known large uploads temporarily.
10. Compare another meeting application or device.
11. Investigate shared infrastructure if several users are affected.
12. Use Teams Call Analytics for recurring business issues.
The principle is:
Echo is usually acoustic. Robot voice is usually network delivery. Cutting out can be either—so isolate the layer before changing settings.
How Hamilton Group Can Help
Poor video-call quality is frustrating because the meeting application often gets blamed even when the real problem sits somewhere else.
Hamilton Group can help diagnose:
Microsoft Teams call quality
VoIP
packet loss and jitter
business Wi-Fi
broadband
VPN performance
headsets and microphones
Windows audio
docking stations
Teams Call Analytics
network monitoring
If one employee sounds robotic, we can isolate the device.
If the entire office experiences poor calls, we can investigate the shared network rather than replacing headsets one at a time.
Visit hgmssp.com or call 0330 043 0069 to discuss video conferencing, VoIP and business network support.