> 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/gestion-commerciale-bis/fichiers/fichiers-de-base/envoi-des-pieces-par-e-mail.md).

# envoi-des-pieces-par-e-mail

Vous pouvez créer des messages type à envoyer pour l'envoie de vos pièces commerciales à vos clients. Vous économisez ainsi beaucoup de temps de saisi.

Il suffit au moment de l'envoie de la pièce commerciale, de sélectionner le message type que vous souhaitez envoyer.

Le texte du message s'affiche automatiquement, et vous pouvez éventuellement le modifier si vous en souhaitez ainsi en gardant le maximum du message.

Vous pouvez, lors du paramétrage de votre message, insérer des champs comme la civilité et le nom, les données correspondant s'insérant automatiquement dans votre message.

Plusieurs champs sont à votre disposition pour les insérer dans la composition de votre message type.


---

# 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/gestion-commerciale-bis/fichiers/fichiers-de-base/envoi-des-pieces-par-e-mail.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.
