Fireflies.ai

Fireflies records meetings by joining as a visible bot (commonly named "Fred") that posts an in-call chat notice announcing the recording, which is how the product handles the two-party/all-party consent requirements that apply in many jurisdictions — admins can restrict which users are allowed to invite the bot into a call from the workspace's app permission settings. On the Free plan, storage is capped at 800 minutes of transcripts on a rolling basis, so older recordings age out automatically unless you upgrade to a paid plan with longer or unlimited retention.

Practical Details

Individual transcripts, along with their AI-generated summaries and action items, can be exported as text, DOCX, SRT, or PDF, or shared via a public link that can optionally be password-protected; admins can also bulk-delete transcripts rather than removing them one at a time. Business and Enterprise plans add controls like restricting external sharing and limiting which calendar-linked meetings the bot auto-joins.

Actionable Considerations

1. Confirm which users can invite the Fireflies bot to calls, since an uninvited or unexpected recording bot is a frequent source of participant complaints.
2. Track your plan's storage window — Free tier transcripts roll off after 800 minutes of cumulative storage — before assuming a missing recording is a bug.
3. Password-protect any transcript share links that contain sensitive discussion before sending them outside your organization.

Setup means connecting your calendar so Fireflies can auto-join scheduled meetings, or manually inviting the "Fred" bot to a specific call -- either way, it joins visibly and posts an in-call notice that the meeting is being recorded.

Practical Details

During setup, configure default note-sharing visibility and confirm who in your workspace can invite the bot, since those settings determine whether every new meeting gets recorded by default or only ones you explicitly add it to.

Actionable Considerations

1. Test with one real meeting first to confirm transcription quality and action-item extraction before rolling out broadly
2. Set default note-sharing visibility deliberately, rather than leaving it at whatever the default happens to be
3. Decide upfront whether the bot should auto-join every calendar meeting or only ones you manually invite it to

Fireflies' practical access control is admin settings governing who can invite the "Fred" bot into a call, plus, on Business/Enterprise plans, restrictions on external sharing of transcripts -- not a granular per-record role and permission system.

Practical Details

Confirm current documentation directly if you need formal audit trails or fine-grained per-transcript permissions beyond workspace/team-level sharing controls, since that's not a headline capability of every plan.

Actionable Considerations

• Restrict who can invite the bot to calls at the workspace level, since that's the real access boundary
• Password-protect any transcript share links containing sensitive discussion before sending them externally
• Confirm your plan tier includes external-sharing restrictions before assuming they're active by default

Scaling means more users generating more transcript minutes against your plan's retention window, plus workspace-level admin settings controlling who can invite the bot to calls and what gets shared externally -- not a technical infrastructure setting.

Practical Details

Business and Enterprise tiers add controls for restricting external sharing and limiting which calendar-linked meetings the bot auto-joins, which matters more as more teams within an org start using it independently.

Actionable Considerations

1. Set workspace-level bot-invite permissions before rolling out broadly, so it doesn't join meetings unexpectedly
2. Use the shared transcript library as your team's searchable knowledge base as adoption grows
3. Review external-sharing restrictions on Business/Enterprise tiers if sensitive discussions are being recorded

Plans are tiered primarily by transcript storage/retention -- the Free tier caps at 800 minutes of stored transcripts on a rolling basis, with paid tiers extending retention and unlocking more AI features (deeper summaries, Ask Fireflies) and admin controls.

Practical Details

The real value comparison is time saved on manual note-taking and follow-up against your plan's cost, plus whether your team actually needs a searchable meeting archive beyond what the Free tier's rolling retention allows.

Actionable Considerations

• Track your cumulative transcript minutes against the Free tier's 800-minute cap before assuming a missing recording is a bug
• Upgrade specifically when you need longer retention or admin/sharing controls, not just more AI features you may not use
• Confirm current tier pricing and feature splits directly, since these change over time

Beyond transcription, Fireflies generates an AI summary and extracts action items from each meeting, and "Ask Fireflies" lets you query across your meeting history in natural language ("what did we decide about pricing last week?") instead of manually searching transcripts one by one.

Practical Details

Soundbites let you clip and share a specific short moment from a call's recording (a key quote or decision) rather than sending someone the entire transcript or recording to find it themselves.

Actionable Considerations

1. Use Ask Fireflies to query across past meetings before manually scanning individual transcripts
2. Clip a Soundbite when you need to share one specific moment, rather than forwarding a full recording
3. Review AI-extracted action items against the actual discussion, since automatic extraction can occasionally misattribute an owner

Fireflies joins Zoom, Google Meet, and Microsoft Teams calls directly as a bot, and integrates with CRMs like Salesforce and HubSpot to log call summaries and notes against the relevant contact or deal record automatically.

Practical Details

For distributing notes elsewhere, native integrations with tools like Slack, Notion, and Asana push summaries and action items into your existing workflow, with Zapier available for connecting anything outside that native list.

Actionable Considerations

1. Connect your CRM first if sales calls are your primary use case, so notes land directly on the right deal record
2. Use the native Slack/Notion/Asana integrations before reaching for Zapier, since they require less setup
3. Confirm which calendar-linked meetings should auto-invite the bot, rather than assuming every meeting should

The practical resources are Fireflies' own documentation and support channels -- confirm current specifics for enterprise-tier support (dedicated contacts, response times) directly rather than assuming a particular service level.

Practical Details

Because most day-to-day questions are about transcription accuracy, bot behavior, or integration setup, checking the documentation for your specific integration (CRM, calendar, Slack) usually resolves things faster than a general support ticket.

Actionable Considerations

• Check integration-specific documentation first for setup issues, since most questions are integration-specific
• Confirm current support tiers and response expectations directly if evaluating a paid plan
• Report transcription accuracy issues with the specific meeting/language involved, since accuracy varies by audio quality and accent

The concrete outcome is not having to manually take notes during a call, which frees people to actually participate, plus a searchable meeting history that makes it easy to check what was said or decided weeks later without relying on memory.

Practical Details

Adoption tends to hinge on the bot itself -- since Fireflies (nicknamed "Fred") joins visibly as a participant, teams that set clear norms for when it's invited adopt it more smoothly than ones where it shows up unannounced and surprises participants.

Actionable Considerations

• Set a team norm for which meetings get the bot invited, so it doesn't surprise external participants
• Use the searchable transcript library for onboarding new team members to past context, not just live meetings
• Review captured action items shortly after each meeting while context is still fresh, rather than letting them pile up

The concrete value is eliminating manual meeting note-taking and creating a searchable archive of what was actually said and decided -- for sales teams specifically, notes and summaries logging directly against CRM contact/deal records removes a manual data-entry step after every call.

Practical Details

Because the bot joins as a visible participant, the value is easiest to realize on recurring, predictable meetings (standups, sales calls, client check-ins) where consistent capture compounds over time, rather than one-off ad hoc calls.

Actionable Considerations

1. Prioritize recurring, predictable meetings for bot invitations first, since that's where searchable history compounds fastest
2. Connect your CRM if sales calls are a primary use case, to remove manual note logging entirely
3. Measure value by time saved on note synthesis and how often the searchable archive actually gets used, not just by adoption alone