> 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/traitements/relances.md).

# relances

## Introduction

Cette option vous permet de générer des lettres de relance ou via e-mailing. Vous allez pouvoir générer des extraits de compte à destination de vos clients également.

Pour une opération de relance par courrier, vous avez des modèles pré-paramétrés dans votre logiciel. Vous pouvez bien évidement créer vos modèles personnalisés et/ou modifier les modèles existants.

{% hint style="success" %}
Nous vous conseillons de dupliquer un modèle en lui donnant un nouveau nom lorsque vous décidez soit de créer un nouveau modèle en partant d'un modèle déjà existant, par exemple, soit pour modifier un modèle. Cela vous permet de sauvegarder le modèle d'origine au cas où vous souhaiteriez revenir dessus.
{% endhint %}


---

# 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/traitements/relances.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.