Fathom

Fathom can provide meeting summaries, transcripts, and participant context for oper8r workflows. It is useful when teams want meeting evidence in account briefs, follow-up drafts, risk reviews, and internal knowledge workflows.

Connection Pattern

Fathom is typically connected with an approved workspace integration and the minimum scopes needed to read meetings, summaries, and transcripts.

Customer setup checklist:

1. Confirm the Fathom workspace and approved users.
2. Connect Fathom through the approved integration path.
3. Select a small set of meetings for validation.
4. Confirm participant and account matching.
5. Decide which workflows can use transcript-derived evidence.

Data Used

oper8r can use:

• Meeting records.
• Recording summaries.
• Recording transcripts.
• Participants.
• Meeting dates and titles.

Example Workflow

Create a customer-ready follow-up from the latest Fathom meeting
for Acme. Separate confirmed commitments from suggested next steps
and cite the transcript evidence.

Recommended Use

• Use Fathom summaries to orient the workflow.
• Use transcripts for evidence and citations.
• Use CRM or graph records for account identity when possible.
• Review customer-facing outputs before sending.

Limitations

• Meeting titles and participants may not always map cleanly to CRM accounts.
• Transcripts may include sensitive information outside the target workflow.
• Summaries should not be treated as the only source when exact commitments matter.

Related Docs

• Call Recordings
• Google Drive
• Use Cases