Decide what the guest audio is actually for
The first question is not about software. It is about what the remote voice has to do. A guest who answers three questions in a recorded interview needs something different from a panelist who trades remarks with people in the room for an hour. Write down whether the audio is going live, being recorded for later, or both, and who must hear the guest while it happens.
That answer sets how much risk you can accept. A live stream gives you one chance, so the guest connection needs a tested path and a fallback. A recording that will be edited gives you room to ask someone to repeat a line. Many teams skip this step and discover halfway through a session that the guest was never meant to be heard by the audience in the room.
Also note how long the guest will be on. A ten minute contribution can survive a mediocre headset. A ninety minute session cannot, because fatigue, battery drain and drifting connections all show up late. Put the expected duration on the checklist before anything else, since every later decision depends on it.
- Live, recorded or both
- Who must hear the guest, and when
- Expected length of the guest's contribution
Check the guest's end before the day
Most poor remote audio is decided at the guest's desk, not at your mixer. Ask where they will sit, whether the room is quiet, and what they will wear on their head or ears. A laptop microphone in a kitchen with a fridge humming gives you a voice you can never fully rescue, however well you handle your own signal.
Send the guest a short plain note: use a wired headset or earbuds with a microphone if they own one, close the door, switch off notification sounds, and plug the laptop into power. Ask for a short test call a day ahead, not ten minutes before going live. Hearing the guest once, in advance, tells you more than any description of their setup.
Keep the instructions free of jargon. Guests are often experts in their own field, not in audio, and an anxious guest sits too far from the microphone or fiddles with settings. A calm, specific request such as keep the microphone a hand's width from your mouth is easier to follow than a paragraph about gain.
- Quiet room with a door that closes
- Wired headset or earbuds if available
- Laptop on power, notifications off
- A short test call the day before
Plan the return feed so the guest can hear
A remote guest needs to hear the room, and what they hear must not contain their own voice coming back. That return feed is often forgotten. Without it the guest cannot follow the panel, talks over others, and loses confidence. Decide which mix they receive: usually the room and other speakers, without the guest's own signal.
On a field mixer this means a dedicated output or auxiliary send that leaves out the guest channel. If that is missed, the guest hears an echo of themselves a moment late, which is hard to speak through. Test it by asking the guest to say a few words and confirming they hear only the others.
Check the level of the return as well. Room microphones feeding a guest can sound distant and thin, so a speaker in the corner may be hard to follow. Where possible, give the guest a cleaner feed of the main voices rather than a general room pickup, and agree a simple way for them to signal that they cannot hear.
- Return feed without the guest's own voice
- Separate output or auxiliary send on the mixer
- Level check with the guest speaking
Settle the connection and the fallback
Connection quality varies more than anything else on the list. Ask the guest whether they are on a wired network or wireless, and whether anyone else in the building is likely to be using it heavily. If the answer is uncertain, agree a fallback in advance, such as a phone call that carries only audio, so the session continues when video drops.
Decide who makes the call to switch. During a live event the person watching the meters should not also be negotiating with the guest. Give one person that job and tell the guest who it is. A phone number written on the run sheet saves a scramble when the signal fails.
Think about what the fallback sounds like. Phone audio is narrow and obviously different from a headset, so tell the presenter in the room that the voice may change character. A listener forgives a change in tone if the host explains it in a sentence, and rarely forgives silence.
- Wired or wireless network at the guest's end
- Phone audio as an agreed fallback
- One named person who decides to switch
Record the guest separately where you can
If the remote voice only exists inside the mixed stream, any glitch is permanent. Where the platform allows it, capture the guest on a separate track or ask them to record locally on their own device as a safety copy. The local file is rarely perfect, but it can rescue a section lost to a dropped signal.
Explain this to the guest in plain terms and ask them to keep the file until you confirm you have what you need. Agree how it will reach you afterwards. Large audio files are awkward to send, so settle the method before the session rather than during the awkward minutes after it.
This belongs with your wider backup plan, not apart from it. A recording of the room, a recording of the mix and a separate guest track are three different protections against three different failures. You do not need all of them every time, but you should know which ones you chose and why.
- Separate guest track where the platform allows
- Local safety recording on the guest's device
- Agreed way to send the file afterwards
Run the final check in the last half hour
Thirty minutes before you start, bring the guest in and go through a short routine: speak at normal level, confirm they can hear the room, check for background sounds, and look at your meters while they talk. Fix one thing at a time so you know what changed the result.
Listen on headphones rather than speakers. Small faults such as clipping, a rattling desk or a distant television are easy to hear in a close pair of headphones and easy to miss in a busy room. If something is wrong and cannot be fixed in the time left, decide now whether the guest joins by phone instead.
Finish by recording a short stretch of the guest's room tone and playing it back. It confirms the file is being written and gives an editor something to match later. Then stop adjusting. Leaving a working setup alone is part of the craft.
- Speak, listen and check meters together
- Monitor on headphones
- Record a few seconds of the guest's room tone
A remote guest rarely fails because of one big mistake. It is usually a quiet room not checked, a return feed not built, or a fallback nobody agreed. Work through these points before you decide how the guest joins, and the session becomes a routine you can repeat. If you want to talk through a particular setup, we are glad to look at it with you.