> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/service/status-messages.md).

# Status messages

Status messages send the customer an SMS or e-mail automatically when a service order reaches a status.

Each status can send one SMS and one e-mail when a service order reaches it. You pick which message text goes out. The status new service orders start on is the one that gives the customer their portal link.

Status messages are set on the status itself: **Settings → Statuses**, open a status, and use **Messages for {status}** beside the status fields. You need the **Service configuration** permission. The section is not shown while you create a status: save it, then open it again. Write the texts first under **Settings → Message texts** (see [Message texts](https://docs.flowretail.com/docs/service/message-texts.md)).

***

## Messages for a status

![Edit status dialog for the start status, 'Messages for …' section with an SMS row switched On and the E-mail row showing Attach paper](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FDIq6TRpLIgYuMXxjxvQC%2Fservice-status-messages.webp?alt=media)

Two rows, SMS and E-mail. **Each change is saved as soon as you make it**, not by the status form's <kbd>Save</kbd>.

| Field             | Meaning                                                                                                                                                     |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SMS / E-mail      | <kbd>Not sent</kbd> until you pick a text. Then a switch: <kbd>On</kbd> sends, <kbd>Off</kbd> keeps the choice without sending.                             |
| Text              | The message text to send. Picking one on an empty row creates the status message, switched on. The picker shows each text in your language beside the list. |
| Attach paper      | E-mail only. <kbd>None</kbd> (default), <kbd>Service confirmation</kbd> or <kbd>Service summary</kbd>. The customer gets the paper as a PDF in the e-mail.  |
| <kbd>Delete</kbd> | Stops sending on this status. Messages already sent stay in each case's log.                                                                                |

The picker offers texts written for that channel, except Message to the customer. Document by e-mail is offered only while a paper is attached, and the paper cannot be removed while it is the text. A text marked <kbd>Needs {language}</kbd> cannot be used until it is written in your language. With no texts for a channel, the row says "Write a text for {channel} first." with a link to the texts.

On the Statuses list, each status shows a badge per channel it sends on, struck through with <kbd>Off</kbd> when switched off.

***

## When a message is sent

* When a service order reaches the status, including when it is created on its start status.
* Again each time the order comes back to the status.
* Never for orders that reached the status before the status message existed.
* Changing or deleting a status message affects later status changes only.
* If the order has already moved to another status before the message goes out, it is skipped. The message sent when an order is created is never skipped.
* While **Pause every message to customers** is on in **Settings → General**, messages wait, then go out when it is turned off, unless the order has moved on. Switching a status message <kbd>Off</kbd> does not stop messages already waiting.

The SMS goes to the customer's mobile number. The e-mail goes to their e-mail address, sent from the store's e-mail address. The text is in the customer's preferred language when written, otherwise in your company's.

***

## The portal link

The customer gets a link to follow their case automatically only when the start status sends a message, and that text contains the **Portal link** variable. Use the Registration text for this (see [Message texts](https://docs.flowretail.com/docs/service/message-texts.md)). Staff can also send a link from the case with **New portal link**.

The start status is set under **Settings → General** as "Start status for new service orders". When it sends nothing, the Statuses list warns "Customers get no portal link: {status} sends no message." The warning does not check that the text contains the Portal link.

***

## Good to know

* Every message shows in the service order's log with its delivery state: <kbd>Recorded</kbd>, <kbd>Sending</kbd>, <kbd>Delivered</kbd>, <kbd>Delivery uncertain</kbd> or <kbd>Failed</kbd>.
* A message that cannot be sent is logged as <kbd>Failed</kbd> with the reason, such as the customer having no mobile number or e-mail address, the store having no e-mail address, or no text in your company's language. The status change itself goes through.
* If the paper cannot be made, the e-mail goes out without it, and the log says so.
* On a failed message, <kbd>Send again</kbd> opens **Send a pre-written message** on that channel; choose the text again. It is not offered when delivery is uncertain, so the customer is not messaged twice.
* While a status message is switched on, its text cannot be deleted in any language.


---

# 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.flowretail.com/docs/service/status-messages.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.
