Call Transcript Follow-Up

When to Use This Skill

Load this skill when the user:

• Pastes or attaches a raw call or meeting transcript
• Shares meeting notes and asks for a structured summary
• Asks to extract action items, decisions, or takeaways from a conversation
• Needs a post-call package for a client, customer, vendor, partner, candidate, or internal stakeholder meeting
• Is in a sales, business development, or account-management context and needs to document a prospect or customer call
• Just finished a discovery call, kickoff, status meeting, working session, or reference check and needs to send follow-ups

This skill applies to any conversation that produces commitments: sales and BD calls, client and customer check-ins, consulting engagements, project status meetings, vendor negotiations, recruiting debriefs, partnership discussions, and internal cross-functional syncs — in any industry.

Inputs

The user may provide:

• A raw transcript (from a recording tool, a note-taking app, or pasted text)
• Meeting notes
• Speaker names
• Client, customer, or company name
• Context about the relationship or meeting goal

If context is missing, infer carefully from the transcript but do not invent facts. If the transcript is clearly a fragment, say so at the top and work with what is there — do not ask for more unless the fragment is unusable.

Core Instructions

When given a transcript, produce a post-call package using the structure below.

1. Meeting Snapshot

Summarize the basic context:

• Meeting topic:
• Participants:
• Date: Use only if provided
• Purpose of the call:
• Overall outcome:

If any of these are unclear, write Not specified.

2. Executive Summary

Write a concise 5–8 bullet summary of the conversation.

Focus on:

• What was discussed
• What mattered most
• Any decisions made
• Any commitments made
• Any next steps
• Any tensions, blockers, or unresolved issues

Avoid generic filler. Prioritize what a busy executive, sponsor, or team lead would need to know.

3. Key Takeaways

Extract the most important strategic, commercial, or operational takeaways.

Use this format:

• Takeaway: [Clear statement]
  • Why it matters: [Business implication]

Include 3–7 takeaways depending on transcript length.

4. Decisions Made

List explicit decisions only.

If no clear decisions were made, write:

No explicit decisions were made in the transcript.

5. Action Items

Extract concrete follow-ups.

Rules:

• Do not invent owners.
• If the owner is implied but not explicit, write Likely owner: [name].
• If no due date is mentioned, write Not specified.
• Separate actual commitments from vague possibilities ("we should probably..." is not an action item unless someone owned it).
• Do not include generic "follow up" items unless the transcript supports them.
• Split "our side" and "their side" items when the call was between two organizations — the user usually only controls one column.

6. Open Questions

List unresolved questions that need clarification.

• Question: [Question]
  • Why it matters: [Impact on next step or decision]

7. Risks, Blockers, or Watchouts

Identify any risks, blockers, or ambiguity. Examples:

• Misalignment between participants
• Unclear ownership
• Missing data
• Legal, compliance, procurement, or approval dependencies
• Timeline risk
• Budget uncertainty
• Technical feasibility concerns
• A stakeholder who was mentioned but not in the room

If none are apparent, write:

No major risks or blockers were apparent from the transcript.

8. CRM / Tracker Note

Add a short CRM-style note for sales, consulting, account-management, recruiting, or partnership conversations — anything that lives in a pipeline or relationship tracker. For internal meetings, use the same format as a project-tracker note.

Use this format:

CRM Note: [3–5 sentence summary of the relationship, the counterpart's need, the opportunity or project status, the next step, and any relevant timing.]

Quality Bar

The final output should feel like it was prepared by a sharp chief of staff after sitting in the meeting. It should be:

• Concise
• Accurate
• Action-oriented
• Easy to skim
• Careful about uncertainty
• Ready to paste into a CRM, ticketing system, or project tracker

Guardrails

• Do not fabricate facts, dates, names, numbers, or commitments.
• Distinguish between what was explicitly said and what is inferred.
• Preserve uncertainty where the transcript is ambiguous.
• Do not include sensitive personal details unless directly relevant to the business purpose of the call.
• Do not quote long passages from the transcript unless specifically asked.
• Do not editorialize about participants' competence or intent; report what was said and what it implies for next steps.

Example prompts

"Here's the Zoom transcript from our discovery call with a regional hospital's procurement team. Process this call — I need action items for my side and theirs, and a CRM note."

"Paste of my notes from the agency kickoff with the new client. What did we actually decide, and what's still open?"

"This is the auto-generated transcript from a customer interview for our onboarding redesign. Pull the takeaways and any commitments we made."