Call Summary Generator

Takes your raw, unstructured post-call notes and turns them into a structured summary. The input can be messy -- bullet points, fragments, stream-of-consciousness. The output is clean and actionable.

Different from the follow-up email (customer-facing) and the meeting outcome log (CRM-facing) -- this is the comprehensive record for your own reference and your team's context.

How to Use

After a call, provide:

• Your raw notes (however messy -- the skill structures them)
• Who was on the call (customer and internal)
• Call duration and type
• Anything you want to highlight or flag

What It Produces

Discussion Points (What Was Covered)

Organises the conversation into distinct topics, each with:

• Topic name
• What was discussed (2-3 sentences)
• Conclusion or outcome (if any)
• Open questions (if the topic was not resolved)

Decisions (What Was Agreed)

Explicit agreements from the call:

• What was decided
• Who decided (consensus, or one person's call)
• Any conditions or caveats

Action Items (Who Committed to What)

Extracted from the notes using the same patterns as the action-item-extractor:

Sentiment Assessment

Based on your notes and observations:

• Overall: positive / neutral / negative / mixed
• Specific signals: what you noticed about the customer's energy, engagement, specific statements
• Shift: did the sentiment change during the call? (Started positive, turned negative during the pricing discussion)

Flags

Signals that should trigger downstream attention:

• Risk flags: Frustration expressed, competitive mention, budget concern, disengagement signals
• Expansion flags: Growth interest, new team mentions, feature requests indicating deeper adoption
• Product flags: Feature requests, bug reports, integration needs
• Relationship flags: Champion sentiment change, new stakeholder identified, political observation

Output Format

## Call Summary: [Account Name]
**Date:** [date] | **Type:** [type] | **Duration:** [minutes]
**Attendees:** [customer contacts] | [internal team]

### Discussion Points
1. **[Topic]**: [2-3 sentence summary]. Conclusion: [outcome or "open"]
2. **[Topic]**: [2-3 sentence summary]. Conclusion: [outcome or "open"]

### Decisions
- [Decision 1]
- [Decision 2]

### Action Items
| Action | Owner | Deadline | Confidence |
|--------|-------|----------|-----------|
| [action] | [name] | [date] | [H/M/L] |

### Sentiment
Overall: [assessment]
Signals: [specific observations]

### Flags
- [Risk/Expansion/Product/Relationship]: [detail]

### Next Touchpoint
[When and what]

Handling Messy Input

The skill works with various input quality levels:

Quality Gates

• Are all action items extracted? Scan the raw notes for commitment language ("I will," "we will," "let's") and confirm each one appears in the action item table
• Is the sentiment assessment honest? "Positive" because no one complained is not the same as "positive" because the customer expressed enthusiasm. Label the evidence
• Are flags captured? A competitive mention buried in paragraph 3 of your notes should appear as a flag in the summary, not disappear into the narrative
• Could someone who was not on the call understand the summary? That is the bar. Your manager, your successor, your colleague covering your accounts while you are on leave -- they should be able to read this and know what happened

Principles

• Write the summary within 1 hour. The quality of your recall degrades exponentially. Notes written the same day are 3x more accurate than notes written the next day
• The summary is a thinking tool, not just a documentation tool. The act of structuring your notes forces you to process what happened: what was the most important topic? What did the customer really mean? What did I commit to? The structure creates clarity that raw notes do not
• Err on the side of capturing too much. You can always trim a comprehensive summary. You cannot reconstruct a missing observation 2 weeks later. When in doubt, include it
• The flags section is the highest-value part for downstream use. The discussion points are for you. The flags are for the system -- they trigger risk reviews, expansion conversations, and product feedback loops