> ## 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

**1. 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.

**2. 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.

**3. 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.

**4. You review and send**

Read the recap, adjust anything, then approve it through Klipy's gated send handshake. It sends only when you confirm.

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](https://klipy.ai/docs/guides/meeting-notetaker.md).
* **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](https://klipy.ai/docs/guides/mcp/use-cases/crm-updates.md).

## Related

> [card] [Follow-up emails](https://klipy.ai/docs/guides/mcp/use-cases/follow-up-emails.md)
>
> Draft a shorter, momentum-keeping follow-up from the same call.

> [card] [CRM updates](https://klipy.ai/docs/guides/mcp/use-cases/crm-updates.md)
>
> Accept the next steps so your CRM reflects the meeting.

> [card] [Tool reference](https://klipy.ai/docs/guides/mcp/tools.md)
>
> Every tool Claude can call, grouped by scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.