Playbook · 2026

How to analyze call recordings with Claude: step-by-step.

Your calls are full of insight that no one has time to mine. This playbook gives you a prompt template that turns a transcript into objections, action items, and themes.

Short version

Paste a call transcript and tell Claude what you are looking for, then ask for a structured analysis: summary, objections, action items, and notable quotes. You turn a recording into usable insight in minutes, and you can analyze many calls for patterns.

The prompt template

This template extracts the structure buried in a transcript. Use it per call, or paste several transcripts and ask for cross-call patterns.

Copy, paste, and fill in the brackets

You are my revenue and research analyst. Analyze this call transcript. Context: - Call type: [sales discovery / demo / customer interview / support] - What I want to learn: [objections / buying signals / feature requests / churn risk] - Transcript: [paste transcript] Produce: - A 3-sentence summary. - Objections or concerns raised, with the exact quote. - Buying signals or risk signals, with quotes. - Action items and follow-ups. - 2-3 notable quotes in the customer's own words. Rules: only use what is in the transcript, no inference presented as fact. Do not use em dashes.

Quote-backed analysis keeps it honest, and pasting several transcripts surfaces patterns one call cannot. Feed what you learn into follow-up emails and research design.

The step-by-step workflow

Get a clean transcript. Use your meeting recorder (Fathom, Gong, Otter) to export the transcript. Claude analyzes text, so the transcript is your input.
Paste the prompt and transcript. Tell Claude the call type and exactly what you want to learn. Specific questions get specific, useful answers.
Ask for quotes, not just summaries. Quote-backed findings keep the analysis honest and let you verify. The template requires exact quotes for each point.
Run it across many calls for patterns. Paste several transcripts and ask for the objections and signals that repeat. That cross-call view is where the strategic insight lives.
Turn insight into action, then save the prompt. Route action items to owners and patterns to product or marketing. Save the prompt so every call gets analyzed the same way.

A worked example

Paste a discovery-call transcript and ask for objections and buying signals. Claude returns the exact objection quotes, the moments of interest, the action items, and a few customer-voice quotes, turning a 40-minute call into a one-screen brief, and across 20 calls it surfaces the objection you keep losing on.

What to avoid

Presenting inference as fact. Require quotes so findings are grounded in what was actually said.
Pasting sensitive recordings into tools without appropriate data agreements and consent.
Analyzing one call and generalizing. Patterns come from many transcripts, not one.
Skipping the human read. Use the analysis to focus your attention, not replace your judgment.

Frequently asked questions

Can Claude analyze a sales call?

Yes, from the transcript. Paste it and ask for objections, buying signals, action items, and quotes. The template here keeps every finding tied to an exact quote.

How do I get a transcript for Claude?

Export it from your meeting recorder (Fathom, Gong, Otter, or similar). Claude works on the text, so a clean transcript is all you need.

Can Claude find patterns across many calls?

Yes, and that is the highest-value use. Paste multiple transcripts and ask for the objections, requests, or risks that repeat across them.

Is it safe to analyze customer calls with AI?

Use appropriate data agreements and ensure recording consent. Keep sensitive transcripts in tools with the right privacy terms, not random consumer apps.