What it does
This skill takes a call transcript (or the rep's raw notes when there is no recording) and fills a sales call summary template with what actually happened: the outcome in one sentence, what the buyer said with the speaker named, commitments in both directions with dates, risks and how they were handled, and a CRM field block the rep can paste without editing. The job it replaces is the update a rep types three hours later from memory, where the buyer's hedged 'we'd probably need to look at budget' becomes 'budget confirmed' in the next-step field, and nobody catches it until the forecast call.
The bad version of a call summary is a paragraph of narrative that reads like the rep's diary: what they pitched, how it went, a feeling about the deal. The good version is a structured record where every line traces back to the transcript, buyer words are separated from rep words, and the CRM fields carry a Confirmed or Inferred tag so RevOps can tell the difference between 'the VP said she owns the budget' and 'the rep thinks she does'. The skill enforces that split. It also refuses to invent a next-step date when none was agreed, which is the single most common way a pipeline gets polluted.
It beats doing it by hand for the reason every RevOps lead already knows: comparability. When ten reps write ten different summaries, the pipeline review is ten separate conversations and the CRM fields mean ten different things. When the same skill fills the same template from every transcript, a manager can read twenty deals in ten minutes, the framework fields in the CRM actually match what the buyer said, and a stalled deal looks stalled instead of looking like a rep with a terse writing style. It also runs the moment the recorder finishes, so the follow-up email and the CRM update happen while the call is still warm and the rep still remembers the tone behind the words.
Where it does not help: garbage in, garbage out. If there is no recording and the rep's notes are three bullets, the skill will say so, tag nearly everything Inferred, and recommend holding the stage rather than advancing on unverified notes. It cannot recover what the buyer meant from what the rep remembers. It also does not write to the CRM by itself unless you have wired that up deliberately, and we recommend you keep a human approving the field block before it lands, at least for stage and close-date changes. Auto-drafting is the win; auto-writing without review is how a hedged maybe becomes a committed forecast.
The sales call summary template
This is the structure the skill fills after every call. Copy it into your notes tool, or paste it as the format instruction when you run the skill. The rule that makes it work: the top half is buyer words, the field block is only what the buyer confirmed, and anything the rep inferred carries a tag so RevOps can see it before it becomes CRM fact.
CALL SUMMARY, {{DEAL}}, {{call date}}
Attendees: {{buyer names, titles}} | Rep: {{name}}
Outcome: {{one sentence: what changed for the deal because this call happened}}
WHAT THE BUYER SAID (buyer statements only, speaker named)
- {{Name}}: {{paraphrase}}
- {{Name}}: {{paraphrase}}
COMMITMENTS
- Us: {{what}}, by {{date / no date agreed}}
- Them: {{what}}, by {{date / no date agreed}}
RISKS / OBJECTIONS
- {{objection}} -> {{how handled / not addressed}}
CRM FIELD BLOCK (paste as-is)
Stage recommendation: {{Advance to X / Hold at Y}} ({{evidence}})
Next step: {{literal next step}}
Next step date: {{date / not agreed}}
Close date: {{keep / move to date}} ({{why}})
{{Framework field}}: {{value}} [Confirmed / Inferred]
{{Framework field}}: {{value}} [Confirmed / Inferred]
TO-DO, BY DEADLINE
1. {{owner}}: {{task}}, {{date}}
2. {{owner}}: {{task}}, {{date}}If a section is empty, write "not discussed" and leave it. An empty Commitments block after a 45-minute call is itself the finding: the call ended without a next step, and the CRM should say so.
Inputs & outputs
Inputs
- The call transcript from your recorder (Gong, Fireflies, Fathom, or a pasted export), or the rep's raw notes if no recording exists (required)
- Deal name and current stage
- The CRM fields you want filled (default: next step, next step date, close date, stage recommendation, MEDDICC fields)
- Optional: the previous call summary, so commitments carried over can be checked
- Optional: your stage definitions, so the stage recommendation follows your rules rather than generic ones
Outputs
- A sub-200-word summary: outcome, what the buyer said (speaker named), commitments both ways with dates, risks with how each was handled
- A CRM field block ready to paste: stage recommendation with evidence, next step and date, close date with the reason it moved or held, framework fields each tagged Confirmed or Inferred
- A to-do list ranked by deadline, owner first
- An explicit "not discussed" or "no date agreed" wherever the call left a gap, instead of a guessed value
How to set it up
Decide where the skill lives
Two setups. (1) In claude.ai, create a Project called "Call Notes", paste the SKILL.md body below into custom instructions, and add a line with your framework and stage names: "We run MEDDICC. Stages: Discovery, Evaluation, Proposal, Negotiation." Reps drop a transcript in and get the summary. (2) In Claude Code, save it as skills/call-summary-to-crm/SKILL.md; this is the route if you want an agent to pick up every new transcript from your recorder and draft the summary automatically, as in the post-call follow-up use case.
Paste the transcript, not your notes, into the sales call summary template
The skill is built to prefer buyer words over rep words, and it can only do that if it can see who said what. Export the transcript from your recorder with speaker labels and paste the whole thing. If you only have notes, say so; the skill will run, tag the output as note-derived, and recommend holding the stage until a recorded call confirms the commitments. That is the correct behavior, not a failure.
Review the Inferred tags, then paste the field block
Scan the CRM field block for [Inferred] before you paste. Each one is a place where the rep's read of the call is about to become a CRM fact. Either you have the evidence and can flip it to Confirmed, or you leave the tag and RevOps sees it in the record. Do not delete the tags to make the record look cleaner; the tags are the point. Then paste the block into the deal, or, if you have wired HubSpot or Salesforce over MCP, have the agent write it and post the diff to the rep for approval.
Chain it into the follow-up and the scorecard
The summary is the raw material for two other things. The commitments section is the skeleton of the follow-up email (the post-call follow-up use case drafts it from the same transcript). The framework fields feed the deal-qualification-scorer skill, which turns a stack of these summaries into a scored deal review. Run all three off one transcript and the rep's post-call work drops to reading and approving.
The SKILL.md
Save this as SKILL.md in a folder named call-summary-to-crm, or paste the body into a Claude Project. Then paste a transcript and the deal name.
---
name: call-summary-to-crm
description: Use right after a sales call, when a transcript or the rep's raw notes exist and the CRM needs updating. Turns the call into a structured sales call summary (outcome, what the buyer said, commitments, risks, next step with a date) plus a CRM-ready field block (stage recommendation, next step, close date, MEDDICC or BANT field updates) and a ranked to-do list. Every claim traces to the transcript; nothing is inferred into the CRM without a tag.
---
# Call Summary to CRM
You turn one sales call into a 60-second summary and a field block a rep can paste into the CRM unedited. The transcript is the only source of truth. Never add what was not said.
## Inputs
- The call transcript, or the rep's raw notes if no recording exists (required).
- Deal name, current stage, and the CRM fields to fill (default: next step and date, close date, stage recommendation, MEDDICC fields).
- Optional: the previous summary, the framework in use.
## Method
1. Read the whole transcript first. Note speakers and titles.
2. State the outcome in one sentence: what changed for the deal because this call happened.
3. Extract what the buyer said as short paraphrases, speaker named. Buyer statements only; the rep's pitch is not a finding.
4. Extract commitments both ways: who promised what, by when. No date said = "no date agreed".
5. List risks and objections, each with how it was handled or "not addressed".
6. Fill the CRM field block from buyer confirmations only. Tag rep inferences [Inferred] for review.
7. Recommend a stage move only if the transcript holds the evidence the stage requires; otherwise "hold".
8. Write the to-do list ranked by deadline, owner first.
## Hard rules
- Transcript or nothing. No fabricated quotes, names, numbers, or dates. Missing detail = "not discussed".
- Buyer words over rep words. Rep-only claims do not enter the CRM as fact.
- Summary under 200 words. Field block values short and literal.
- Never write to the CRM yourself unless a tool is wired and the user asked; default is a block to paste or approve.
## Output template
**Call Summary: <Deal>, <call date>**
Attendees: <buyer names/titles> | <rep>
Outcome: <one sentence>
**What the buyer said**
- <Name>: <paraphrase>
- <Name>: <paraphrase>
**Commitments**
- Us: <what>, by <date or "no date agreed">
- Them: <what>, by <date or "no date agreed">
**Risks / objections**
- <objection> -> <how handled | not addressed>
**CRM field block**
Stage recommendation: <Advance to X | Hold at Y> (<evidence>)
Next step: <literal next step>
Next step date: <date | not agreed>
Close date: <keep | move to date> (<why>)
<Framework field>: <value> [Confirmed | Inferred]
...
**To-do, by deadline**
1. <owner>: <task>, <date>
2. <owner>: <task>, <date>
Run it from the terminal
Example run
An AE pastes the transcript of a two-stakeholder discovery call and gets the summary plus a paste-ready CRM block, with the economic buyer correctly tagged Inferred.
Prompt: call-summary-to-crm. Deal: Acme Observe, stage Discovery, close 2026-10-15. Framework: MEDDICC. Transcript attached (2026-09-03). We sell an AI SDR that books meetings while reps ramp.
Output:
Call Summary: Acme Observe, 2026-09-03
Attendees: Priya Nair (VP Sales), Tom Ellis (Head of RevOps) | Rep: Sam
Outcome: Acme confirmed the coverage gap is a Q4 priority and agreed to a scoped pilot review, pending a security questionnaire.
What the buyer said
- Priya Nair: five BDRs start 2026-10-01 and she expects a two-quarter ramp; pipeline coverage is "the number I get asked about".
- Tom Ellis: any tool that writes to HubSpot needs a security review first; the last one took three weeks.
- Priya Nair: budget for the pilot would come from the SDR tooling line; she "would need to move some things".
Commitments
- Us: send the security questionnaire pack and a one-page pilot scope, by 2026-09-05.
- Them: Tom to start the security review once the pack arrives, no date agreed.
- Them: Priya to confirm which segment the pilot targets, by 2026-09-10.
Risks / objections
- "We just hired for this." -> handled: pilot feeds the new hires, framed as ramp insurance.
- Security review length -> not addressed; three weeks lands after her 2026-10-01 start date.
CRM field block
Stage recommendation: Advance to Evaluation (buyer agreed to pilot review and named a process)
Next step: Send security pack + pilot scope
Next step date: 2026-09-05
Close date: move to 2026-10-31 (three-week security review pushes past the current 2026-10-15)
Metrics: pipeline coverage ratio during BDR ramp [Confirmed]
Economic Buyer: Priya Nair, SDR tooling line [Inferred, she said "would need to move some things", not that she signs]
Decision Process: security review (Tom) then unknown [Confirmed, partial]
Champion: Priya Nair [Inferred, engaged but has not acted yet]
To-do, by deadline
1. Sam: send security questionnaire pack and pilot scope, 2026-09-05
2. Sam: ask Priya for the segment decision and who signs the order form, 2026-09-10
3. Sam: check in with Tom on review start, 2026-09-12Related plays
- Sales Follow-Up Email Templates, Auto-Drafted From Every Call →The full agent build: transcript in, follow-up email and HubSpot fields out, with a human approving every send.
- Turn Call Notes Into a Follow-Up and Action Plan →The one-off prompt version for when you do not want a persistent skill.
- Claude + Gong integration guide →Getting the transcript to Claude automatically instead of pasting it.
- Claude + HubSpot integration guide →Writing the field block into the CRM over MCP, and the read-write line to hold.