Two meetings at the same time: a working setup

Two meetings on the calendar at the same hour, both mandatory, neither cancellable. The cheap version of the fix is two browser windows and luck. It works exactly until one of the calls escalates and you have to actually answer a question. This post is the version that survives a week.

The audio layout

You have one set of ears and two streams of speech. Mixing them into the same channel is the failure mode — both calls turn into background noise. The setup that works is two channels with intentional asymmetry:

• Primary call: headphones, both ears. This is the one you are actively present in. Mic unmuted by default. Camera on if expected.
• Secondary call: external speaker, one ear half-uncovered, or a single AirPod. Audible enough to register, quiet enough not to compete. Mic muted. Camera off — "I have to step away for a moment" in the chat, set once, leave it.

The asymmetry is the point. Trying to give equal attention to both is what breaks. The secondary is for monitoring, not participating. You will jump in if your name comes up; you will not contribute otherwise.

↳ pull quote

Two streams of equal volume into one head produces zero comprehension. Make one of them quieter on purpose.

The calendar trick

Block the second half of the secondary call as "focus" on your shared calendar. People do not double-book on top of a focus block. If the secondary is recurring (status, standup, etc.), this is the easy win — you accept the first half, send a regret for the second, and the meeting ends naturally for you when the active half does.

If you cannot decline a section of the call, set the expectation up front. "I might be on mute for parts of this — I'm bridging two things, please tag me directly if you need me." This converts the social cost from "rude/checked out" to "warned and tagged" and most teams accept it without comment.

The watcher on the secondary

The thing that actually makes this workable is having something listen to the secondary call so you do not have to. Specifically: an alert that fires when your name is spoken or when a topic you care about surfaces, with enough context that you can rejoin the thread cleanly.

MeetPing is built for exactly this. The auto-arm watches Core Audio and the foreground meeting app, so when the secondary call starts the listener fires up automatically. The past-30s replay captures the 30 seconds before your name fired plus the 30 seconds after, so you can read what was happening while you were heads-down in the primary call. By the time you unmute on the secondary you already know the thread.

The profile move

Different calls want different keyword sets. Engineering standup needs metric names, sprint identifiers, the names of services that just broke. Customer call needs the account name, the AE's name, the renewal flag. Profiles let you keep separate watchword lists per context and switch with one click. The benefit during overlap is that you can run the standup profile on the primary and the customer profile on the secondary in your head — different words, different priorities, neither leaking false positives into the other.

Camera, mic, and the etiquette layer

The unwritten rules that keep this from being rude:

• Camera off on the secondary, always. People do not need to see you typing into the other window.
• Mic muted on the secondary unless you are actively answering. The accidental hot-mic during a customer call is the failure mode you cannot recover from.
• If the primary needs eye contact (sales call, 1:1 with your manager), do not run a secondary at all. Some meetings cannot be background-tasked.
• If you are speaker-presenting on the primary, secondary comes off entirely. You will mis-speak otherwise.

The on-device requirement

A keyword listener that uploads your audio to a cloud transcript service is fine on your own personal calls and a hard sell on your employer's. The whole reason this setup is socially survivable is that nothing leaves your machine. The audio buffers age out of RAM in 30 seconds. Nothing is written to disk. The case for on-device vs cloud transcription is laid out in full elsewhere — the short version is that a bot in the call changes the nature of the call.

For the same reason, do not record either meeting. The watcher is enough. Recordings outlive the moment you might have wanted them.

The full overemployed kit

This post covers the back-to-back case. The broader workflow — energy budgeting, what to do about Slack, the three browser windows — lives in the overemployed meeting survival kit. And the head-to-head with the closest tool in this shape is on MeetPing vs PingMeBud.

The take

Two simultaneous calls are not solved by trying harder. They are solved by audio asymmetry, a clear secondary posture, a keyword listener doing the monitoring for you, and the discipline to not turn the camera on. The cheap version costs nothing; the version that survives the quarter includes a local watcher.