# tl;dv vs Avoma: pricing, features, and which is better > tl;dv and Avoma compared across pricing, capture, speaker labels, recordings, notes, sharing, automations, integrations, AI-agent access, and administration. - Canonical HTML: https://circleback.ai/compare/tldv-vs-avoma - Structured JSON: https://circleback.ai/compare/tldv-vs-avoma.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 tl;dv is the lower-friction recorder for clips and recurring reports. Avoma is the more complete revenue workflow with scheduling, CRM updates, coaching, and forecast add-ons. 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. ## tl;dv at a glance tl;dv combines unlimited meeting recording on its free tier with clips, reels, recurring reports, playbooks, and sales coaching. Its newer bot-free desktop mode broadens capture, but that mode is audio-only and drops video, screen share, and chat. **Best for:** Individuals and customer-facing teams that want a generous free recorder, easy clips, recurring multi-meeting reports, and optional sales playbooks. **Less ideal for:** Teams that need a mature mobile rollout, video in bot-free mode, stable API contracts, durable free-plan retention, or one cross-functional company context layer. **Price:** Free; Pro from $18/user/month annually; Business from $29 annually Free includes unlimited recordings and transcripts, but recordings are retained for three months, older recordings are archived shortly after processing, advanced AI credits are lifetime-limited, and after the first ten meetings generated notes cover only the first ten minutes. Paid prices are per user/month: Pro is $18 with annual billing or $29 month-to-month; Business is $29 or $39. Enterprise is quoted separately. **Free option:** Yes: unlimited recordings and transcripts, with retention, archive, AI-note, credit, duration, and concurrency limits. ### tl;dv strengths - One of the broadest free recording and transcription allowances, despite meaningful retention and AI-output limits. - Strong clips, reels, highlights, multi-meeting reports, playbooks, and sales coaching workflows. - Bot and bot-free macOS/Windows capture now sit beside an early mobile recorder for in-person conversations. - Recurring AI reports and conditional Slack workflows are particularly good at turning many calls into a compact digest with decisions and owner/deadline action lists. ### tl;dv tradeoffs - Bot-free capture is audio-only: no video, screen sharing, or meeting chat is preserved. - The newly documented mobile recorder is still described as an early-stage testing experience rather than a mature production path. - Free recordings are retained for three months and quickly archived; after the first ten meetings, generated notes cover only the first ten minutes. - The public API is labeled v1alpha1, and MCP searches typically return at most 50 meetings per query. - There is no bulk meeting export in the product. Individual recording downloads require both owner and downloader to be on a paid plan, plus editor or admin access. - The domain-level Organization is automatic rather than a governed tenant: any same-domain user can join it and the Organization itself cannot be deleted. Paid Teams provide the actual admin hierarchy. - Several advanced AI, sales, and multilingual capabilities are reserved for higher plans. - tl;dv can extract assigned action lists and send them elsewhere, but it does not document a native workspace-wide task system with assignee queues, status, due dates, and completion tracking. ### Choose tl;dv when - Unlimited free recording matters more than unlimited AI notes. - Your workflow revolves around clips, playlists, sales playbooks, and recurring topic reports. - You are comfortable using a bot when video, screen share, and chat need to be retained. ## 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. ## Feature comparison | What matters | tl;dv | Avoma | | --- | --- | --- | | Capture options | Broad support — Meeting bot or bot-free desktop recording. macOS and Windows can capture system audio from any meeting platform without a bot. The bot remains the richer mode for supported conferencing platforms. | 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. | | Desktop and mobile | Available with limits — Web, Chrome, macOS, Windows, and an early mobile app. Desktop capture is broad. tl;dv now documents a mobile app for in-person meetings, but describes it as recently launched, early-stage, and available for testing. | 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. | | In-person capture and speaker labels | Available with limits — Desktop microphone or early-stage mobile recording. A laptop can capture room audio and the newer mobile app can record in-person meetings. tl;dv documents speaker identification generally but does not explain whether the early mobile path preserves the same naming behavior, so test it before a broad rollout. There is no documented Watch capture. | 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. | | Recordings, playback, and clips | Broad support — Rich playback, clips, and reels—with a botless video caveat. Bot recordings support video, transcript, clips, reels, and shareable moments. Bot-free recordings are audio-only and omit video, screen sharing, and chat. | 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. | | Notes, action items, and search | Broad support — AI notes, action digests, multi-meeting reports, and topic tracking. The product is particularly good at synthesizing multiple meetings and turning recurring prompts into reports, including action lists grouped by person and date. Those are report or checklist outputs rather than a native task lifecycle with workspace queues and completion state. Free accounts get a limited number of AI notes. | 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. | | People, companies, and context | Available with limits — Meeting library and multi-meeting synthesis. tl;dv can query and report across accessible meetings, but it does not present a broader email/calendar/person/company relationship memory as its core model. | 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. | | Automatic sharing and workspace defaults | Broad support — Granular team privacy defaults and automatic sharing. Teams can automatically share with participants, publish to a team or organization library, and apply admin privacy rules using meeting context such as title, internal or external type, and team role. Sensitive categories can remain private by rule. | 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. | | Automations | Broad support — Recurring AI reports and sales workflows. Automated multi-meeting reports, playbooks, CRM updates, and conditional Slack posts are useful, especially for customer-facing teams. Slack workflows can format decisions and action items with owners and deadlines, but team workflow scope excludes team admins and billing-group admins, and the overall system is less open-ended than a general meeting condition/action builder. | 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. | | Integrations | Available with limits — CRM and collaboration integrations on paid plans. tl;dv connects to common CRMs and work tools; exact access varies by plan. The catalog is oriented around GTM and collaboration workflows. | 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. | | API, MCP, CLI, and data portability | Available with limits — MCP on Pro+ and a public alpha API. MCP can search meetings and participants, with typical result sets capped at 50. A subtle access rule matters: viewing a shared meeting is not enough if its organizer is on Free—the organizer must have Pro or higher before that meeting is available through MCP or the API. The API is documented as v1alpha1 and includes recording downloads, so integration teams should expect contract evolution. | 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. | | Security, privacy, and admin | Available with limits — Paid Team controls, with a looser domain Organization layer. Paid Teams add roles, billing administration, and forward-looking defaults; team settings do not override Team Admins. The separate domain-based Organization has no organization-wide admin defaults, any same-domain user can join it, and it cannot be deleted. Multi-team management is Business-only. | 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. | | Languages | Available with limits — Multilingual transcription; advanced multilingual mode is plan-gated. Language selection behavior varies by capture mode, and the multilingual Whisper option is documented for Business and Enterprise. | 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. | 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 **Both products document broad support for capture options, with different scope and plan limits.** **tl;dv:** Meeting bot or bot-free desktop recording. macOS and Windows can capture system audio from any meeting platform without a bot. The bot remains the richer mode for supported conferencing platforms. Evidence: [tl;dv bot-free recording](https://intercom.help/tldv/en/articles/14433337-recording-without-a-bot). **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). ### Desktop and mobile **Both products support desktop and mobile, with different scope and plan limits.** **tl;dv:** Web, Chrome, macOS, Windows, and an early mobile app. Desktop capture is broad. tl;dv now documents a mobile app for in-person meetings, but describes it as recently launched, early-stage, and available for testing. Evidence: [tl;dv bot-free recording](https://intercom.help/tldv/en/articles/14433337-recording-without-a-bot), [tl;dv mobile app](https://intercom.help/tldv/en/articles/8490450-mobile-app). **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). ### In-person capture and speaker labels **tl;dv has broader documented support for in-person capture and speaker labels.** **tl;dv:** Desktop microphone or early-stage mobile recording. A laptop can capture room audio and the newer mobile app can record in-person meetings. tl;dv documents speaker identification generally but does not explain whether the early mobile path preserves the same naming behavior, so test it before a broad rollout. There is no documented Watch capture. Evidence: [tl;dv mobile app](https://intercom.help/tldv/en/articles/8490450-mobile-app), [tl;dv speaker identification](https://intercom.help/tldv/en/articles/6171907-speaker-identification-in-transcript). **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). ### Recordings, playback, and clips **Both products document broad support for recordings, playback, and clips, with different scope and plan limits.** **tl;dv:** Rich playback, clips, and reels—with a botless video caveat. Bot recordings support video, transcript, clips, reels, and shareable moments. Bot-free recordings are audio-only and omit video, screen sharing, and chat. Evidence: [tl;dv bot-free recording](https://intercom.help/tldv/en/articles/14433337-recording-without-a-bot), [tl;dv free-plan limits](https://intercom.help/tldv/en/articles/8919450-what-are-the-limits-of-the-free-plan). **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). ### Notes, action items, and search **Both products document broad support for notes, action items, and search, with different scope and plan limits.** **tl;dv:** AI notes, action digests, multi-meeting reports, and topic tracking. The product is particularly good at synthesizing multiple meetings and turning recurring prompts into reports, including action lists grouped by person and date. Those are report or checklist outputs rather than a native task lifecycle with workspace queues and completion state. Free accounts get a limited number of AI notes. Evidence: [tl;dv pricing](https://intercom.help/tldv/en/articles/6082483-what-is-tl-dv-s-pricing), [tl;dv free-plan limits](https://intercom.help/tldv/en/articles/8919450-what-are-the-limits-of-the-free-plan), [tl;dv AI prompts](https://intercom.help/tldv/en/articles/9235713-ai-prompts-inspiration). **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). ### People, companies, and context **Both products support people, companies, and context, with different scope and plan limits.** **tl;dv:** Meeting library and multi-meeting synthesis. tl;dv can query and report across accessible meetings, but it does not present a broader email/calendar/person/company relationship memory as its core model. Evidence: [tl;dv MCP](https://intercom.help/tldv/en/articles/15322415-mcp). **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). ### Automatic sharing and workspace defaults **Both products document broad support for automatic sharing and workspace defaults, with different scope and plan limits.** **tl;dv:** Granular team privacy defaults and automatic sharing. Teams can automatically share with participants, publish to a team or organization library, and apply admin privacy rules using meeting context such as title, internal or external type, and team role. Sensitive categories can remain private by rule. Evidence: [tl;dv team privacy defaults](https://intercom.help/tldv/en/articles/15033798-team-privacy-defaults). **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). ### Automations **Both products document broad support for automations, with different scope and plan limits.** **tl;dv:** Recurring AI reports and sales workflows. Automated multi-meeting reports, playbooks, CRM updates, and conditional Slack posts are useful, especially for customer-facing teams. Slack workflows can format decisions and action items with owners and deadlines, but team workflow scope excludes team admins and billing-group admins, and the overall system is less open-ended than a general meeting condition/action builder. Evidence: [tl;dv pricing](https://intercom.help/tldv/en/articles/6082483-what-is-tl-dv-s-pricing), [tl;dv Slack workflows](https://intercom.help/tldv/en/articles/5946410-set-up-the-slack-integration). **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). ### Integrations **Avoma has broader documented support for integrations.** **tl;dv:** CRM and collaboration integrations on paid plans. tl;dv connects to common CRMs and work tools; exact access varies by plan. The catalog is oriented around GTM and collaboration workflows. Evidence: [tl;dv pricing](https://intercom.help/tldv/en/articles/6082483-what-is-tl-dv-s-pricing). **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). ### API, MCP, CLI, and data portability **Both products support API, MCP, CLI, and data portability, with different scope and plan limits.** **tl;dv:** MCP on Pro+ and a public alpha API. MCP can search meetings and participants, with typical result sets capped at 50. A subtle access rule matters: viewing a shared meeting is not enough if its organizer is on Free—the organizer must have Pro or higher before that meeting is available through MCP or the API. The API is documented as v1alpha1 and includes recording downloads, so integration teams should expect contract evolution. Evidence: [tl;dv MCP](https://intercom.help/tldv/en/articles/15322415-mcp), [tl;dv API](https://intercom.help/tldv/en/articles/11583137-api), [tl;dv download limits](https://intercom.help/tldv/en/articles/5946213-how-to-download-your-recording). **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). ### Security, privacy, and admin **Avoma has broader documented support for security, privacy, and admin.** **tl;dv:** Paid Team controls, with a looser domain Organization layer. Paid Teams add roles, billing administration, and forward-looking defaults; team settings do not override Team Admins. The separate domain-based Organization has no organization-wide admin defaults, any same-domain user can join it, and it cannot be deleted. Multi-team management is Business-only. Evidence: [tl;dv pricing](https://intercom.help/tldv/en/articles/6082483-what-is-tl-dv-s-pricing), [tl;dv team privacy defaults](https://intercom.help/tldv/en/articles/15033798-team-privacy-defaults), [tl;dv organization and team model](https://intercom.help/tldv/en/articles/8975481-organization-vs-team-what-s-the-difference), [tl;dv permission levels](https://intercom.help/tldv/en/articles/10131073-understanding-permission-levels). **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). ### Languages **Avoma has broader documented support for languages.** **tl;dv:** Multilingual transcription; advanced multilingual mode is plan-gated. Language selection behavior varies by capture mode, and the multilingual Whisper option is documented for Business and Enterprise. Evidence: [tl;dv pricing](https://intercom.help/tldv/en/articles/6082483-what-is-tl-dv-s-pricing), [tl;dv bot-free recording](https://intercom.help/tldv/en/articles/14433337-recording-without-a-bot). **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). ## 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: tl;dv or Avoma? tl;dv is the lower-friction recorder for clips and recurring reports. Avoma is the more complete revenue workflow with scheduling, CRM updates, coaching, and forecast add-ons. ### Which is less expensive, tl;dv or Avoma? tl;dv: Free; Pro from $18/user/month annually; Business from $29 annually. Avoma: Base recording plans from $19/recorder/month annually; intelligence add-ons cost extra. Compare the paid seats, included usage, recording access, and admin features you actually need. ### Can tl;dv and Avoma record without a bot? tl;dv: Meeting bot or bot-free desktop recording. Avoma: Meeting bot, native cloud options, and bot-free desktop capture. 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. tl;dv: Granular team privacy defaults and automatic sharing. Avoma: Meeting-type visibility defaults, teams, and free viewers. ### Can I access and move the full meeting data? tl;dv: MCP on Pro+ and a public alpha API. Avoma: API for recordings, transcripts, notes, and coaching data. 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 ### tl;dv sources - [tl;dv pricing](https://intercom.help/tldv/en/articles/6082483-what-is-tl-dv-s-pricing): Official Free, Pro, Business, and Enterprise pricing and plan scope. - [tl;dv free-plan limits](https://intercom.help/tldv/en/articles/8919450-what-are-the-limits-of-the-free-plan): Recording retention, archive behavior, AI-note coverage, lifetime credits, meeting duration, and concurrency. - [tl;dv mobile app](https://intercom.help/tldv/en/articles/8490450-mobile-app): Recently launched early-stage mobile recording for in-person meetings. - [tl;dv speaker identification](https://intercom.help/tldv/en/articles/6171907-speaker-identification-in-transcript): General automatic speaker identification; the article does not document mobile-mode parity. - [tl;dv bot-free recording](https://intercom.help/tldv/en/articles/14433337-recording-without-a-bot): Desktop capture and the audio-only limitation. - [tl;dv MCP](https://intercom.help/tldv/en/articles/15322415-mcp): Plan eligibility, tools, access model, and result behavior. - [tl;dv API](https://intercom.help/tldv/en/articles/11583137-api): Pro/Business eligibility and v1alpha1 status. - [tl;dv team privacy defaults](https://intercom.help/tldv/en/articles/15033798-team-privacy-defaults): Admin-controlled automatic sharing, workspace-library publishing, and privacy rules for sensitive meetings. - [tl;dv download limits](https://intercom.help/tldv/en/articles/5946213-how-to-download-your-recording): No bulk export plus paid-plan, ownership, and permission requirements for individual recording downloads. - [tl;dv organization and team model](https://intercom.help/tldv/en/articles/8975481-organization-vs-team-what-s-the-difference): Automatic same-domain Organization membership, absence of Organization-wide admin defaults, and the paid Team hierarchy. - [tl;dv permission levels](https://intercom.help/tldv/en/articles/10131073-understanding-permission-levels): Team roles, admin behavior, and the non-deletable domain Organization. - [tl;dv AI prompts](https://intercom.help/tldv/en/articles/9235713-ai-prompts-inspiration): Cross-meeting action-item reports grouped by participant and date plus common analysis workflows. - [tl;dv Slack workflows](https://intercom.help/tldv/en/articles/5946410-set-up-the-slack-integration): Conditional automatic summaries, decisions, and owner/deadline action lists plus the team-admin scope exception. ### 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.