Fred Your AI Teammate Explained: What It Changes Now

What launched on November 11, 2026, and what it changes

Fireflies launched Fred as an AI teammate on November 11, 2026, and its launch post says Fred "still takes notes" but now also sorts your inbox, keeps you on top of Slack, and finds answers across your apps. For a small B2B team, that turns a notetaker subscription into a broader work assistant, so the buying question moves from "which transcript tool" to "can one assistant cover notes, inbox, Slack, and follow-up well enough to replace tools we already pay for." Our category call is that Fred should be judged as a work assistant that includes meeting notes, not as a new notetaker, and that judgment should rest on workflow scope, admin controls, and a price you can verify rather than on transcript quality, which none of the sources here measure.

An AI teammate, as this guide uses the term, is an assistant that acts across meetings and messaging tools instead of only producing a transcript and a summary.

TL;DR: Fred is a wider assistant than the notetaker it grew from, its Slack and inbox scope is described on Fireflies' own pages, and the paid price is the open question for a buyer deciding this month.

Key Takeaways

• Fred now covers meeting notes plus inbox, Slack, and cross-app search, according to the launch post dated November 11, 2026.

• Scheduling and screen recording are described as coming later, not as shipped features.

• Slack is the most concrete current capability: thread and channel summaries, plus questions answered across Slack, meetings, email, and web.

• Fireflies' webhooks cover 3 event types, retry failed deliveries up to 5 times, and limit team-wide webhooks to Enterprise.

• Otter.ai's Business plan costs $19.99 per user per month billed annually, and Fathom's Team plan costs $15 per user per month billed annually. No Fireflies paid price could be read on its pricing page.

• Pilot Fred on one team's real calls before a company-wide purchase, and write recording-consent rules first.

How we evaluated these tools

This guide compares Fred with Otter.ai and Fathom on five criteria a small B2B team actually decides on. Every price, plan limit, and feature below comes from a vendor page we opened for this guide, and independent sources are used only for context and labeled as such. We did not run any of these products, so nothing here is a hands-on test.

Two limits apply throughout. The launch post we opened confirms the November 11, 2026 date and the split between what Fred does now and what is coming, but the copy we could read did not include the full feature list, rollout dates, or usage figures, so this guide does not repeat them. The Fireflies pricing page we opened names its Free, Pro, Business, and Enterprise plans, but its text carried no per-seat figures, so no Fireflies paid price appears here.

The weights sum to 100%. Scope and price carry the most weight because they change both the monthly bill and the team's routine. Consent carries less weight because it is a rule a team sets once, not a feature to compare.

Feature matrix: Fred against Otter.ai and Fathom

The most useful baseline for Fred is Fireflies' own previous role, which the launch post describes as a product that still takes notes, with the new work layered on top. The two rivals are compared on the same decision items, using only the vendor pages we opened.

Read the "not on the pricing page we opened" cells carefully. They mean a vendor's pricing page does not state the feature, not that the product lacks it, so a buyer should check each vendor's feature pages before deciding. For Fireflies, the Slack details come from its Slack product page, which describes connecting the app, choosing the channels where Fred should respond, and then mentioning Fred to make requests.

The Fireflies pricing page describes Business as adding higher, team-pooled API limits, analytics, private channels, and video recording. It lists HIPAA-ready support with a BAA, SSO, SCIM, Private Storage, and Audit Logs without a clear mapping to a plan, while the Slack page ties BAA support to Enterprise with Private Storage. For a buyer, the compliance question should go to Fireflies before a rollout rather than be assumed from the feature list.

Pricing and seat math

Fireflies' pricing page names four plans, Free, Pro, Business, and Enterprise, and the text we could read gave no per-seat figures, so this guide prints no Fireflies paid price. Treat any Fireflies number you see elsewhere as unverified until you read the live page for your seat count. The page also says buyers of more than 50 members should contact the company.

Team plan: $15 per user per month billed annually according to Fathom (2026). Fathom's Team plan requires a minimum of 2 users, and its Business plan at $25 per user per month billed annually adds CRM field sync, which the Team plan does not list.

Otter.ai's Business plan costs $19.99 per user per month billed annually, according to Otter.ai (2026). Its Basic plan is free with 300 transcription minutes per user in a shared pool. Its Pro figures carry a footnote that the discounted rates apply only to India-issued cards, so this guide quotes no Pro price. Otter.ai's Enterprise plan is custom priced and handled by sales, so it is listed as Quote-based.

Checked November 11, 2026: the Otter.ai and Fathom prices above were re-read on their live pricing pages on that date. The 10-seat column is simple arithmetic on annual-billing prices, shown step by step in the table below.

Ten seats times 12 months times $19.99 gives $2,398.80 for Otter.ai's Business plan. Ten times 12 times $15 gives $1,800 for Fathom's Team plan, and ten times 12 times $25 gives $3,000 for Fathom's Business plan. Fathom's Premium plan for individuals is $16 per user per month billed annually according to Fathom (2026), and its Free plan lists unlimited recordings and transcriptions with no team features or CRM sync. Fireflies stays blank until its live page is read for your seat count. Taxes and add-ons are outside these pages, so the invoice remains the final test.

Signal vs speculation

We keep verified facts apart from our judgment.

Signal, from pages we opened:

• Fireflies' launch post is dated November 11, 2026, and says Fred "still takes notes" while also sorting inboxes and keeping users on top of Slack.

• The same post says Fred will "take on even more," naming scheduling and screen recording. The copy we read does not describe either as shipped.

• Fireflies' Slack page lists meeting notes, thread and channel summaries, and cross-app questions for Slack.

• Fireflies' webhook documentation lists 3 event types, retries failed deliveries up to 5 times, and limits team-wide webhooks to Enterprise with the Super Admin role.

• Study size: 756 companies in Metrigy's 2026-27 AI study according to No Jitter (2026). That study covers AI practice in general, not notetaker adoption.

Speculation, our judgment:

• We expect many small teams to keep a dedicated notetaker for recording and use Fred mainly for Slack and inbox work at first. None of the sources here measures that split.

• We think the Enterprise gate on team-wide webhooks will push small teams toward per-meeting designs, which need their own testing before anyone relies on them.

• We do not know how accurate Fred's answers will be on your data, and no source we read says.

• Because the Metrigy study covers AI practice broadly, we read it as a reason to pilot before a full rollout, not as a forecast for Fred.

Vendor profiles: best fit, limits, and setup

Fireflies Fred

Best fit is a team that already runs most of its calls and Slack threads through Fireflies and wants notes, summaries, questions, and follow-up drafts in one place. A team that wants fewer separate subscriptions is the buyer the launch post is aimed at.

The limits are that the paid price is not printed here, the full rollout schedule could not be read on the copy we opened, and team-wide webhooks are gated to Enterprise. Slack setup is a workspace connection, channel selection, and a mention. Developer use means a receiving endpoint that returns a 2xx status within 30 seconds, with a signing secret so each request's X-Hub-Signature header can be checked. Retry limit: 5 times per failed webhook delivery according to Fireflies (2026). The endpoint should therefore treat repeat events as possible duplicates. Evidence: Fireflies' launch post and the Slack page.

Otter.ai

Best fit is a team whose need is transcription and notes first, at the lowest entry cost. Otter.ai's Business plan lists unlimited monthly minutes with a 4-hour cap per conversation, according to Otter.ai (2026). The pricing page we opened does not describe Slack, inbox, or webhook features, so this profile cannot credit Otter.ai with them. The Pro footnote also complicates any budget. Setup is seat-based billing, so the team needs to decide which members hold a paid seat before buying. Evidence: Otter.ai pricing.

Fathom

Best fit is individuals and small teams that want AI call summaries, action items, and, at the Business tier, CRM field sync. The Free plan lists unlimited recordings and transcriptions plus instant AI call summaries, with no team features or CRM sync. The Team plan has a 2-user minimum, CRM field sync sits on Business, and the Slack and inbox features Fred covers do not appear on the pricing page we opened. Choose Team or Business only if you need shared workspaces or CRM sync, and check the tier before purchase. Evidence: Fathom pricing.

Workflow changes for a small team

This section describes a proposed, configurable workflow for a team that already records calls. It is a design to pilot, not a live deployment or a measured result.

Proposed workflow, call notes into the CRM: when Fireflies sends a meeting.transcribed event, a US Tech Automations design would fetch that meeting's transcript through Fireflies' API using the meeting_id, draft a CRM note with decisions and action items, and post the draft to the account owner in Slack for approval. The prerequisites are a receiving endpoint that returns a 2xx status within 30 seconds, the signing secret checked against the X-Hub-Signature header, CRM credentials, and written rules for which calls may be recorded. Confirm first that your plan allows the webhook scope you need, since the documentation limits team-wide webhooks to Enterprise. The human review point is the account owner, who approves the draft before anything is written to the CRM.

The second design point is repeat delivery. Fireflies retries failed deliveries up to 5 times and can resend an event with a reprocessed_at value when a transcript changes, so the receiver should key every CRM write on meeting_id. A failed write should post to an owner channel instead of failing silently. Those rules belong to the buyer, and each step in the table needs a named owner.

Take an illustrative 10-person services firm that records 30 client calls a week and types CRM notes by hand at 12 minutes a call. That is 360 minutes, or 6 hours a week, or 288 hours across 48 working weeks. If a draft arriving from meeting.transcribed cuts review time to 3 minutes a call, the saving is 9 minutes per call, or 270 minutes (4.5 hours) a week, or 216 hours a year across 48 weeks. These numbers are assumptions chosen for the example, not measured results. The 3-minute review time is exactly what a pilot would have to prove before the firm relies on it.

The main alternative most small teams will weigh is stitching this together in Zapier, Make, or n8n, or building it in-house. Those tools can support run histories, retries, error branches, and audit evidence when they are configured, so the difference is not raw capability. The difference is ownership: the buyer designs and maintains observability, idempotency, escalation, access controls, and upkeep. A US Tech Automations design could configure the receiver's signature check, a meeting_id dedupe key, an alert channel for failed deliveries, and a review queue. Your team would still own the CRM credentials, the retention rules, and the sign-off on who sees each draft.

Who should choose which tool

Who this is for

Fred fits a team that already runs most internal and client calls through Fireflies and wants one place for notes, Slack questions, and follow-up drafts, with an admin who can own the rules. Otter.ai fits a team whose need is transcripts at the lowest verified entry cost. Fathom fits individuals and small teams that want call summaries and action items, and at Business, CRM field sync.

Red flags: you need a Fireflies price you can verify before budget approval, you record calls where consent is hard to obtain or client rules forbid recording, or you need team-wide webhook access without an Enterprise plan.

Common mistakes

• Buying on the launch headline without reading the live price for the tier you need.

• Reading "not on the pricing page we opened" as "the product lacks this."

• Turning on a notetaker for client calls before consent rules are written.

• Writing CRM records from webhook events without a dedupe key, so retries create duplicate notes.

Decision checklist

• Read the live Fireflies price for your seat count, and record the figure with its date.
• Confirm which plan includes the webhook scope and admin role you need.
• Write recording and consent rules for each call type, including client calls.
• Pilot the Slack and inbox work your team actually does, on one team, for a fixed period.

When NOT to use US Tech Automations: a simpler tool wins when you only need transcript search across recorded calls, where Otter.ai's Basic plan or Fathom's Free plan answers the question at no cost. It also wins when one Zapier or Make step moving a single field is enough and nobody needs to approve a draft. And it wins when you cannot yet provide the Fireflies API access or CRM credentials the proposed workflow depends on, because no design runs without them.

Frequently asked questions

Is Fred a new product or the same Fireflies assistant?

Fred is the same Fireflies assistant with a wider scope, because the launch post says he "still takes notes" and now also handles inbox, Slack, and cross-app work.

Can I buy Fred this month at a price I can verify?

Not from this guide's sources, because the Fireflies pricing page we opened named its plans without readable per-seat figures. Check the live page for your seat count before budgeting, and use the Otter.ai and Fathom figures above only as comparison points.

Does Fred work inside Slack today?

Yes, according to Fireflies' Slack page, which lists meeting notes delivered in Slack, thread and channel summaries, and questions answered across Slack, meetings, email, and web. Setup means connecting the app, choosing the channels where Fred responds, and mentioning Fred in Slack.

Can Fred replace a notetaker for a small team?

Only after a pilot. The sources here cover scope and terms, not transcript accuracy, so keep your current notetaker until a pilot shows Fred handles your calls well.

Can a small team build its own workflow from Fireflies events?

Yes, within the documented limits. The webhook documentation lists meeting.transcribed, meeting.summarized, and meeting.bot_joined, and team-wide webhooks require Enterprise with the Super Admin role.

Do Otter.ai or Fathom offer the same Slack and inbox scope?

Neither pricing page we opened describes Slack or inbox features, so this guide cannot confirm either way. Check each vendor's feature pages before comparing scope, since scope is the criterion with the highest weight.

Decide this month or wait

Act this month only if three things are true: you can read the Fireflies price for your seat count on the live page, your recording consent rules are written, and one team has a pilot target for its Slack and inbox work. If any of those is missing, wait for the full feature list and rollout dates, which the copy we opened did not include. For background on how SaaS companies get surfaced in AI answers, see how SaaS companies get cited in Google AI Overviews. For another 2026 launch comparison, see the GPT-5.6 Sol alternatives after its launch, and for a broader SaaS software roundup, see our 2026 SaaS roundup. For a proposed webhook-to-CRM review design of this kind, see how US Tech Automations configures this.