> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/francais/courriels/programmation-des-courriels-et-boite-denvoi.md).

# Programmer des e-mails

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM2MTY4Mw==>" %}

Vous pouvez programmer la date et l’heure d’envoi d’un e-mail en sélectionnant l'option Programmer l'envoi.

L’e-mail programmé apparaîtra dans les onglets Communication s et Chronologie avec le nom de la personne qui l'a programmé et la date à laquelle il a été programmé. Vous pouvez aussi envoyer immédiatement un e-mail programmé à partir des onglets Communications et Chronologie.

![](https://gblobscdn.gitbook.com/assets%2F-MWYnDNwe3Cuo4zlGbs5%2F-MjUU4GA2Of4CwaPt8lV%2F-MjUX2xllVeXBSXeeD3G%2FSchedule-Send%20\(1\).gif?alt=media\&token=589f40f2-71d1-4d15-b29c-3f75bdc26724)

Notez que les e-mails qui dépassent la taille définie dans Builder ne peuvent pas être enregistrés en tant que brouillons. [Voir ici pour plus d'informations](https://docs.enate.net/enate-help/builder/builder-2021.1/system-wide-settings/general-settings#maximum-email-size). Cependant, la validation de la taille de l’e-mail se fait lors de son enregistrement, et non au moment de son envoi. Ainsi, si un e-mail de 25 Mo a été programmé et que la taille maximale est réduite à 10 Mo dans Builder, l’e-mail programmé sera tout de même envoyé car il était conforme à la taille autorisée lors de sa programmation.


---

# 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.enate.net/enate-help/francais/courriels/programmation-des-courriels-et-boite-denvoi.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.