Integrations · Call transcripts

Marcora + Fathom

Bring selected Fathom meetings into a launch, campaign or other project. Keep the decisions behind the work available when shaping a content plan and writing from it.

Beta

Selected imports and scheduled import rules are available in Beta. Call-generated plans and Follow-ups are available; you control generation and publication.

How it flows · Beta

FathomSelected call transcript
Marcora contextUse with approved company knowledge

Why this source

Plan Campaign Content From the Meetings Behind It

Keep the relevant meeting alongside the campaign brief. Use the team’s commitments and questions to shape the work, then create or revise documents with the same project context.

How it works

Give the Campaign Its Conversation Context

Choose the meetings relevant to the initiative and file them where the plan and writing will happen.

1. Connect Fathom and choose relevant meetings, or ask Marcora to find calls and import them by reference. 2. Review the call details, summary, participants and actual audience, then file the meeting with the launch, campaign or other project it should inform. 3. Use the meeting when shaping the content plan and creating or revising writing. When content-needs processing is enabled, internal commitments can suggest new plans and external requests become Follow-ups.

Source details

Keep the Source Useful

Review speaker names, internal/external identification, company details and call kind. Use company, date and kind controls to choose the conversations relevant to the piece you are creating.

Repeatable workflow

Define How Calls Come In

Use an import rule to keep the source, filters and project filing together. Rules for all five Beta providers can run on selected days and times or use as-ready polling every 15 minutes. Run now is also available. Automatic imports stay Only me for a call with 2 or fewer speakers or a speaker Fathom doesn't list, regardless of the rule’s audience.

Put it to work

From Meeting to Plan, Writing and Reference

Keep the meeting with its project while shaping the content needed. When enabled, automatic content-needs processing suggests new plans and matches existing readable content; it does not recommend targeted document updates. You can edit, accept, dismiss or generate directly from Pending. Revisions to existing writing are user-directed, and nothing publishes automatically.

• Use meeting details alongside the launch/campaign brief and approved company knowledge. • New plan suggestions appear as Pending; acceptance is optional before generation, and Produced is not publication. External requests become Follow-ups and are matched against readable existing content first. • Explicitly copy a call summary to Reference Library, or create a blueprint-based reference document, review it, mark Ready and add it. These flows do not auto-sync existing documents. • See the grounding FAQ for the current limits on using conversations as evidence.

Related capability

See the Full Call Transcripts Workflow

Follow one connected meeting through project context, content planning, writing/reference documents and deliberate sharing.

Explore Call transcripts →

Questions About Fathom

Can I import Fathom calls now?

The Fathom adapter supports selected imports as Beta. Available transcript and participant details depend on the source. Review and correct what the source leaves unclear.

Does this automatically import every meeting?

No. Import rules use your filters and filing choices, with selected days and times or as-ready polling every 15 minutes. The first run uses a recent 14-day discovery window. Automatic imports stay Only me for a call with 2 or fewer speakers or a speaker Fathom doesn't list, regardless of the rule’s audience. The Call transcripts page explains Only me and Team sharing.

Can a meeting create or update my content plan?

The call processor suggests new plans and matches existing readable content first; it does not make targeted update recommendations for existing documents. External requests become Follow-ups. Plan suggestions appear as Pending. Generate can run directly from saved Pending or Accepted plans; writing revisions are user-directed, and nothing publishes automatically.

How does Marcora treat a call as evidence?

Calls can appear among a claim’s supporting sources, with a caution note when calls are its only support. A customer’s experience is not company authority. Conversation detection is limited today and does not link to the supporting passage; an improved engine is in development. See the capability page for the current grounding limits.

Explore Call transcripts →
Can meeting details become a reference document?

Yes, through explicit user actions using eligible call context. Copy a summary to Reference Library with confirmation, or generate a blueprint-based document, review it, mark Ready and choose Add to Reference Library. A copied summary is not continuously synced, and ingestion does not automatically rewrite existing library documents.

Put Selected Fathom Conversations to Work

Start with the conversations that matter to your next piece of content.