# Avoma vs Fathom: pricing, features, and which is better > Avoma and Fathom compared across pricing, capture, speaker labels, recordings, notes, sharing, automations, integrations, AI-agent access, and administration. - Canonical HTML: https://circleback.ai/compare/avoma-vs-fathom - Structured JSON: https://circleback.ai/compare/avoma-vs-fathom.json - Comparison directory: https://circleback.ai/compare - Language: en-US - Editorial perspective: Neutral competitor comparison. Circleback appears only as a clearly labeled third option. ## Short answer Avoma has the deeper revenue stack and administration. Fathom is easier and cheaper when the job is recording online calls, making clips, and sending notes to a CRM. The useful buying test is to run both products on the same external call, internal planning session, and noisy in-person meeting. Compare the result, the sharing defaults, and the work that still has to happen by hand. ## Avoma at a glance Avoma spans meeting assistance, CRM hygiene, scheduling, conversation intelligence, and revenue intelligence. Its modular packaging lets sales teams buy depth, while making total cost and cross-company fit more complicated. **Best for:** Customer-facing teams that want notes and CRM sync today, then may add conversation coaching, forecasting, and lead routing without changing platforms. **Less ideal for:** Teams prioritizing in-person capture, simple predictable pricing, or a neutral company-wide memory rather than a revenue workflow. **Price:** Base recording plans from $19/recorder/month annually; intelligence add-ons cost extra Startup is $19/recorder/month with annual billing or $29 month-to-month. Conversation Intelligence and Revenue Intelligence each add $29/selected user/month annually or $35 month-to-month; Lead Router adds $19 annually or $25 month-to-month. Recorder users in a workspace share one base tier. Avoma’s live pricing page currently says Enterprise requires 10 paid seats, while its dedicated minimum-seat help article still says 20, so confirm the minimum in a quote. **Free option:** Free viewer users can consume shared content; recording requires a paid recorder seat. ### Avoma strengths - A broad GTM suite spanning scheduling, recording, CRM updates, coaching, forecast, and routing. - Free viewers let coworkers consume shared meetings without buying a recorder seat. - Strong CRM-oriented workflows, speaker analytics, playlists, scorecards, and enterprise controls. - Action items can be detected with owners and deadlines, tracked in task dashboards, prioritized, and synchronized with CRM and project tools. - Customer meeting data is not used to train AI models; recordings and transcripts can be downloaded in standard formats, and admins can set retention policies. ### Avoma tradeoffs - Conversation Intelligence and Revenue Intelligence are separate add-ons, so the attractive base price is not the full sales-platform price. - Enterprise has a meaningful recorder-seat minimum. Avoma’s current pricing page says 10 while its dedicated help article says 20, so a smaller team should confirm the requirement before evaluating its governance tier. - Avoma’s own help center says it does not fully support in-person meetings the way it supports virtual calls; speaker identification can be limited. - The product model is customer/revenue-centric, which can be awkward for product, engineering, recruiting, and internal meetings. ### Choose Avoma when - You want a modular revenue platform with scheduling and CRM workflow depth. - Free viewer access matters and most recorders are customer-facing employees. - You are comfortable adding paid coaching or forecasting modules as the team matures. ## Fathom at a glance Fathom is easy to love for online calls: unlimited free recordings and transcripts, quick summaries, clips, assigned action items, CRM sync, and a focused interface. Its new Mac experience adds useful bot-free modes, while Windows parity and a generally available in-person app are still arriving. **Best for:** Individuals and sales teams that live in Zoom, Google Meet, and Teams and want a generous free plan, fast summaries, clips, and CRM-friendly workflows. **Less ideal for:** Companies that need proven iOS/Android or in-person capture today, broad cross-platform botless video, a workspace-wide task board, or a cross-channel context graph. **Price:** Free; Premium from $16/user/month annually Free includes unlimited recordings and transcripts but only five advanced AI summaries per month. Paid prices are per user/month: Premium is $16 with annual billing or $20 month-to-month; Team is $15 or $19 with a two-seat minimum; Business is $25 or $34. Enterprise is custom. **Free option:** Yes: unlimited recordings and transcripts, with five advanced summaries per month. ### Fathom strengths - Unlimited free recording and transcription is unusually generous for a solo online-meeting workflow. - Fast, polished summaries, highlights, clips, playlists, assigned action items, and CRM sharing. - Public API and MCP support make the meeting library available to custom tools and agents. - Action items include assignees and transcript evidence, and an Asana integration can synchronize assigned work automatically or on demand. ### Fathom tradeoffs - Fathom’s current pages disagree about iOS availability: the product overview says in-person capture is live, while the help center and launch page still describe the official app as pre-download or coming soon. Treat it as a staged rollout until your account can use it. - Chromebook, Linux, Android, tablet, phone call, webinar, and breakout support remains limited or absent. The current Fathom 3.0 bot-free experience is Mac- and English-only; Windows users remain on the older experience for now. - Bot-free video is currently available for Zoom on Mac. Google Meet support is still described as coming, Teams support depends on how the call is joined, and the bot remains the broadest cross-platform path. - The free plan’s advanced AI summaries are capped even though raw recordings and transcripts are unlimited. - Fathom may use de-identified meeting data to improve its in-house AI models unless the user or Team Edition administrator opts out. Third-party model providers are prohibited from training on it. - All Fathom data is US-hosted. Custom retention is Enterprise-only, applies one policy to the whole team, and is currently configured through support rather than self-service. ### Choose Fathom when - You want a generous free online-meeting recorder and rarely need in-person capture. - Clips, highlights, fast summaries, and simple CRM delivery are the center of the workflow. - You are comfortable keeping the bot for video and named-speaker fidelity. ## Feature comparison | What matters | Avoma | Fathom | | --- | --- | --- | | Capture options | Broad support — Meeting bot, native cloud options, and bot-free desktop capture. Avoma can use a bot, supported native platform recording, or a desktop path. The bot appearance and consent messages are customizable. | Available with limits — Meeting bot or bot-free transcript, audio, and Zoom video on Mac. The bot remains the broadest mature path. Eligible Mac users can choose bot-free transcript-only, audio plus transcript, or Zoom video; Google Meet bot-free video is still coming and Teams behavior varies by how the call is joined. Fathom says the bot-free modes preserve speaker attribution and action items. | | Desktop and mobile | Available with limits — Web and desktop with a mobile app. The platform supports virtual-meeting workflows well. Mobile recording exists, but the company documents caveats for using it as a full in-person substitute. | Narrow or indirect — Mac for the new bot-free experience; Windows on the older path. Fathom supports major online platforms on computers, but its current 3.0 rollout is limited to Mac and English-language meetings. Windows remains supported through the older bot-based experience. Official pages conflict on whether iOS in-person capture is already live; Android, Chromebook, Linux, phone calls, webinars, and breakout rooms are not normal supported paths. | | In-person capture and speaker labels | Narrow or indirect — Possible, with explicit speaker and quality caveats. Avoma says it does not fully support in-person meetings in the same way as virtual calls. Mobile and conference-device workarounds can record audio, but reliable room speaker identification is a limitation. | Narrow or indirect — iOS is staged; the old room workaround cannot separate speakers. Fathom’s marketing overview says its iOS app captures in-person meetings, but the help center and current launch page still call it coming soon or pre-download. In the older workaround, every room voice is attributed to the Fathom user rather than separated. Verify iOS access and room-speaker labeling in the actual account before rollout. | | Recordings, playback, and clips | Broad support — Audio/video playback, snippets, playlists, and coaching review. Virtual customer conversations get rich playback and revenue-review workflows. Hosts, participants, admins, and host managers can download video, audio, and VTT or TXT transcripts. Retention and access depend on workspace configuration and plan. | Broad support — Unlimited AV, playback, highlights, and clips. Fathom has polished review and sharing for online calls. Video no longer universally requires the bot, but the current bot-free video path is limited to Zoom on Mac rather than equivalent across every supported platform. | | Notes, action items, and search | Broad support — AI notes, search, and assigned action-item dashboards. Notes and search are strong. Avoma detects action items with owners and deadlines, tracks them in default task dashboards, suggests priority from meeting and deal context, and flags overdue or at-risk work. Additional topic, scorecard, and coaching intelligence is available through the Conversation Intelligence add-on. | Broad support — Fast summaries, assigned action items, Ask Fathom, and team search. Summary quality and speed are core strengths. Paid AI action items identify assignees and link to the source moment; the API also returns completion state and assignee metadata. Fathom presents action items inside each meeting rather than documenting a workspace-wide task dashboard. Advanced summary types and some AI capabilities are plan-limited even while base transcription is free. | | People, companies, and context | Available with limits — Customer-account and deal context. Avoma organizes history around meetings, accounts, and revenue workflows. It is less focused on a general person/company memory incorporating email, calendar, and internal context for every department. | Available with limits — Meeting and customer-call library. Fathom organizes team calls and customer context well, but does not center a broader email/calendar/person/company knowledge layer for all departments. | | Automatic sharing and workspace defaults | Broad support — Meeting-type visibility defaults, teams, and free viewers. Internal meetings default to private and external meetings to organization visibility, with Primary Team and Public options available. Organization admins can instead choose internal/external defaults for participants, specific teams, or the organization and lock the rule against user changes. Free viewer seats, snippets, and playlists make broad consumption practical. | Broad support — Organization and team visibility defaults, plus attendee auto-share. Admins can set auto-capture and visibility separately for external, internal, and unscheduled meetings at organization or team level, including whether users may override the default. Individuals can also send a summary, a recording, or both automatically—but the audience is every calendar invitee, including people who did not attend. | | Automations | Broad support — Conditional CRM, task, privacy, scheduling, and routing workflows. Avoma has a real organization-level trigger/condition/action system. It can react to calendar, transcript, or note events; filter by title, team, participant domain, keyword, or meeting type; then set privacy or purpose, detect outcomes, update CRM data, and create tasks from action items. Manual rules start on the Startup plan and AI-powered rules require Organization or higher; coaching, forecasting, and lead routing remain separate modules. | Available with limits — CRM, webhook, Zapier, and Asana follow-through. Fathom handles common customer-facing follow-through well. Assigned action items can sync automatically or manually to Asana, webhooks can deliver action-item payloads, and Zapier or CRM integrations extend delivery. It does not document the same broad native trigger/condition/action builder for arbitrary work systems. | | Integrations | Broad support — Deep CRM and sales-stack integrations. Avoma emphasizes CRM, conferencing, calendar, dialer, and sales tools. Action items can sync into HubSpot, Salesforce, ClickUp, Asana, and other destinations, with Zapier extending the catalog. It remains oriented around GTM rather than being a neutral engineering-workflow platform. | Available with limits — Strong CRM, Asana, Zapier, and common work-tool connections. CRM delivery and collaboration integrations cover the common sales workflow, while Asana turns assigned meeting actions into trackable tasks. Broader issue-tracker coverage and custom operational actions are less central. | | API, MCP, CLI, and data portability | Available with limits — API for recordings, transcripts, notes, and coaching data. Avoma documents API access to recordings, transcripts, summaries, notes, and coaching insights on selected plans. Keys are admin-created, requests are user- or organization-scoped, and the documented rate limit is 60 requests per minute. | Broad support — Rich public API and MCP, scoped to the connected user. The REST API can return speaker-attributed transcripts, summaries, action items with assignees and completion state, attendees, CRM matches, playback metadata, and recording downloads. Its official MCP connects authorized meeting data to ChatGPT, Claude, and other clients. Both follow what the authenticated user owns or can see through team sharing; an administrator key does not automatically reach private meetings across the organization. | | Security, privacy, and admin | Broad support — Strong enterprise controls on upper tiers. Admin, configurable retention, SSO, and compliance features are available as plans increase. Avoma says customer meeting data is never used to train AI models, and its DPA commits to deletion or return within 30 days after termination, subject to backups and legal obligations. The same-base-tier requirement for recorder users reduces mix-and-match flexibility. | Available with limits — Strong upper-tier controls, with US-only hosting. Enterprise adds SSO, SCIM, and custom retention. Fathom currently supports one retention policy per team and asks customers to configure it through support. All data is US-hosted; de-identified data may improve Fathom’s in-house models unless users or a Team Edition admin opt out. | | Languages | Broad support — More than 60 documented languages and dialects. Avoma’s help page says it supports more than 60 languages and dialects, while its page title advertises 75+. Buyers should verify the exact language and whether the coaching or revenue-intelligence feature they need supports it. | Available with limits — 38 languages on the free plan. Fathom documents 38 supported languages. Bot-free rollout is currently narrower, so language support should be checked per capture mode. | Ratings describe documented breadth rather than overall product quality: - **Broad support:** Broad native support across the product or relevant paid plans. - **Available with limits:** Documented support with meaningful scope, mode, or plan limits. - **Narrow or indirect:** Narrow, indirect, beta, or substantially plan-gated support. - **Not documented:** No current first-party documentation for a native option. ## Detailed analysis ### Capture options **Avoma has broader documented support for capture options.** **Avoma:** Meeting bot, native cloud options, and bot-free desktop capture. Avoma can use a bot, supported native platform recording, or a desktop path. The bot appearance and consent messages are customizable. Evidence: [Avoma recording](https://www.avoma.com/ai-meeting-assistant/meeting-recording-software). **Fathom:** Meeting bot or bot-free transcript, audio, and Zoom video on Mac. The bot remains the broadest mature path. Eligible Mac users can choose bot-free transcript-only, audio plus transcript, or Zoom video; Google Meet bot-free video is still coming and Teams behavior varies by how the call is joined. Fathom says the bot-free modes preserve speaker attribution and action items. Evidence: [Fathom bot-free recording](https://help.fathom.video/en/articles/11578049), [Fathom product overview](https://www.fathom.ai/overview), [Fathom 3.0 rollout](https://help.fathom.video/en/articles/11577345), [Fathom release notes](https://help.fathom.video/en/articles/6220097). ### Desktop and mobile **Avoma has broader documented support for desktop and mobile.** **Avoma:** Web and desktop with a mobile app. The platform supports virtual-meeting workflows well. Mobile recording exists, but the company documents caveats for using it as a full in-person substitute. Evidence: [Avoma recording](https://www.avoma.com/ai-meeting-assistant/meeting-recording-software), [Avoma in-person meeting support](https://help.avoma.com/can-avoma-help-with-an-in-person-meeting). **Fathom:** Mac for the new bot-free experience; Windows on the older path. Fathom supports major online platforms on computers, but its current 3.0 rollout is limited to Mac and English-language meetings. Windows remains supported through the older bot-based experience. Official pages conflict on whether iOS in-person capture is already live; Android, Chromebook, Linux, phone calls, webinars, and breakout rooms are not normal supported paths. Evidence: [Fathom supported systems](https://help.fathom.video/en/articles/296576), [Fathom 3.0 rollout](https://help.fathom.video/en/articles/11577345). ### In-person capture and speaker labels **Both products cover in-person capture and speaker labels narrowly, indirectly, or on limited plans.** **Avoma:** Possible, with explicit speaker and quality caveats. Avoma says it does not fully support in-person meetings in the same way as virtual calls. Mobile and conference-device workarounds can record audio, but reliable room speaker identification is a limitation. Evidence: [Avoma in-person meeting support](https://help.avoma.com/can-avoma-help-with-an-in-person-meeting). **Fathom:** iOS is staged; the old room workaround cannot separate speakers. Fathom’s marketing overview says its iOS app captures in-person meetings, but the help center and current launch page still call it coming soon or pre-download. In the older workaround, every room voice is attributed to the Fathom user rather than separated. Verify iOS access and room-speaker labeling in the actual account before rollout. Evidence: [Fathom in-person meetings](https://help.fathom.video/en/articles/5500225), [Fathom product overview](https://www.fathom.ai/overview). ### Recordings, playback, and clips **Both products document broad support for recordings, playback, and clips, with different scope and plan limits.** **Avoma:** Audio/video playback, snippets, playlists, and coaching review. Virtual customer conversations get rich playback and revenue-review workflows. Hosts, participants, admins, and host managers can download video, audio, and VTT or TXT transcripts. Retention and access depend on workspace configuration and plan. Evidence: [Avoma recording](https://www.avoma.com/ai-meeting-assistant/meeting-recording-software), [Avoma meeting downloads](https://help.avoma.com/downloading-a-meeting). **Fathom:** Unlimited AV, playback, highlights, and clips. Fathom has polished review and sharing for online calls. Video no longer universally requires the bot, but the current bot-free video path is limited to Zoom on Mac rather than equivalent across every supported platform. Evidence: [Fathom pricing](https://www.fathom.ai/pricing), [Fathom bot-free recording](https://help.fathom.video/en/articles/11578049), [Fathom product overview](https://www.fathom.ai/overview). ### Notes, action items, and search **Both products document broad support for notes, action items, and search, with different scope and plan limits.** **Avoma:** AI notes, search, and assigned action-item dashboards. Notes and search are strong. Avoma detects action items with owners and deadlines, tracks them in default task dashboards, suggests priority from meeting and deal context, and flags overdue or at-risk work. Additional topic, scorecard, and coaching intelligence is available through the Conversation Intelligence add-on. Evidence: [Avoma pricing](https://www.avoma.com/pricing), [Avoma action-item tracking](https://www.avoma.com/ai-meeting-assistant/action-item-tracking-software). **Fathom:** Fast summaries, assigned action items, Ask Fathom, and team search. Summary quality and speed are core strengths. Paid AI action items identify assignees and link to the source moment; the API also returns completion state and assignee metadata. Fathom presents action items inside each meeting rather than documenting a workspace-wide task dashboard. Advanced summary types and some AI capabilities are plan-limited even while base transcription is free. Evidence: [Fathom pricing](https://www.fathom.ai/pricing), [Fathom product overview](https://www.fathom.ai/overview), [Fathom AI action items](https://help.fathom.video/en/articles/640768). ### People, companies, and context **Both products support people, companies, and context, with different scope and plan limits.** **Avoma:** Customer-account and deal context. Avoma organizes history around meetings, accounts, and revenue workflows. It is less focused on a general person/company memory incorporating email, calendar, and internal context for every department. Evidence: [Avoma pricing](https://www.avoma.com/pricing). **Fathom:** Meeting and customer-call library. Fathom organizes team calls and customer context well, but does not center a broader email/calendar/person/company knowledge layer for all departments. Evidence: [Fathom pricing](https://www.fathom.ai/pricing). ### Automatic sharing and workspace defaults **Both products document broad support for automatic sharing and workspace defaults, with different scope and plan limits.** **Avoma:** Meeting-type visibility defaults, teams, and free viewers. Internal meetings default to private and external meetings to organization visibility, with Primary Team and Public options available. Organization admins can instead choose internal/external defaults for participants, specific teams, or the organization and lock the rule against user changes. Free viewer seats, snippets, and playlists make broad consumption practical. Evidence: [Avoma meeting privacy](https://help.avoma.com/meeting-privacy), [Avoma organization privacy policies](https://help.avoma.com/manage-organization-wide-privacy-and-security-settings). **Fathom:** Organization and team visibility defaults, plus attendee auto-share. Admins can set auto-capture and visibility separately for external, internal, and unscheduled meetings at organization or team level, including whether users may override the default. Individuals can also send a summary, a recording, or both automatically—but the audience is every calendar invitee, including people who did not attend. Evidence: [Fathom auto-capture and visibility controls](https://help.fathom.video/en/articles/13729025), [Fathom attendee auto-share](https://help.fathom.video/en/articles/7574785). ### Automations **Avoma has broader documented support for automations.** **Avoma:** Conditional CRM, task, privacy, scheduling, and routing workflows. Avoma has a real organization-level trigger/condition/action system. It can react to calendar, transcript, or note events; filter by title, team, participant domain, keyword, or meeting type; then set privacy or purpose, detect outcomes, update CRM data, and create tasks from action items. Manual rules start on the Startup plan and AI-powered rules require Organization or higher; coaching, forecasting, and lead routing remain separate modules. Evidence: [Avoma pricing](https://www.avoma.com/pricing), [Avoma automations](https://help.avoma.com/understanding-automations-in-avoma). **Fathom:** CRM, webhook, Zapier, and Asana follow-through. Fathom handles common customer-facing follow-through well. Assigned action items can sync automatically or manually to Asana, webhooks can deliver action-item payloads, and Zapier or CRM integrations extend delivery. It does not document the same broad native trigger/condition/action builder for arbitrary work systems. Evidence: [Fathom pricing](https://www.fathom.ai/pricing), [Fathom Asana integration](https://help.fathom.video/en/articles/7639617), [Fathom public API](https://developers.fathom.ai/quickstart). ### Integrations **Avoma has broader documented support for integrations.** **Avoma:** Deep CRM and sales-stack integrations. Avoma emphasizes CRM, conferencing, calendar, dialer, and sales tools. Action items can sync into HubSpot, Salesforce, ClickUp, Asana, and other destinations, with Zapier extending the catalog. It remains oriented around GTM rather than being a neutral engineering-workflow platform. Evidence: [Avoma pricing](https://www.avoma.com/pricing), [Avoma action-item tracking](https://www.avoma.com/ai-meeting-assistant/action-item-tracking-software). **Fathom:** Strong CRM, Asana, Zapier, and common work-tool connections. CRM delivery and collaboration integrations cover the common sales workflow, while Asana turns assigned meeting actions into trackable tasks. Broader issue-tracker coverage and custom operational actions are less central. Evidence: [Fathom pricing](https://www.fathom.ai/pricing), [Fathom Asana integration](https://help.fathom.video/en/articles/7639617). ### API, MCP, CLI, and data portability **Fathom has broader documented support for API, MCP, CLI, and data portability.** **Avoma:** API for recordings, transcripts, notes, and coaching data. Avoma documents API access to recordings, transcripts, summaries, notes, and coaching insights on selected plans. Keys are admin-created, requests are user- or organization-scoped, and the documented rate limit is 60 requests per minute. Evidence: [Avoma API documentation](https://help.avoma.com/api-documentation), [Avoma meeting downloads](https://help.avoma.com/downloading-a-meeting). **Fathom:** Rich public API and MCP, scoped to the connected user. The REST API can return speaker-attributed transcripts, summaries, action items with assignees and completion state, attendees, CRM matches, playback metadata, and recording downloads. Its official MCP connects authorized meeting data to ChatGPT, Claude, and other clients. Both follow what the authenticated user owns or can see through team sharing; an administrator key does not automatically reach private meetings across the organization. Evidence: [Fathom public API](https://developers.fathom.ai/quickstart), [Fathom MCP](https://developers.fathom.ai/mcp-docs), [Fathom release notes](https://help.fathom.video/en/articles/6220097). ### Security, privacy, and admin **Avoma has broader documented support for security, privacy, and admin.** **Avoma:** Strong enterprise controls on upper tiers. Admin, configurable retention, SSO, and compliance features are available as plans increase. Avoma says customer meeting data is never used to train AI models, and its DPA commits to deletion or return within 30 days after termination, subject to backups and legal obligations. The same-base-tier requirement for recorder users reduces mix-and-match flexibility. Evidence: [Avoma pricing](https://www.avoma.com/pricing), [Avoma seat minimums](https://help.avoma.com/is-there-a-minimum-seat-requirement-for-each-plan), [Avoma AI data handling](https://help.avoma.com/do-you-use-my-data-to-train-your-models), [Avoma data processing addendum](https://www.avoma.com/data-processing-addendum). **Fathom:** Strong upper-tier controls, with US-only hosting. Enterprise adds SSO, SCIM, and custom retention. Fathom currently supports one retention policy per team and asks customers to configure it through support. All data is US-hosted; de-identified data may improve Fathom’s in-house models unless users or a Team Edition admin opt out. Evidence: [Fathom pricing](https://www.fathom.ai/pricing), [Fathom auto-capture and visibility controls](https://help.fathom.video/en/articles/13729025), [Fathom security and AI training](https://help.fathom.video/en/articles/296512), [Fathom retention policies](https://help.fathom.video/en/articles/6057089). ### Languages **Avoma has broader documented support for languages.** **Avoma:** More than 60 documented languages and dialects. Avoma’s help page says it supports more than 60 languages and dialects, while its page title advertises 75+. Buyers should verify the exact language and whether the coaching or revenue-intelligence feature they need supports it. Evidence: [Avoma supported languages](https://help.avoma.com/does-avoma-support-other-languages). **Fathom:** 38 languages on the free plan. Fathom documents 38 supported languages. Bot-free rollout is currently narrower, so language support should be checked per capture mode. Evidence: [Fathom pricing](https://www.fathom.ai/pricing), [Fathom bot-free recording](https://help.fathom.video/en/articles/11578049). ## A third option to consider: Circleback Circleback turns online meetings, in-person conversations, and imported calls into one shared company memory. Record with a bot, with the botless desktop app, from an iPhone or Android phone, or on Apple Watch. Every route produces the same speaker-labeled record, detailed notes designed to stand alone, and automatically assigned action items. Sharing rules and automations carry the useful parts into the teams and tools that need them. Circleback is built for people and AI agents: the complete meeting record available to a person is also available programmatically through its API, MCP, and CLI. Circleback can also search connected apps and take action in them. It is built for people and AI agents: the same complete meeting data available to a person is available programmatically to ChatGPT, Claude, other agents, and internal tools through the API, MCP, and CLI. Free; Pro from $15/user/month annually; Business from $25/user/month annually; Enterprise $35/user/month, billed annually. ## Frequently asked questions ### Which is better: Avoma or Fathom? Avoma has the deeper revenue stack and administration. Fathom is easier and cheaper when the job is recording online calls, making clips, and sending notes to a CRM. ### Which is less expensive, Avoma or Fathom? Avoma: Base recording plans from $19/recorder/month annually; intelligence add-ons cost extra. Fathom: Free; Premium from $16/user/month annually. Compare the paid seats, included usage, recording access, and admin features you actually need. ### Can Avoma and Fathom record without a bot? Avoma: Meeting bot, native cloud options, and bot-free desktop capture. Fathom: Meeting bot or bot-free transcript, audio, and Zoom video on Mac. The useful check is whether your required capture mode keeps video, a recording, and speaker names. ### Which is better for a whole company? First ask who gets each note automatically; otherwise useful context stays with the recorder. Then compare permissions, retention, and enforced defaults. Avoma: Meeting-type visibility defaults, teams, and free viewers. Fathom: Organization and team visibility defaults, plus attendee auto-share. ### Can I access and move the full meeting data? Avoma: API for recordings, transcripts, notes, and coaching data. Fathom: Rich public API and MCP, scoped to the connected user. Check the selected plan, authentication model, transcript scope, export format, and retention window for the workflow you need. ### How was this comparison researched? We use first-party pricing pages, product pages, help docs, and release notes for both products. The sources are linked below. ## Methodology Circleback reviews first-party pricing pages, product pages, help docs, and release notes. Prices and capabilities move, so check the linked sources when a detail is important to your decision. Every feature dimension links to the exact first-party documents used for that claim. Ratings describe documented breadth, not an overall score or winner. This page is a neutral competitor-to-competitor comparison. There are no paid placements or affiliate rankings. ## First-party sources ### Avoma sources - [Avoma pricing](https://www.avoma.com/pricing): Base plans, free viewers, minimums, and Conversation/Revenue Intelligence add-ons. - [Avoma seats and add-ons](https://help.avoma.com/avoma-pricing-recorder-seats-free-users-add-ons): Recorder-seat rules, viewer access, add-on prices, and workspace base-tier behavior. - [Avoma seat minimums](https://help.avoma.com/is-there-a-minimum-seat-requirement-for-each-plan): This help article says Enterprise has a 20-recorder minimum, while the live pricing page says 10; verify the current requirement with Avoma. - [Avoma in-person meeting support](https://help.avoma.com/can-avoma-help-with-an-in-person-meeting): Official limitations and workarounds for room conversations. - [Avoma recording](https://www.avoma.com/ai-meeting-assistant/meeting-recording-software): Capture methods, languages, CRM workflow, and retention overview. - [Avoma meeting privacy](https://help.avoma.com/meeting-privacy): Automatic internal and external defaults plus Private, Primary Team, Organization, and Public access levels. - [Avoma organization privacy policies](https://help.avoma.com/manage-organization-wide-privacy-and-security-settings): Locked organization defaults for internal and external meeting visibility across participants, teams, or the whole organization. - [Avoma API documentation](https://help.avoma.com/api-documentation): Recording, transcript, summary, notes, coaching insight, scope, authentication, and rate-limit details. - [Avoma action-item tracking](https://www.avoma.com/ai-meeting-assistant/action-item-tracking-software): Automatic owner and deadline extraction, task dashboards, prioritization, at-risk flags, and CRM/project-tool synchronization. - [Avoma automations](https://help.avoma.com/understanding-automations-in-avoma): Organization-level triggers, conditions, plan gates, privacy rules, AI outcomes, CRM updates, and task creation from notes. - [Avoma meeting downloads](https://help.avoma.com/downloading-a-meeting): Recording downloads and transcript exports in VTT or TXT. - [Avoma supported languages](https://help.avoma.com/does-avoma-support-other-languages): Official multilingual transcription count and language list. - [Avoma AI data handling](https://help.avoma.com/do-you-use-my-data-to-train-your-models): Explicit statement that customer data is not used to train AI models. - [Avoma data processing addendum](https://www.avoma.com/data-processing-addendum): Subprocessor terms, transfer safeguards, and deletion or return within 30 days after service termination. ### Fathom sources - [Fathom pricing](https://www.fathom.ai/pricing): Free, Premium, Team, Business, and Enterprise prices and feature gates. - [Fathom supported systems](https://help.fathom.video/en/articles/296576): Computer, platform, mobile, phone call, webinar, and breakout limitations. - [Fathom in-person meetings](https://help.fathom.video/en/articles/5500225): Current workaround, speaker limitation, and upcoming iOS path. - [Fathom bot-free recording](https://help.fathom.video/en/articles/11578049): Current Zoom-on-Mac bot-free video and Google Meet/Teams rollout status. - [Fathom product overview](https://www.fathom.ai/overview): Current bot-free capture modes, speaker attribution, action items, Ask Fathom, programmatic access, and the marketing claim that iOS capture is available. - [Fathom 3.0 rollout](https://help.fathom.video/en/articles/11577345): Current Mac-only, English-only eligibility and staged rollout behavior for the new bot-free experience. - [Fathom auto-capture and visibility controls](https://help.fathom.video/en/articles/13729025): Organization and team defaults for capture and visibility across external, internal, and unscheduled meetings. - [Fathom attendee auto-share](https://help.fathom.video/en/articles/7574785): Automatic delivery of summaries, recordings, or both to every calendar invitee, including no-shows. - [Fathom public API](https://developers.fathom.ai/quickstart): User-scoped API keys plus meeting metadata, speaker-attributed transcripts, summaries, assigned action items, CRM matches, pagination, and administrator visibility limits. - [Fathom MCP](https://developers.fathom.ai/mcp-docs): Official authenticated MCP access from ChatGPT, Claude, Claude Code, and other compatible clients. - [Fathom AI action items](https://help.fathom.video/en/articles/640768): AI detection of action items and their assignees plus follow-up email generation. - [Fathom Asana integration](https://help.fathom.video/en/articles/7639617): Automatic or manual synchronization of assigned meeting actions into Asana with source links. - [Fathom release notes](https://help.fathom.video/en/articles/6220097): July 2026 API recording-download support and current product changes. - [Fathom security and AI training](https://help.fathom.video/en/articles/296512): US data hosting, de-identified in-house model training and opt-out controls, plus third-party no-training terms. - [Fathom retention policies](https://help.fathom.video/en/articles/6057089): Enterprise-only, support-managed retention with one policy per team.