> 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/appendix/brokerage-set-up/marketing-template-guidelines/template-design-guidelines/custom-presentation-templates.md).

# Custom Presentation Templates

<figure><img src="/files/1sgZEbNljzBryfoGQ7Qg" alt=""><figcaption></figcaption></figure>

### **The guide covers:**

* How custom CMA presentations work alongside Rechat's built-in CMA pages
* Digital (web) and print design requirements
* Choosing between static and fully editable pages
* Accepted design file formats
* Required deliverables before implementation
* Annotation best practices for MLS fields, agent information, and locked content
* Packaging and submitting your project for development
* A complete annotated example of a finished CMA template

{% file src="/files/fUH63LrBuFF9UbqtMLvl" %}

### Before You Submit

To help us begin implementation as quickly as possible, please make sure your submission includes:

* Editable source files in a supported design format (.fig, .psd, .ai, .indd, or .sketch)
* PDF exports of both portrait and landscape versions
* Clear annotations identifying:
  * MLS-populated fields
  * Agent information
  * Locked (non-editable) elements
* All linked assets, fonts, and supporting files
* Everything organized in a single shared folder (Google Drive, Dropbox, OneDrive, etc.)

### Need Help?

If you have questions about preparing your designs or aren't sure whether your files meet our implementation requirements, your Rechat onboarding or Customer Success team is happy to help before development begins.


---

# 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://help.rechat.com/appendix/brokerage-set-up/marketing-template-guidelines/template-design-guidelines/custom-presentation-templates.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.