> ## Documentation Index
> Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I recap a recorded meeting?

> Ask Claude to turn a recorded meeting into an accurate recap, surface the next steps Klipy suggested, and draft a recap email you review and send.

A prospect asks you to "send over a recap of what we discussed." Writing an accurate one means you either took perfect notes during the call or you reconstruct it from memory and get a detail wrong. Connect Claude to Klipy and it drafts the recap from the transcript, and surfaces the next steps the meeting left behind.

## Example prompt

Copy this into Claude once it is connected to Klipy:

```text theme={null}
Recap my last meeting with Acme — summarize what we discussed, list the
next steps, and draft a recap email I can send the attendees.
```

## What happens

<Steps>
  <Step title="Claude finds and reads the meeting">
    Claude calls `list_meetings` to locate the recording, then `get_meeting_transcript` to read the full transcript and participant summary.
  </Step>

  <Step title="It surfaces the next steps">
    Claude calls `list_agent_suggestions` to see the next-step actions Klipy already proposed from the meeting — so the recap reflects what Klipy captured, not just a re-read of the transcript.
  </Step>

  <Step title="It drafts the recap email">
    Claude calls `draft_email_message` to prepare a structured recap for review. Nothing sends at this step — the draft waits in Klipy.
  </Step>

  <Step title="You review and send">
    Read the recap, adjust anything, then approve it through Klipy's gated send handshake. It sends only when you confirm.
  </Step>
</Steps>

Tokens are consumed only when you accept the send. Reading the meeting and preparing the draft cost nothing.

## Good to know

* **Recaps come from recorded meetings.** `get_meeting_transcript` needs a recording with a transcript. If the notetaker did not record the call, there is no transcript to summarize. See [Meeting notetaker](/docs/guides/meeting-notetaker).
* **Sending the recap needs a connected email account.** `draft_email_message` requires a connected mailbox and a recipient who already exists as a CRM contact. Without a mailbox it returns a blocked status with guidance.
* **Suggestions are Klipy's proposals, not applied changes.** `list_agent_suggestions` shows pending next-step actions; applying one is a separate, explicit accept step. See [CRM updates](/docs/guides/mcp/use-cases/crm-updates).

## Related

<CardGroup cols={2}>
  <Card title="Follow-up emails" icon="reply" href="/docs/guides/mcp/use-cases/follow-up-emails">
    Draft a shorter, momentum-keeping follow-up from the same call.
  </Card>

  <Card title="CRM updates" icon="database" href="/docs/guides/mcp/use-cases/crm-updates">
    Accept the next steps so your CRM reflects the meeting.
  </Card>

  <Card title="Tool reference" icon="wrench" href="/docs/guides/mcp/tools">
    Every tool Claude can call, grouped by scope.
  </Card>
</CardGroup>