> For the complete documentation index, see [llms.txt](https://docs.dailybiz.com/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dailybiz.com/index/crm-crm/fichiers/divers/messages-types-e-mails/introduction.md).

# Introduction

Vous créez ici les messages types que vous envoyez à vos contacts.

Vous pouvez par exemple définir une message type pour l'envoi d'une pièce commerciale à un client ou juste mettre en place votre signature quand c'est un message pour un sujet ponctuel.

La richesse d'options dans ce fichier, vous permet de rajouter des champs dynamiques dans l'objet de votre message. Il suffit de cliquer sur la zone de l'objet pour que la liste des champs disponibles s'affiche.

C'est un fichier qui peut vraiment vous faire gagner du temps lors de la gestion du quotidien de votre activité.


---

# 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.dailybiz.com/index/crm-crm/fichiers/divers/messages-types-e-mails/introduction.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.