> ## 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 update my CRM from a chat?

> Ask Claude to read a meeting and apply the CRM updates Klipy suggested — you accept each change, so your CRM stays current without manual data entry.

Every call generates work you never do: notes to write up, records to update, next steps to log. That admin debt piles up until your CRM is out of date and effectively useless. Connect Claude to Klipy and it reads the conversation, shows you the updates Klipy already proposed, and applies the ones you accept.

## Example prompt

Copy this into Claude once it is connected to Klipy:

```text theme={null}
Read my last meeting with Acme and show me the CRM updates Klipy
suggested from it. Walk me through them so I can accept the right ones.
```

## What happens

<Steps>
  <Step title="Claude reads the meeting">
    Claude calls `get_meeting_transcript` to read what was discussed — the source the updates are drawn from.
  </Step>

  <Step title="It surfaces Klipy's suggestions">
    Claude calls `list_agent_suggestions` to list the pending CRM and task changes Klipy proposed from the conversation, each awaiting review.
  </Step>

  <Step title="You accept the ones you want">
    For each suggestion you approve, Claude calls `accept_agent_suggestion`, which applies that change to your CRM. You can override fields before it applies. Nothing is applied until you accept it.
  </Step>
</Steps>

Applying a suggestion is a supervised, explicit step — Claude does not accept changes on your behalf. Tokens are consumed only when you accept.

## Good to know

* **Suggestions come from Klipy, not invented by Claude.** `list_agent_suggestions` returns proposals Klipy's agent already generated from your conversations. Claude surfaces and applies them — it does not fabricate CRM edits.
* **You stay in control of every change.** Accepting is one suggestion at a time, and you can edit fields before applying. To dismiss one instead, Claude uses `reject_agent_suggestion`.
* **Updates need a recorded meeting to draw from.** This workflow grounds on `get_meeting_transcript`, so it works on calls Klipy recorded. Suggestions can also arise from other conversations Klipy processes.

## 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 recap email while you are there.
  </Card>

  <Card title="Ask your data" icon="message-circle-question" href="/docs/guides/mcp/use-cases/ask-your-data">
    Ask questions across the conversations behind the updates.
  </Card>

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