> ## 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 draft a follow-up after a call?

> Ask Claude to draft a follow-up email after a sales call or meeting, grounded in the transcript and the deal's history — you review and send.

The best follow-up window is the few minutes right after a call — while the conversation is still specific. That is exactly when you are onto the next thing, and the follow-up gets pushed to "later," where it turns generic. Connect Claude to Klipy and it drafts the follow-up from what was actually said, ready for you to review and send.

## Example prompt

Copy this into Claude once it is connected to Klipy:

```text theme={null}
Pull up my most recent call with Sarah from Northwind and draft a
follow-up email that references what we actually discussed and the
next step we agreed on.
```

## What happens

<Steps>
  <Step title="Claude reads the meeting">
    Claude calls `get_meeting_transcript` to read the transcript and the meeting's participant summary, so the follow-up is built on the real conversation — not your memory of it.
  </Step>

  <Step title="It checks the wider history">
    Claude calls `search_interactions` to pull related email and meeting context for the same contact, so the draft picks up threads from before this one call.
  </Step>

  <Step title="It prepares a draft">
    Claude calls `draft_email_message` to create a suggested email. This does not send anything — the draft waits in Klipy for your review.
  </Step>

  <Step title="You review and send">
    Open the draft, edit anything you want, then approve it through Klipy's gated send handshake. Sending only happens when you confirm.
  </Step>
</Steps>

Tokens are consumed only when you accept the send — reading the transcript and preparing the draft are free.

## Good to know

* **A connected email account is required.** `draft_email_message` needs a mailbox connected to Klipy. Without one, it returns a blocked status with guidance instead of a draft. [Connect email and calendar](/docs/guides/connecting-email-calendar) first.
* **The recipient must already be a contact.** The first `to` address has to match an existing CRM contact. If the person from the call is not in your CRM yet, add them first.
* **Transcripts come from recorded meetings.** If the call was not recorded by Klipy's notetaker, there is no transcript to ground the draft — Claude can still work from email history via `search_interactions`.

## Related

<CardGroup cols={2}>
  <Card title="Meeting recaps" icon="file-text" href="/docs/guides/mcp/use-cases/meeting-recaps">
    Turn the same meeting into a structured recap and next steps.
  </Card>

  <Card title="Cold deal outreach" icon="flame" href="/docs/guides/mcp/use-cases/cold-deal-outreach">
    Re-engage deals that went quiet, one personal note at a time.
  </Card>

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