Two remote guests is not the same math as one
A host and one remote guest is a single connection: one round trip, one echo path, one file to worry about losing. Add a second remote guest and you now have three separate legs, three chances for feedback, and three tracks that all have to line up in the edit. The setup has to change, not just scale up.
This is about the wiring, not the conversation. Keeping three voices moving once the call is live is a moderation skill, and choosing which platform to record on at all is a separate tool decision. This piece is the routing underneath both: what feed each person hears, what gets recorded where, and what happens when one leg drops.
Route mix-minus, not the full mix, to every leg
Mix-minus means each person's outgoing feed carries everyone else's audio and leaves their own voice out. Send someone their own mic back and you get a loop: a faint delayed copy of themselves under everyone else, and a call platform's echo canceller fighting three sources instead of one.
| Participant | What their feed includes | What it leaves out |
|---|---|---|
| Host | Guest A, Guest B | The host's own mic |
| Guest A | Host, Guest B | Guest A's own mic |
| Guest B | Host, Guest A | Guest B's own mic |
Most call platforms and recording tools handle this automatically once local recording is on, because each person's own local capture never gets routed back to them. The setting to check is whether the platform still injects a monitor of your own mic into your headphones. If it does, turn it off before anyone joins.
Record three separate local tracks, not a mixed file
A three-way session needs three discrete files: host, guest A, guest B, each captured on that person's own device before the network touches it. A single mixed track from the call platform is your fallback copy, never the file you cut from, the same rule that applies with two people in a hybrid setup, just with a third file added.
- Name each track for the person, not the seat: EP22_raw_host.wav, EP22_raw_rivera.wav, EP22_raw_chen.wav, so a mislabeled guest never gets buried in the edit.
- Confirm the recording tool actually exports three files before the call, not two. Some free tiers cap local tracks and silently drop back to a mixed download.
- Have each guest confirm their own upload finished before anyone closes the tab. A local track that never uploads is worse than no backup at all.
- Keep the platform's own mixed recording running the whole time regardless. It is compressed and combined, but it is complete on the day one local file is not.
Pick one connection as the latency anchor
With three legs, latency does not add evenly. It compounds at whichever pair has the worst connection between them, and that pair is not always the one you would guess. Name one participant, usually you, as the anchor everyone paces off, and route turn-taking cues through that person instead of leaving three parties to guess each other's delay.
In practice this is a hosting habit more than a setting: address each question to a name, wait a full beat longer than feels natural before jumping in, and let the anchor call the traffic when two people start talking over each other. The audio is doing what audio does. Your pacing is what keeps it listenable.
Build the backup path before anyone dials in
With two remote legs, a dropped connection during the call is now a live routing decision, not something you patch in the edit. Decide in advance which leg is most likely to be the weak one, based on what each guest told you about their setup, and have a named fallback ready for that person specifically.
- Confirm each guest's connection type ahead of time. Hardwired beats hotel wifi, and the guest on hotel wifi is your named risk.
- Give that guest a phone-dial-in number as backup, tested once before the day, so a dropped video leg becomes an audio-only continuation instead of a dead line.
- Tell the other two, out loud, what happens if one leg drops: pause, or keep rolling and patch the gap in the edit. Decide it before you need it.
- Keep recording on the two legs that are still connected. A lost leg is a hole to fill later, not a reason to stop the other two tracks.
Write the routing setup down once
None of this is complicated in isolation. It is easy to forget under three separate check-in emails, three time zones, and a recording tool you only open once a month. A short routing sheet, filled once per session, removes the guesswork the day of the call.
| Field | What you enter |
|---|---|
| Anchor | The connection everyone else paces off, usually the host |
| Track names | Host, Guest A, Guest B, matched to real names |
| Named weak leg | Whichever guest confirmed the least stable connection |
| Backup path | The phone number or fallback for the weak leg |
| Drop protocol | Pause and wait, or keep rolling and patch it later |
Most hosts rebuild this sheet from memory every time a three-way comes up, because it happens rarely enough to forget the shape of it. Pod Green Room keeps the routing sheet attached to the episode record, next to the guest pipeline for both guests. Pod Green Room pulls the connection notes onto the same card as the follow-ups, so the anchor, the weak leg, and the backup path are already filled in the next time three people need to be on one call.