> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/send-cmas-directly-from-the-history-tab.md).
# Send CMAs Directly from the History Tab
We’ve made it even easier to share your Comparative Market Analyses (CMAs) with clients — no extra clicks or editor loading required.
### ✨ What’s New
Instead of opening the CMA editor to email your report, you’ll now see an **Email button** right in your **History tab gallery view** (as shown above).
Click **Email** to open a message slide-out on the right side of your screen.
***
### 💌 How It Works
1. **Go to**: `Marketing > History > Presentations`
2. Hover over the CMA you’d like to send.
3. Click the **Email** button.
4. A pre-drafted email will appear on the right-hand side already filled with your CMA title, report summary, and link.
5. **Choose your recipient**.
6. **Send,** and you’re done!
***
### 💡 Why It Matters
* **Save time:** No need to open or edit the presentation to send it.
* **Stay consistent:** Every email includes a professional, branded message automatically.
* **Increase engagement:** Make it easier to follow up with your clients while keeping your workflow seamless.
***
{% hint style="info" %}
**Pro Tip:** You can still access the editor anytime by clicking **Edit** if you’d like to make changes before sending.
{% endhint %}
[**Learn more about creating Presentations.**](/guides/marketing/presentations.md)
---
# 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://help.rechat.com/whats-new/send-cmas-directly-from-the-history-tab.md?ask=&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.
