> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/fr/cas-dusage/data-activation/increase-loyalty/notification-about-order-delay.md).

# Notification de retard de commande

## Description du cas d’usage

🎯 Objectif :

Répondez aux attentes des clients, **réduire le trafic du centre d'appels** et augmenter la fidélité.

Informez vos clients lorsqu'une commande est retardée, cela réduira le trafic du centre d'appels et apportera davantage d'interactions avec les clients en leur donnant plus d'informations. Si nécessaire, vous pouvez également ajouter une incitation pour le prochain achat en compensation.

🔧 Complexité : 2/5

💰 ROI: Faible

![](https://3282103337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-255935cb1d57ad85d707c49bdbddba653f35ca8d%2Fdelay.png?alt=media)

## Configuration du cas d’usage

Étape 1 : créer une nouvelle variable order\_delay = True / False et importer les valeurs

Étape 2 : créer un segment avec order\_delay = True

Étape 3 : créer un flux pour envoyer les utilisateurs du segment créé précédemment vers une solution d'emailing ou de notification push


---

# 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://doc.commandersact.com/fr/cas-dusage/data-activation/increase-loyalty/notification-about-order-delay.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.