People rarely say “we have packet loss.” They say the other person swallowed a name, or that the last two digits of a phone number never arrived. Those gaps are often missing packets, not a bad microphone.
On a WhatsApp voice call the gap is usually a short hole in the sentence. The rest of the phrase continues as if nothing happened, which is why staff blame each other for not listening. On a desk-phone app that waits for a burst of packets before playing audio, the same loss can become a longer freeze, then a rush of words.
In our Kuala Lumpur captures, loss under one percent is often inaudible on a quiet one-to-one call. The same rate on a six-person Teams meeting, with two people on mobile data in Petaling Jaya, is enough to clip every other question. The app is doing its best to hide the holes. Hiding is not the same as arriving.
A useful field check, before anyone books us, is to ask the other person to read a list of six Malay street names, slowly. Write down what you heard. If Jalan Ampang becomes Jalan Amp- and then silence, you are not dealing with accent. You are dealing with a hole in the stream.
Packet loss also has a weather. After a heavy afternoon storm over Danau Desa we have watched previously clean calls start shedding the ends of words. The office Wi-Fi still showed “full bars.” Bars do not count packets. They count a radio handshake.
If you already record calls for training, listen for the same hole at the same second across several recordings. A hole that always lands when someone walks past the microwave, or when the upstairs neighbour starts a Zoom class, is a local contention problem. A hole that appears on every outgoing call at 11:00 is more likely the building’s link filling up.
We still need a proper capture to name the hop. The listening test only tells you the fault is real, and that it is not rudeness.