Integrations · Call transcripts
Marcora + Gong
Use selected Gong conversations to inform an enablement or campaign content plan. Bring customer questions into the project alongside approved product information.
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
Why this source
Plan Enablement Around the Questions People Ask
Let selected objections and competitive questions inform which enablement assets are useful. Keep external asks distinct from the team’s internal commitments, then use the conversation when writing the response.
How it works
Start With the Objections People Actually Raised
Start with the enablement question or campaign, then select the calls that can inform its content needs.
1. Connect Gong 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 Gong 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 Gong
Can I import Gong calls now?
The Gong 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 Gong 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 →Does this sync the whole Gong library or write back to Gong?
Selected imports bring in the calls you choose, and import rules can collect matching calls on a schedule. This does not imply indexing every call or writing content back into Gong.
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 Gong Conversations to Work
Start with the conversations that matter to your next piece of content.