Articles in this section

[Admin Guide] Create and Update Content from Your Teams Calls with the AI Content Builder

Turn what was said on a Teams call into reusable content for your whole team, and keep that content current as deals move. The AI Content Builder lets you attach a call as context, then generate new content or update existing content grounded only in what was actually said. It works with your synced Microsoft Teams and Gong calls, with transcript files you upload from tools like Zoom, Otter, or Chorus, and on Deal Room templates the whole team uses.

ℹ️ Who this is for: Experts and Account Admins creating and updating team content, including shared templates. Viewers with Deal Room access can also create and update content inside their own Deal Rooms. See [Rep Guide] Create and Update Deal Room Content from Your Teams Calls.

 

1. Attach a Teams call as a source

Every task in this article starts the same way. Attach the call first, then prompt. Grounding the AI in a real conversation is what keeps it from filling gaps with general knowledge.

  1. Open the AI Content Builder and stay on the Create tab.
  2. Select + Add context sources.
  3. Choose Transcripts.
  4. Your recent calls are listed already. Search your calls if the one you want is older.
  5. Hover the call you want and select + Add. Teams calls carry the Teams icon, Gong calls carry the Gong icon.

ℹ️ Note: you can attach 1 transcript at a time. The panel says Max 1 transcript above the list.

If the call you need is not there, select Upload transcript under Don't see the call you need? and upload a .txt file.

Source button What it attaches
Transcripts A synced Teams or Gong call, or a transcript file you upload
Spekit Existing content from your Spekit library
Web A public web page

 

2. Create new content from a call

Start from a blank Spek and let the AI draft it from the call, so you are editing a real first draft instead of a blank page.

  1. Open the Spekit Hub (Web App).
  2. Select + New, then Create a Spek.
  3. Open the AI Content Builder.
  4. Attach the Teams call, using section 1.
  5. Type your request in the prompt box and send it.

The prompt box holds up to 1700 characters, so there is room to be specific.

💡 Pro Tip: the editor has a Doc and Slides toggle in its header. Decide which one you want before you prompt, so the draft comes back in the right shape.

 

3. Update existing content from a call

When a Spek already exists and only needs to reflect what changed on a recent call, ground the AI in that call and let it update what you have.

  1. Open the content in Spekit and select Edit.
  2. Open the AI Content Builder.
  3. Attach the Teams call, using section 1.
  4. Prompt it to update the content, naming what changed. For example: "Update the pricing section of this Spek with the volume discount the buyer asked about on this call, and change the timeline to the new security review date."
  5. Review the changes, then save.

💡 Pro Tip: name the sections you want changed. A blanket "update this based on the call" lets the AI rewrite parts that were already correct, which gives you more to review and more to undo.

 

4. Update a template with recent call data

Use this to start from a saved template and fill it in with call details, like refreshing a follow-up template after a meeting.

  1. Select + New, then Spek.
  2. Choose the template you want, then select + Use this template.
  3. Attach the Teams call, using section 1.
  4. Prompt it to update, for example: "Edit the existing content using the attached meeting details. Update relevant sections with the latest information, replace outdated details, and preserve the existing structure and formatting."
  5. Review the changes, then save.

⚠️ Templates are shared. Edits to a template affect everyone who uses it. Review carefully before saving a template change.

 

5. Prompt examples

Once a call is attached, prompts like these work well. The first set creates new content, the last 2 update content you already have.

  • "Based on the transcript, extract the top 3 pain points the prospect mentioned and draft a Discovery Recap Spek for this account."
  • "Search the transcript for budget or timeline mentions. Draft a Deal Risk summary highlighting any red flags."
  • "Create a Next Steps Spek that lists every commitment made by both the rep and the prospect during this conversation."
  • "Find the moment the rep was asked about pricing. Rewrite their response into a polished Pricing Objection Handler for the rest of the team."
  • "Identify any questions the rep could not answer. Create a Knowledge Gap Spek that provides those answers for the next call."
  • "Analyze the discovery questions asked in this transcript. Create a Stage 1 Playbook of the 5 most effective questions that got the customer talking."
  • "Extract any product feature requests the customer mentioned and format them into a Product Feedback Spek."
  • "Update this Spek with the new objection the prospect raised on today's call and how the rep handled it."
  • "Rewrite this Deal Room follow-up template using the next steps and timeline we agreed on in the call."

💡 Pro Tip: ask for 1 clear output at a time, and name the format you want, like a Spek titled "Discovery Recap". Specific requests produce cleaner content than a vague "summarize this".

 

6. Use cases

These are the patterns that turn 1 call into something the whole team uses.

Use case What to do
A great objection handled well Turn the rep's answer into a Pricing Objection Handler for everyone
The same question across several calls Build a reusable Spek once, rather than answering it deal by deal
A technical explanation a specialist gave Ask for it simplified into a how-to for a non-technical audience
Questions nobody could answer Create a Knowledge Gap Spek so the next call goes better
A discovery call that went well Draft a Stage 1 Playbook from the questions that got the buyer talking

 

7. Best practices

These 6 habits are the difference between a usable draft and one you rewrite by hand.

Best practice Why it matters
Attach the call before you prompt Grounding the AI in the real conversation keeps it from filling gaps with general knowledge
Be specific about format and focus Name the format and the focus, rather than asking for a vague summary
Ask for 1 output at a time A single clear ask beats a long list in 1 prompt
When updating, say what changed Name the objection, timeline, or next steps to change, rather than a blanket "update it"
Review shared content before saving You own the final content, and template edits affect everyone
Turn recurring call themes into team content When the same objection shows up across calls, build a Spek so the whole team benefits

 

8. Common questions

Does this work the same for Teams calls and Gong calls? Yes. Both appear in the same Recent calls list, each with its own icon.

Can I attach more than 1 call? No. The panel allows Max 1 transcript at a time.

My call is not in the list. What now? If it is recent, search for it. If it never arrived in Spekit, see Troubleshooting the Microsoft Teams Integration. You can also upload the transcript as a .txt file.

Can Viewers do this? Inside their own Deal Rooms, yes. For content used across the team, that is an Expert or Account Admin task.

Does the AI ever get it wrong? It can. The panel says so under the prompt box. Read before you save.

Was this article helpful?
0 out of 0 found this helpful