> 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/create-cma-presentations-from-the-search-center.md).
# Create CMA Presentations from the Search Center
### 🔍Create CMA Presentations from Search Center!
The Search Center is your one-stop hub for finding and sharing listings, building tours, and now—creating stunning CMA Presentations with just a few clicks. Here’s how to make the most of it:
#### Create CMA Presentations from Search Center
You can now build **CMA Presentations** directly from your property search:
1. **Navigate to the Search Center**.
2. **Select Properties**: Click the listings you want to include in your presentation.
3. **Tap "Presentation"** from the bottom menu bar.
4. **Choose a Template**: Pick from your CMA templates to get started.
Once you’ve selected your properties and template, you’ll enter the familiar CMA editing flow. From here, you can adjust listing specs, tailor the design, and customize the details before sharing with your clients.
With this update, your search experience is even more powerful—whether you're prospecting, preparing for client meetings, or following up.
{% embed url="" %}
Need help? Visit our **CMA** or **Search Center guides** for more tips!
---
# 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/create-cma-presentations-from-the-search-center.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.
.png?alt=media&token=ccc7add8-95d8-4905-b31c-ea2aa498c6a0)