Call Summary

1---2name: call-summary3description: Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.4argument-hint: "<call notes or transcript>"5---6 7# /call-summary8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Process call notes or a transcript to extract action items, draft follow-up communications, and update records.12 13## Usage14 15```16/call-summary <notes or transcript>17```18 19Process these call notes: $ARGUMENTS20 21If a file is referenced: @$122 23---24 25## How It Works26 27```28┌─────────────────────────────────────────────────────────────────┐29│                      CALL SUMMARY                                │30├─────────────────────────────────────────────────────────────────┤31│  STANDALONE (always works)                                       │32│  ✓ Paste call notes or transcript                               │33│  ✓ Extract key discussion points and decisions                  │34│  ✓ Identify action items with owners and due dates              │35│  ✓ Surface objections, concerns, and open questions             │36│  ✓ Draft customer-facing follow-up email                        │37│  ✓ Generate internal summary for your team                      │38├─────────────────────────────────────────────────────────────────┤39│  SUPERCHARGED (when you connect your tools)                      │40│  + Transcripts: Pull recording automatically (e.g. Gong, Fireflies) │41│  + CRM: Update opportunity, log activity, create tasks          │42│  + Email: Send follow-up directly from draft                    │43│  + Calendar: Link to meeting, pull attendee context             │44└─────────────────────────────────────────────────────────────────┘45```46 47---48 49## What I Need From You50 51**Option 1: Paste your notes**52Just paste whatever you have — bullet points, rough notes, stream of consciousness. I'll structure it.53 54**Option 2: Paste a transcript**55If you have a full transcript from your video conferencing tool (e.g. Zoom, Teams) or conversation intelligence tool (e.g. Gong, Fireflies), paste it. I'll extract the key moments.56 57**Option 3: Describe the call**58Tell me what happened: "Had a discovery call with Acme Corp. Met with their VP Eng and CTO. They're evaluating us vs Competitor X. Main concern is integration timeline."59 60---61 62## Output63 64### Internal Summary65```markdown66## Call Summary: [Company] — [Date]67 68**Attendees:** [Names and titles]69**Call Type:** [Discovery / Demo / Negotiation / Check-in]70**Duration:** [If known]71 72### Key Discussion Points731. [Topic] — [What was discussed, decisions made]742. [Topic] — [Summary]75 76### Customer Priorities77- [Priority 1 they expressed]78- [Priority 2]79 80### Objections / Concerns Raised81- [Concern] — [How you addressed it / status]82 83### Competitive Intel84- [Any competitor mentions, what was said]85 86### Action Items87| Owner | Action | Due |88|-------|--------|-----|89| [You] | [Task] | [Date] |90| [Customer] | [Task] | [Date] |91 92### Next Steps93- [Agreed next step with timeline]94 95### Deal Impact96- [How this call affects the opportunity — stage change, risk, acceleration]97```98 99### Customer Follow-Up Email100```101Subject: [Meeting recap + next steps]102 103Hi [Name],104 105Thank you for taking the time to meet today...106 107[Key points discussed]108 109[Commitments you made]110 111[Clear next step with timeline]112 113Best,114[You]115```116 117---118 119## Email Style Guidelines120 121When drafting customer-facing emails:122 1231. **Be concise but informative** — Get to the point quickly. Customers are busy.1242. **No markdown formatting** — Don't use asterisks, bold, or other markdown syntax. Write in plain text that looks natural in any email client.1253. **Use simple structure** — Short paragraphs, line breaks between sections. No headers or bullet formatting unless the customer's email client will render it.1264. **Keep it scannable** — If listing items, use plain dashes or numbers, not fancy formatting.127 128**Good:**129```130Here's what we discussed:131- Quote for 20 seats at $480/seat/year132- W9 and supplier onboarding docs133- Point of contact for the contract134```135 136**Bad:**137```138**What You Need from Us:**139- Quote for 20 seats at $480/seat/year140```141 142---143 144## If Connectors Available145 146**Transcripts connected (e.g. Gong, Fireflies):**147- I'll search for the call automatically148- Pull the full transcript149- Extract key moments flagged by the platform150 151**CRM connected:**152- I'll offer to update the opportunity stage153- Log the call as an activity154- Create tasks for action items155- Update next steps field156 157**Email connected:**158- I'll offer to create a draft in ~~email159- Or send directly if you approve160 161---162 163## Tips164 1651. **More detail = better output** — Even rough notes help. "They seemed concerned about X" is useful context.1662. **Name the attendees** — Helps me structure the summary and assign action items.1673. **Flag what matters** — If something was important, tell me: "The big thing was..."1684. **Tell me the deal stage** — Helps me tailor the follow-up tone and next steps.