People may sound robotic, video may freeze, screen sharing may lag, or the call may reconnect or drop. Others may report that your audio cuts out even though you hear them. These symptoms often involve delay, congestion, packet loss, weak Wi-Fi, or an overloaded device, but one meeting service or headset can also be the cause.
Identify who is affected. Ask whether everyone has trouble or only you. If only one participant is unclear, the issue may be at that participant's location. Note the time and whether audio, video, screen sharing, or all three were affected.
Reduce demand without ending important work. Stop nonessential downloads, cloud sync transfers, streaming, and large uploads on your device. Ask household members to pause heavy personal traffic if appropriate. Do not close security, backup, or management software installed by your organization.
Improve the connection path. Move closer to the approved Wi-Fi access point or use your normal approved Ethernet connection. Stay in a fixed location rather than walking between coverage areas. Do not move cables at a switch, router, firewall, wall cabinet, or access point.
Turn off outgoing video temporarily. Audio usually needs less capacity than video. If the call stabilizes, leave your camera off and tell the organizer. You can also stop a screen share that is no longer needed. Do not lower organization-wide meeting policies or change advanced service settings.
Check the meeting app. Confirm that the correct microphone, speaker, and camera are selected. Close and reopen the app after the meeting, then install its normal update if company policy permits. Avoid downloading meeting clients from advertisements or unofficial links.
Use built-in quality information. In Teams, open the call health information if available and record what it shows. In Zoom, note any unstable connection warning and use the app's audio or video settings test. Do not post screenshots that show participant names, meeting IDs, chat, or confidential shared content.
Compare one approved alternative. If practical, join an approved test meeting or make a short test call. If multiple meeting platforms fail on the same connection, the network or device is more likely involved. If only one service fails, check its official service status or ask support. Do not use an unauthorized personal meeting account for confidential business.
Restart at a safe time. After saving work and leaving the meeting, restart the computer once. If possible, test at a different time and record whether the problem is tied to a location, time of day, or specific meeting. Do not reboot shared network equipment.
Do not factory reset a router, firewall, access point, switch, managed device, or phone. Do not change DNS, static IPs, VLANs, firewall rules, Quality of Service settings, proxy settings, certificates, or managed network profiles unless Zerolimit directs you. Do not disable endpoint protection, the company VPN, or traffic inspection to improve a call.
Use only the meeting link supplied through the expected calendar invitation or business channel. Never give remote control to an unexpected participant. Treat requests to install a codec, certificate, browser extension, or network optimizer as suspicious. Do not share meeting passwords, MFA codes, or confidential recordings in a ticket.
Contact Zerolimit when calls fail repeatedly, multiple users or services are affected, wired and wireless tests both fail, or the app shows persistent connection warnings. Include device and operating system, app and version, connection type, location, date and exact time with time zone, meeting platform, whether others were affected, what froze or dropped, and safe call health values if visible. Provide the meeting ID only if support specifically needs it and the ticket is appropriately restricted. Never include Wi-Fi passwords, VPN secrets, MFA codes, meeting passwords, or confidential records.