Fix: Fireflies Didn't Record My Meeting
The meeting ran forty minutes. You open Fireflies afterward and the call isn't there. No transcript, no summary, no entry in the list. As far as Fireflies is concerned the meeting never happened, because Fred was never in the room to hear it.
This is a different problem from the bot showing up when you didn't want it. Same architecture, opposite failure. Here is the order of operations.
TL;DR
- Fireflies records by sending a participant into the call. No participant, no audio, no transcript.
- Most misses are the auto-join setting, a waiting room, a call under three minutes, or a Recording Rule you forgot you wrote.
- Fireflies' own status log shows call-joining incidents on their side, so it is not always your settings.
- A call the bot missed is gone. You cannot re-record a conversation that already happened.
What people are saying
Fireflies keeps a whole page for this, Why Fred did not join your meeting, and it lists seventeen distinct causes. That number is the story. A feature with seventeen documented failure modes is not one that fails rarely.
Their transcription troubleshooting guide adds the two limits people trip over most. "Fireflies doesn't process meetings that last less than 3 minutes," and "It can take 5–10 minutes for your transcript to be generated after a meeting." Check the clock before you file a ticket.
It also is not always your fault. Fireflies' status history logs "Issues joining Google Meet calls" opening 2026-06-02 and running a little over a day, and "Call Joining, Meeting Processing & Related Services Disruption" on 2026-05-07 (status log via StatusGator). If your miss lands in one of those windows, no settings work would have saved it.
Reviewers describe flakiness, not a hard break. Michiel B., a managing director and practising lawyer, wrote on Capterra on 2026-06-11: "It does not always add itself to meetings automatically. Another issue is that, where several team members are on the same call, the meeting is sometimes captured by another team member's Fireflies agent." That second half catches people out. The meeting was recorded, into someone else's account, and if that owner set sharing to owner-only you cannot see it.
Francisco A. named the workflow gap on 2026-03-18, also on Capterra: "if I'm invited to a digital meeting via WhatsApp and I forget to open Fireflies.ai and start participating in the meeting, I'm left out." A calendar-driven bot cannot see calls that never touched the calendar. tl;dv's Fireflies review, published 2026-04-15, quotes a G2 reviewer on "issues with getting the app to join MS Teams calls." Same shape, different platform.
Why this keeps biting you
Fireflies is a guest at your meeting. To hear anything it has to get past whatever the conferencing platform puts in the way: a lobby, a login wall, a password, a CAPTCHA, an encryption flag, a domain allowlist your IT team wrote last quarter. Each one is a place where a perfectly configured Fireflies account still ends up with nothing.
That gatekeeping is doing its job. The problem is that your notes depend on it failing. Recording is coupled to admission, and other people control admission. The host who never checks the waiting room. The guest who clicks remove. The policy that auto-rejects notetaker apps.
The second coupling is the calendar. Auto-join reads it and decides in advance. An ad-hoc huddle, a call that starts in Slack, a client who phones instead, a link pasted into WhatsApp. None of those are on the calendar, so none of them get a bot. That is the Francisco A. case, and no setting fixes it because there is nothing for the setting to read.
Fix it in Fireflies first
- Check the auto-join setting before anything else. In Fireflies settings, "Auto-join calendar meetings" has four options: All meetings with web-conf link, Only meetings that I own, Only meetings with teammates, and Only when I invite fred@fireflies.ai. The last two are the usual culprit (auto-join guide).
- Look at your Recording Rules. Rules keyed on keywords, email addresses, or domains override the auto-join preference. A rule written months ago to skip internal standups will quietly skip anything that matches it.
- Confirm the calendar is still connected. Reauthorizing Google or Outlook, or re-signing with a different profile, silently breaks the link, and Fireflies stops seeing your meetings at all.
- Admit the bot before the call starts, not four minutes in. Nothing is captured while Fred waits in the lobby, and a short call can end before anyone notices him there.
- Check the Meeting Status dashboard, then the status page. The dashboard says whether Fireflies attempted the call and what stopped it. If it attempted and failed, their incident log may already explain why.
- Rule out the three-minute floor and the processing delay. Under three minutes is never saved, and for ten minutes after the call the transcript may simply not exist yet.
- Ask whether a teammate's bot took the call. If two attendees both run Fireflies, one account owns the recording. Have them share it.
If the miss was a lobby block, an encrypted meeting, a CAPTCHA, or a policy that rejects notetakers, stop troubleshooting. Fireflies cannot take that meeting, and it will not take the next one on the same platform either.
Stay or switch
| Job | Stay with Fireflies | Switch to LUCI |
|---|---|---|
| Your team runs on Fireflies search, channels, and CRM push | Yes | No |
| Every call is on your calendar, on a platform that admits bots | Yes | Also yes |
| You take ad-hoc calls, huddles, and in-person conversations | No, nothing for auto-join to read | Yes, capture isn't calendar-driven |
| External guests or IT block third-party notetakers | No | Yes, no participant to block |
| You want meetings searchable next to the rest of your day | No, meetings only | Yes |
What to do next
The checklist recovers most misses. It does not fix the shape of the problem, which is that a bot has to be let in, and the people deciding that are not you.
Bot-free capture inverts that. LUCI records the audio mix on your own computer, so there is no participant to admit, remove, or block, and no calendar entry needed before recording starts. On-device understanding turns that audio into a searchable transcript on Mac and Windows. It does not land in a per-call file either. It joins your memory alongside what was on your screen at the time, so "what did the client agree to in June?" resolves to a cited answer instead of a folder you have to remember to open.
For the side-by-side, see LUCI vs Fireflies, or Fireflies alternatives if you are comparing more broadly.
Frequently asked questions
Why didn't the Fireflies bot join my meeting?
The usual causes are an auto-join setting scoped to meetings you own or to manual invites, a Recording Rule that overrides auto-join, a disconnected calendar, or the bot sitting in a waiting room unadmitted. Platform blocks stop it too: login-required meetings, passwords, CAPTCHAs, end-to-end encryption, a domain allowlist. Fireflies lists seventeen reasons, so work the Meeting Status dashboard rather than guessing.
Can I recover a meeting Fireflies didn't record?
Not from Fireflies. There was no audio feed, so there is nothing to reprocess. If someone recorded the call independently, a Zoom cloud recording or a local file, you can upload it and get a transcript, though that file is then processed in Fireflies' cloud. Otherwise the conversation is gone, which is the strongest argument for capture that does not depend on a bot being admitted.
Why does Fireflies skip meetings shorter than three minutes?
It is a documented product limit, not a bug. Fireflies states plainly that it does not process meetings under three minutes, because short calls are usually noise: accidental joins, connection tests, someone dialling in and dropping. If a two-minute call matters to you, you need a recorder that captures continuously on your machine rather than one deciding after the fact whether the call was worth keeping.
Is there a way to get meeting notes without a bot joining the call?
Yes. Tools that capture your computer's own audio produce a transcript without adding a participant, so there is nothing to admit and nothing for IT or a guest to reject. Fireflies has a bot-free desktop path of its own, though the audio still goes to their cloud. LUCI captures the same way but does the understanding on your device, so the recording and transcript stay on your machine. Either way, tell people you are recording. Bot-free removes the visible cue. It does not remove the obligation.
