> 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 call center** et renforcer la fidélité.

Informez vos clients lorsqu’une commande est retardée ; cela réduira le trafic du call center et générera davantage d’interactions avec les clients en leur donnant plus d’informations. Si nécessaire, vous pouvez aussi ajouter une incentive pour le prochain achat en guise de compensation.

🔧 Complexité : 2/5

💰 ROI : faible

![](/files/eff6597cb7daa4d928bf2a3aba87839740d63269)

## 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 stream pour envoyer les utilisateurs du segment précédemment créé vers une solution d’emailing ou de push notification


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.commandersact.com/fr/cas-dusage/data-activation/increase-loyalty/notification-about-order-delay.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.