> 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/dapti/capabilities/sales-meetings.md).

# Sales Meetings

Dapti has access to every meeting the AI Note Taker has recorded for your workspace. It can list them, dig into any one of them for a full structured summary, and spot patterns across the whole set. Below are three of the most useful meeting conversations.

{% hint style="info" %}
For Dapti to see a meeting, the AI Note Taker has to have joined the call. See the [AI Note Taker guide](https://github.com/Dapta-Tech/dapta-docs/blob/develop/docs-en/dapti/capabilities/broken-reference/README.md) to make sure it joins your future meetings automatically.
{% endhint %}

***

## List Your Recent Meetings

Ask Dapti for a quick read on what meetings happened recently. Dapti returns a table with every meeting, its date, duration, and a clickable link to the full record.

**Try this prompt:**

> *Show me my recent sales meetings.*

<figure><img src="/files/GeDJ9Xnae22OSlLIZKpf" alt="Dapti listing 15 recent sales meetings in a table showing meeting title, date and time in the user&#x27;s timezone, and duration in minutes, with each meeting title as a clickable link"><figcaption><p>Every meeting the Note Taker recorded, in one clickable list.</p></figcaption></figure>

Other meeting-list prompts you can use:

* *"What meetings do I have this week?"*
* *"Show me my meetings from last week"*
* *"Find meetings with \[participant name]"*
* *"Which of my meetings ran longer than an hour?"*

***

## Get a Full Meeting Summary

Ask Dapti to dig into any specific meeting and return a structured summary with everything that mattered: who was there, what was discussed, what was committed to, and what to do next.

**Try this prompt:**

> *Give me a detailed summary of the Sprites Demo meeting and key action items.*

Dapti reads the transcript and returns an organized brief with overview, key topics, stakeholders, action items with owners and priorities, AI-generated sales coaching tips, and call insights.

<figure><img src="/files/G3OoafTfC8k4gbXhBWfK" alt="Dapti&#x27;s full summary of the Sprites Demo meeting: overview, key topics covered table, action items table with task, owner, and priority columns, sales tips from AI analysis (reduce monologue, summarize key points, clarify technical requirements, align on stakeholders earlier), and call insights identifying decision drivers and next steps"><figcaption><p>Dapti's structured meeting brief: overview, topics, stakeholders, action items, AI sales tips, and call insights.</p></figcaption></figure>

Other deep-dive prompts you can use:

* *"What were the key takeaways from the \[meeting name] call?"*
* *"Pull all action items from my meeting with \[participant]"*
* *"Who said what during the \[meeting name] call?"*
* *"What objections came up in the \[meeting name] meeting?"*

{% hint style="success" %}
The action items Dapti extracts include owner and priority. Use these to feed your task tracker or follow-up email without rewatching the call.
{% endhint %}

***

## Surface Patterns Across Meetings

The most powerful question to ask Dapti is across multiple meetings at once: what keeps coming up, where does friction cluster, and what is your team consistently hearing.

**Try this prompt:**

> *What are the most common questions or objections coming up across my recent Office Hours meetings?*

<figure><img src="/files/5k7lkBNeHOYILY9fhbn9" alt="Dapti analyzing 8 recent Office Hours meetings and surfacing recurring themes including CRM integration, credit consumption, campaign setup, inbound call configuration, agent behavior, WhatsApp integration, Google Sheets as a CRM alternative, and platform onboarding, plus a Key Objections frequency table and Strategic Implications with prioritized recommendations"><figcaption><p>Dapti clusters questions and objections across multiple meetings and translates them into strategic recommendations.</p></figcaption></figure>

Other pattern prompts you can use:

* *"What product features do customers ask about most often?"*
* *"What is the most common reason a deal doesn't move forward?"*
* *"Where are prospects getting confused in my demos?"*
* *"What are the top three things to fix in our onboarding?"*

{% hint style="info" %}
Patterns are most useful when you have 5 or more meetings to compare. The more recordings Dapti can read, the sharper the cross-meeting insights become.
{% endhint %}

***

## Next Steps

{% content-ref url="/pages/ITt1P6qAQhK8f6FgbVFk" %}
[Call Analytics](/dapti/capabilities/call-analytics.md)
{% endcontent-ref %}

{% content-ref url="/pages/9VV2mFTv81FnCZ0y12C3" %}
[Account Evaluation](/dapti/capabilities/account-evaluation.md)
{% endcontent-ref %}

{% content-ref url="/pages/UjlkeeYDNhNUVMDiFvdf" %}
[Commercial Support](/dapti/capabilities/commercial-support.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/dapti/capabilities/sales-meetings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.