Does Your AI Notetaker Lose the Meeting If Your Wi-Fi Drops?

The short answer

Sometimes. It depends on two things: which connection actually failed, and whether the notetaker keeps a copy of your audio while it waits. Two tools can both say they "handle connection drops" and give you very different transcripts of the same bad afternoon.

Before comparing tools, it helps to be precise about the drop itself, because there are two different failures hiding under the same complaint.

Two different drops

The first is a full drop. Your laptop loses the network and the call drops for you. The meeting carries on without you, and the other voices stop arriving at your laptop. No app on your computer can transcribe what your computer never received. The most any local tool can keep is your own microphone and whoever is in the room with you.

The second is more common and easier to miss. The call survives, because video apps are built to ride out packet loss, but the notetaker's own connection to its transcription service stalls. Hotel Wi-Fi, a VPN that reconnects, a train between towers. Granola's troubleshooting page puts it plainly: an unstable connection "can stop transcription even when the rest of the web still loads." You keep talking, the call sounds fine, and the transcript quietly stops growing.

Where the audio lives decides the answer

A bot that joins the call runs on the vendor's servers with its own connection. If your laptop drops, the bot stays in the meeting and keeps recording the other people. This is the one situation where a bot is clearly the safer choice: it catches the part of the meeting you missed. What you said while you were cut off never reached the meeting, so it is missing for everyone.

Some desktop apps write audio to your disk as they record and transcribe it properly afterwards. Junior's help page says losing connection does not interrupt the recording, and that the final transcript is produced from the saved audio, so a gap in the live view disappears from the finished call. Wispr Flow's Notetaker keeps recording to your device when the live transcript stops and transcribes those sections after the meeting once you reconnect; it needs free local storage and asks you to confirm offline recording. The trade is that a recording of your meeting sits on your laptop until it uploads.

Other desktop apps stream audio to the cloud and do not keep it. For them the transcript only contains what reached the service. A short stall can be covered by holding audio in memory and sending it late. Anything longer than that buffer is gone for good, because there is no recording to go back to.

What Driffle does

Driffle is in the third group, by design: audio is not stored, which is a privacy choice with a cost on bad connections. Here is the behaviour in the shipped Mac app.

When the link to the transcription service drops, Driffle holds roughly a minute of audio in memory and sends it once the connection is back, so a short stall should leave no hole. It keeps retrying with growing waits, giving up after twenty failed attempts in a row or two minutes, whichever comes first, which in practice is usually around a minute. If it still cannot reconnect, the note shows a banner saying live transcription stopped and that no new words will appear until you stop and start the recording again. While your Mac is offline, the note says "You're offline, we've paused transcription."

Transcript lines that were already produced are written to disk on your Mac before they upload, and they are sent when the connection returns, including after the app restarts. So you do not lose what was already transcribed.

What Driffle cannot do: fill a gap longer than its buffer after the meeting, because there is no audio to reprocess. And if you stop the recording while you are still offline, the audio held in memory is not transcribed. If your connection drops near the end of a call, reconnect first, then stop. Driffle runs on Apple Silicon Macs, and transcription and AI run in the cloud, so it needs a connection to do anything useful.

A five minute test before you trust any tool

Start a test call between your laptop and your phone, and start the notetaker. Read a numbered list aloud, one to forty, slowly. At ten, turn Wi-Fi off for thirty seconds, then back on. At twenty five, turn it off for three minutes, keep reading, then turn it back on. Wait a minute, then stop.

Now read the transcript and note three things. Which numbers survived each gap. Whether the app told you something was wrong while it was happening, or let you assume it was fine. And whether the missing numbers appear later, once processing finishes. That last one tells you which of the three designs you are actually buying, whatever the marketing page says.

Which design to pick

If you regularly take important calls on connections you do not control, pick a tool that saves audio locally or one that uses a bot, and accept what each costs you: a recording on your disk, or a visible participant in the call. If what matters most is that no recording of the meeting is kept anywhere, accept that a long outage leaves a gap, and fix the connection instead: a cable at your desk, and your phone's hotspot ready before the call that matters.

If the second trade suits you and you want notes without a bot in the call, Driffle is available for Apple Silicon Macs at driffle.ai/download.