I spent three hours last Tuesday trying to salvage a recording where my guest decided to take the interview while walking through a busy train station. The audio was a disaster of wind noise and digital clipping, and no amount of expensive compression could save it. Most “gurus” will tell you that if you just buy the right $500 plugin, you can fix anything, but that is a lie. If you want to learn how to record a phone call for a podcast that doesn’t sound like it was captured through a tin can in a wind tunnel, you have to stop looking at software and start looking at signal paths.
I’m not here to sell you a masterclass or a subscription to some shiny new platform. I’m going to tell you the actual, unglamorous mechanics of what works—from why you should never, ever use a standard cellular line when you can avoid it, to the specific settings that keep your levels from peaking. This is about the practical reality of remote recording, focusing on the technical hurdles that actually break a production before you even get to the editing stage.
Avoiding Phone Call Audio Compression and Digital Grit
The biggest mistake I see people making is assuming that a clear connection equals a clear recording. You can have five bars of signal, but if you are recording the actual cellular stream, you are fighting a losing battle against avoiding phone call audio compression. Cellular networks are designed to prioritize the intelligibility of speech by aggressively stripping away frequencies and compressing the dynamic range. This results in that hollow, “underwater” sound that makes your listeners want to turn the volume up just to hear the words, only to get blasted by a sudden peak.
If you want to do this properly, stop trying to record the call directly through your computer’s line-in. Instead, look into recording local audio vs cellular audio as two separate tracks. The gold standard is to have your guest record their voice locally on their own device—using a decent handheld recorder or even a voice memo app on a phone placed on a soft surface—while you record the call stream separately. This way, when the cellular signal inevitably glitches or drops a packet, you have a clean, uncompressed master file to fall back on during the edit.
Choosing High Quality Audio Recording Software Over Basic Lines
If you’re relying on a standard FaceTime call or a basic WhatsApp voice note, you aren’t really recording a podcast; you’re recording a conversation that happens to be captured. The problem is that these platforms are designed for low-latency communication, not fidelity. They aggressively strip away frequencies to make sure the voice stays intelligible even on a weak signal, which is exactly how you end up with that tinny, hollow sound. To avoid this, you need to move toward high quality audio recording software that uses a “double-ender” method. This means the software records a high-resolution stream from your guest’s microphone directly to a local drive on their machine, rather than just pulling the compressed stream through the internet connection.
When you’re building a proper remote podcast interview setup, look for tools like Riverside or Zencastr. These aren’t just fancy interfaces; they are designed specifically for the task of recording local audio vs cellular audio. By capturing the audio locally on both ends and then uploading it to the cloud, you bypass the jitter and packet loss that make a standard phone call sound like it’s being transmitted from a submarine. It’s more work to manage the files, but it’s the difference between a professional production and a clip you’ll be embarrassed to release.
Five ways to stop your remote recordings from sounding like a walkie-talkie conversation
- Tell your guest to use headphones. I cannot stress this enough. If they play your voice through their phone speakers while they are on the call, your microphone is going to pick up your own voice leaking back into their end. You’ll end up with a hollow, echoing mess that no amount of EQ can fix in post.
- Forget the built-in phone mic. If they are using a smartphone, ask them to use a wired headset with a decent inline mic, or better yet, a dedicated USB mic plugged into a laptop. The “handheld phone to the ear” method is a recipe for handling noise and that thin, tinny frequency response that makes listeners want to turn off.
- Check the signal strength before you hit record. If your guest is sitting in a “dead zone” or on a train with fluctuating 4G, you’re going to get digital artifacts—those nasty, chirping sounds that happen when the data stream drops packets. If the connection looks shaky, stop the interview, troubleshoot, and restart. It’s better to lose ten minutes of time than ten hours of editing.
- Record locally if you can. If you are using a platform like Riverside or Zencastr, you’re already ahead of the game because they record the audio on the guest’s device and upload it later. If you are stuck using a standard phone call, ask the guest to open the “Voice Memos” app on their phone and record a separate track simultaneously. You can sync those two files in your DAW later, and you’ll have a much cleaner file to work with than the compressed stream.
- Watch the room, not just the tech. I’ve had guests with $500 microphones who recorded in a kitchen with all the hard surfaces exposed. The reverb will kill your ability to compress the audio later without it sounding “pumped” and unnatural. Tell them to find a room with rugs, curtains, or even a walk-in closet. Soft surfaces are your best friend when you can’t control the environment.
The Bottom Line
Stop relying on the cellular network; if you aren’t using a local recording setup (like Riverside or Zencastr) to capture high-bitrate audio on both ends, you’re just editing a compressed mess.
The environment matters more than the gear; tell your guest to move away from windows and hard surfaces, because no amount of EQ can fix the sound of a person talking in a kitchen.
Always record a 30-second “safety” clip at the start of the call to check levels; it’s better to catch a clipping mic or a silent connection in the first minute than to realize you’ve lost an hour of interview during the edit.
The Myth of the "Good Enough" Connection
You can spend three grand on a Shure SM7B, but if you’re trying to salvage a guest who is insisting on using their built-in laptop mic over a shaky Zoom connection, you aren’t producing a podcast; you’re performing digital archaeology. Stop trying to fix bad air in post and start demanding a decent headset before you even hit record.
Nadine Okafor
Don't Let the Tech Get in the Way of the Story
At the end of the day, recording a remote guest over a phone line is a battle against physics and compression. You can’t undo a bad signal once it’s baked into the file, so you have to be proactive. That means moving away from standard cellular calls, ditching the built-in laptop mics, and using software that captures local audio rather than just the stream. If you manage to get a decent signal and a quiet room, you’ve already cleared the biggest hurdle. It’s about mitigating the inevitable through better tools and smarter workflows so that when you sit down to edit, you aren’t spending five hours trying to fix a digital mess that should have been avoided in the first place.
I know it feels like a lot of technical overhead for something that’s supposed to be a simple conversation, but that’s the reality of the craft. Most people quit because they get frustrated with the friction of production, but the ones who actually build a listener base are the ones who master the unglamorous parts. Don’t let a tinny, compressed audio file be the reason a great interview goes unheard. Get the settings right, respect the signal path, and then get out of the way so the story can actually breathe.
