Platform · Context · Call transcripts

Turn Your Meetings Into Content Plans

Bring connected meeting transcripts into the project they belong to. Use the commitments and decisions behind the conversation to shape your content plan and inform the documents you create or revise.

Fathom, Gong, Fireflies, Google Meet and Wispr Flow offer Beta imports and scheduled import rules. Call-generated plans and Follow-ups are available; you control generation and publication.

Get started Explore the meeting-to-plan workflow

One meeting, start to draftIllustrative
Launch meetingConnected source · Oct 14
Project: LaunchWith brief + product context
Content plan PendingPartner launch FAQ · from a commitment in the meeting
Edited plan, still yoursSave as pending, Save & accept, or Generate when ready.

01 · From meeting to plan

Spot the Content Worth Creating

Call-generated plans and Follow-ups are available. Review plan suggestions and choose when to generate; nothing publishes automatically.

The call processor suggests new content plans and matches existing readable content first. An internal commitment can be skipped when matching content already exists; external requests take the Follow-ups path. This is not an automatic recommendation to update an identified document.

Launch meeting · Oct 14Illustrative

Team meeting · Internal

12:31

Speaker 1: “I’ll put together a partner FAQ before the launch briefing.”

Example conversation, not a real customer statement.

Source evidenceLaunch meeting · Oct 14

Carry Launch Decisions Into the Content Plan

A launch meeting might clarify the audience, settle a message or name the assets the team needs. Keep those details attached to the project rather than reconstructing them for the next brief. When content-needs processing is enabled, the call-processing workflow identifies still-standing commitments to create content and can suggest new plans.

These are illustrative meeting details, not guaranteed extraction fields. The detector defaults on for team meetings and 1:1s; rejected ideas, artifact mentions and requests to send existing content should not become new plans.

Content plan · editableIllustrative
Title
Partner launch FAQ
Why
Committed in the launch meeting, for the partner briefing
Project
Launch
Context
Launch meetingLaunch briefApproved product context

Illustrative controls only. Your instructions stay in this page and appear in the example draft.

  1. Pending
  2. Accepted · optional
  3. Produced

Pending: Generate now, or accept first. Either works.

Pending

The plan board uses Pending → Accepted → Produced. Call-generated suggestions appear as Pending.

Accepted

Open a plan to inspect its evidence and edit the permitted instructions, timing, project and sources. Save it as pending, accept it, dismiss it or ask Marcora for help.

Produced

Generate can run directly from a saved Pending or Accepted plan. A separate acceptance step is not required before writing; Produced links to new content, not external publication.

Matching an existing document or adding source references to a gap plan does not update the produced document. Revisions to existing writing are user-directed.

Project

Launch

PrivateIllustrative
Meeting
Launch meeting Connected source · Oct 14
Brief
Launch brief
Product
Approved product context
Plan
Partner launch FAQ Pending

Project membership and call permissions still apply. Filing does not make private material public.

02 · One project

Keep the Meeting With the Work It Informs

For a launch, put the relevant meeting in the launch or campaign project alongside its brief and approved company context. The team’s decisions, questions and content commitments can then inform that initiative’s planning and writing. The same pattern applies to other projects and ongoing work.

03 · Create or revise

Create Something New or Revise What You Have

Use eligible project calls when creating or revising a launch brief, messaging document or other writing. You choose the work and review the result. Meeting context supports that task; ingestion does not automatically rewrite your documents.

Create new

Generate From the Plan

Pending or Accepted plan → Generate → new draft.

Use the meeting, launch brief and approved product context together.

Revise existing · you choose the piece

Write With the Launch Specifics

Choose the draft, add eligible project calls as context and ask Marcora for a revision. Review the result before you keep it.

No automatic detection of a specific document to update.

04 · Reference Library

Add to the Reference Library on Purpose

A meeting can teach the whole team something. Sharing that knowledge is a step you take, not a side effect of importing.

Path A · summary copy

Add the Summary

From the call window, Add summary to Reference Library confirms sharing a copied summary with the team. An Only me original can remain private.

  1. Review the meeting summary.
  2. Choose Add summary to Reference Library and confirm sharing.
  3. The attributed copy joins the library; the original can stay private.

Path B · reference document

Write a Reference Document

For a tailored reference document, use eligible project calls in writing. A supported path is to generate a blueprint-based document, review it, mark it Ready and choose Add to Reference Library, subject to permissions.

  1. Create from eligible project calls.
  2. Review and edit.
  3. Mark Ready.
  4. Add to Reference Library.

A whole call can also be deliberately filed in Reference Library after confirmation.

These are explicit user actions, not continuous synchronization. Copied summaries and call-derived reference material preserve provenance and do not become authoritative company facts simply by entering the library.

05 · External asks

External Asks Take a Separate, Opt-in Path

Selected customer and prospect conversations can inform the launch’s messaging and enablement needs. In the call-processing workflow, external asks become Follow-ups with matching readable content attached first. The same unmet request from 3 or more different companies within 30 days can suggest a new gap plan when no matching content exists.

  • Keep external requests distinct from internal commitments to create content.
  • Use relevant conversation evidence alongside approved product information when creating or revising a draft.
  • Preserve whose experience supports a point rather than treating one participant’s statement as a market-wide fact.

Internal · Team meetings & 1:1s

Commitments Become New Plans

Still-standing commitment → new Pending plan.

Existing readable content is checked first. Tentative ideas and requests to send existing content should not create new work.

External · Customer & prospect calls

Asks Become Follow-ups

Illustrative toggle; no calls are processed.

  1. Ask from a customer or prospect.
  2. Match existing readable content first.
  3. Draft a Follow-up for review.
  4. Gap suggestion if unmet across 3 companies in 30 days.

06 · Evidence & source choice

Control Which Calls Inform Your Writing

Choose the Calls That Belong in This Draft

File calls with a project or collection, or keep them in Calls. In the content form, the Calls source starts with the last 30 days. Choose 7, 30 or 90 days, Any date or a custom range, and filter by kind or company. You can explicitly include older calls.

Marcora selects relevant summaries and transcript passages, not every stored transcript. This source-selection default is separate from the enhanced 30-day-default grounding engine that is still in development.

Illustrative source controls

Selected: Last 30 days. Example only; no source query is run.

Keep Customer Experience Separate From Company Facts

A call can appear among a claim’s supporting sources. When a claim rests only on calls, a caution note distinguishes a customer’s experience from company fact. Today, grounding rarely confirms a claim from a conversation. Review what was said and keep its limits clear.

Grounding does not link to the supporting transcript passage. An improved engine, including 30-day recent-call grounding and passage-level attribution, remains in development.

Keep Who Said What Attached

Speaker names help you follow the conversation. Participant and company details help distinguish internal from external calls, label the company and filter for relevant conversations. Customer classification can draw on vendor CRM evidence or the conversation itself, and you can correct details.

Available metadata depends on the source. An external participant is not automatically a customer or prospect. The planning workflow uses available participant details conservatively when suggesting who should own a content plan. Google Meet does not provide participant emails or attendance. A Wispr recording shared with you supplies attendee names only, without emails, internal/external labels or automatic company details.

One Workflow From Connected Meeting to Content Plan

Scheduled import execution is available for all five Beta providers.

Start with a meeting from a supported connection. Choose calls and filing for the project, or define an import rule in Workflows. Fathom, Gong, Fireflies, Google Meet and Wispr Flow rules can run on selected days and times or use as-ready polling every 15 minutes. Run now is also available. See Only me handling.

Filters determine which calls belong in the workflow. The first run uses a recent 14-day discovery window; as-ready is polling, not instant push.

Privacy · Available

Keep Sharing Deliberate

Calls start as Only me. Automatic imports stay Only me, regardless of the rule’s audience, for every Google Meet call, any Wispr recording shared with you, and any provider’s call with 2 or fewer speakers or a speaker the app does not list. The owner controls sharing, and Team visibility does not override a private project or collection. Eligible private drafts can use their owner's call context; broader use requires the relevant confirmation. Filing a call in the Reference Library does not turn a participant's experience into an approved company fact.

Illustrative audience control. Calls default to Only me.

Already Have a Transcript? Add It Directly

Paste or upload an existing transcript when a connected source is not the intake you need. Marcora parses speaker turns and timestamps, prepares a summary and lets you review the call details and filing. Put the call with the project it should inform.

This is an alternative intake path. Marcora imports transcripts; it does not record meetings. Summaries use Studio Credits and may still be processing while a transcript is usable.

Context layer

Part of Your Shared Context

Use meeting context alongside Brand Foundation, your Reference Library and project context.

FAQ

Questions About Call Transcripts

Which meeting sources can I use?

Fathom, Gong, Fireflies, Google Meet and Wispr Flow offer Beta call imports and scheduled import rules. Meet cannot filter calls by attendee; Wispr Flow supports calendar-backed attendance for recorded meetings. You can also paste or upload a transcript as a secondary intake path.

Can calls arrive automatically?

Yes. Scheduled execution is available for Fathom, Gong, Fireflies, Google Meet and Wispr Flow. Use filters and filing to choose the calls you need. As-ready polls every 15 minutes; selected days/times and Run now are also available. The first run uses a recent 14-day discovery window.

Does automatic processing create plans or recommend document updates?

The call processor suggests new plans and matches existing readable content first. It does not identify a target document and recommend an update. You can explicitly use the conversation when creating or revising writing yourself.

Do I have to accept a plan before generating content?

No. The board uses Pending, Accepted and Produced. Generate can run directly from a saved Pending or Accepted plan; any edited fields are saved first, and a failed save prevents generation. Produced means new content exists, not that it was published externally.

How do meeting details reach Reference Library?

Use an explicit action: add a copied call summary with confirmation, deliberately file a whole call, or create a reference document using eligible project calls. A supported document path is a blueprint-generated document marked Ready, followed by Add to Reference Library. These actions do not continuously sync or automatically overwrite existing library documents.

How do internal and external content needs differ?

When content-needs processing is enabled, internal commitments can suggest new plans; external asks become Follow-ups and are checked against readable existing content first. The same unmet request from 3 or more different companies within 30 days can suggest a gap plan when no matching content exists. These suggestions do not automatically revise an existing document or publish content.

How does grounding handle conversation evidence?

A call can be listed among a claim’s supporting sources, but it represents a customer’s experience, not company authority. Claims supported only by calls receive a caution note. Detection from conversations is limited today: grounding rarely confirms those claims and does not link to the supporting passage. An improved engine is in development.

Who can see a call or a copied summary?

Calls default to Only me, and the owner controls sharing. Automatic imports stay Only me, regardless of the rule’s audience, for every Google Meet call, any Wispr recording shared with you, and any provider’s call with 2 or fewer speakers or a speaker the app does not list. Team visibility does not bypass private containers. Adding a summary to Reference Library confirms a team-visible copy while the original can remain private. Calls and copied summaries remain conversation evidence.

Put the Meeting Behind Your Next Piece of Content

Start with a conversation that matters, keep it in the right project and carry its decisions into your planning and writing.