A remote interpreting setup
that holds up all day.

AIIC's distance interpreting guidance starts here for a reason: plug in an ethernet cable. Wi-Fi is fine until the exact moment it isn't, and a two-second dropout costs a listener a whole sentence in a language they can't fall back on.

Have a fallback ready before you need it: a phone hotspot already configured, and the meeting link open on a second device. The point isn't that you'll use them, it's that switching takes seconds instead of minutes when you do.

Interpreters sit in headphones for hours, which makes hearing protection part of the setup, not an accessory. Acoustic shock, the sudden spike when someone's mic feeds back or a laptop gets dropped, is taken seriously enough that AIIC's technical committee works on it. A wired headset with a built-in limiter is the practical baseline, and it's worth knowing that limiters cap peaks rather than making loud days safe: keep your listening volume as low as you can work with.

On the outgoing side, your voice is the product. A microphone close to your mouth beats an expensive one across the desk: a headset boom or a dynamic USB mic both work. Skip Bluetooth entirely, in both directions. The compression is audible, the mic placement is wrong, and a battery dying mid-assignment is a self-inflicted incident.

You rarely pick the platform, the client does. What you can do is know each one's limits before the assignment instead of during it.

Zoom has the most complete interpretation feature: language channels on paid plans, up to 20 interpreters, and relay via the "listening in" option so you can work from a colleague's output instead of the floor. The limits: participants need the desktop or mobile app to hear channels, interpretation doesn't work in breakout rooms, and only the host can manage it. Interpreters also can't hear each other natively, which is why the second device exists.

Microsoft Teams supports interpretation with up to 16 language pairs, desktop only. No relay, no handover mechanism, and recordings keep only the floor audio. Don't confuse it with Teams' "interpreter agent," which is an AI speech-to-speech feature under a Copilot license, a different thing entirely.

Webex has native simultaneous interpretation too, and hosts can create channels without Zoom's interpreter cap. It's the one people forget to prepare for.

Google Meet has no human interpretation feature. The workaround is a second, parallel call for the interpretation channel, with all the volume juggling that implies.

On-site, a handover is a nod. Remote, it needs a plan, because the platform gives you nothing: you can't hear your boothmate, and they can't hear you.

• Keep a backchannel open for the whole assignment: a WhatsApp call, a separate meeting, or a second device joined to the main call as a listener. This is where handover cues, terminology help, and "your mic is still open" live.
• Agree the cue before the session, not during it. A countdown message, a raised hand on camera, whatever, as long as both of you know whether the switch happens at the next sentence boundary or the next speaker change.
• Switch every 20 to 30 minutes. Remote fatigue argues for the shorter end.
• The resting half still works. Follow the speech, feed numbers and names into the backchannel, watch the meeting chat, and stay ready to take over early if your partner's connection dies.

Everything above is about the signal. This part is about your hands. During interpretation your eyes belong to the speaker and your glossary, so every control that needs aiming a mouse is a control that costs you a phrase.

Two actions matter most. Mute, because an open mic in the booth channel is the classic remote interpreting incident. And the language switch, because in Zoom the alternative is clicking a small button mid-handover. Zoom has an undocumented keyboard shortcut for that switch, which we've written up in detail: the Zoom interpretation shortcut.

Full disclosure, MuteDeck is our product: it puts both actions on physical keys. A mute key with live state, red when you're muted, that works in Zoom, Teams, Webex, and Meet alike, and a language toggle key for Zoom from its action library. If your week spans two platforms and a second-call Meet workaround, one consistent set of keys is the part of the setup you stop thinking about. The interpreter-specific setup lives on MuteDeck for interpreters.