> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-mcp/skills/sales-meetings.md).

# Sales Meetings

Ask Claude to find and analyze your recorded sales meetings, surfacing AI summaries, action items, and sales tips.

Ask Claude to turn your recorded sales meetings into searchable, summarized insight.

**Guide:** `sales-meeting-analyzer`

**What it does:** Finds and analyzes your recorded sales meetings, surfacing the summary, action items, and sales tips already computed for each meeting, and answers follow-up questions about what was discussed.

**Use it when:** You want to see your meetings, analyze your last call, search for a meeting by title, check whether your calendar is connected, see upcoming scheduled recordings, or get meeting statistics.

**Try saying:**

* "Show me my recent meetings and analyze my last one."
* "Find my meeting with Juan from last week and give me the action items."
* "How many meetings did we have this month, and is my calendar connected?"

**You get back:** Meeting lists in a table (title, date, duration, whether insights exist), a single meeting's summary with action items and sales tips, aggregate statistics, connected-calendar status, and upcoming scheduled recordings. Transcripts are summarized rather than dumped, since they contain sensitive personal information.

**Writes data?** No, read-only.

**Behind the scenes:** `get_current_workspace_meetings`, `get_organization_meetings`, `search_meetings_by_title`, `get_meeting_by_bot_id`, `get_meeting_statistics`, `get_organization_calendars`, `get_scheduled_bots`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dapta-mcp/skills/sales-meetings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.