> 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/day-to-day-operations/customers/sending-sms-messages.md).

# Sending SMS messages

Send SMS messages to customers and other mobile numbers.

Flow Retail sends SMS messages to registered customers and to mobile numbers not registered to a customer. SMS is also used for customer notifications, such as an order being ready for pickup.

## Getting started

To send SMS messages, you need the SMS extension, active on each store that sends them. The sending store pays for its messages.

## Sending messages

### Send messages from basically 'anywhere'

**In Flow Client:**

* **Customers → Customers:** select **Send SMS** to write to one or more recipients, or send to a single customer who has a telephone number.
* **Customers → Messages:** see messages that have been sent.

The dialog has **Recipient's mobile number** and **Message**, and counts characters and **SMS count** as you type. Without the SMS extension, Flow Client shows **SMS extension is not activated**.

**In Flow Admin → Messages:**

* **Send SMS:** choose the sending store, add each **Recipient**, write the **Message** and select **Send Message**.
* **Broadcast SMS & email:** send to many customers at once. A marketing broadcast only reaches customers with the selected consent.
* **Message History:** every message sent.

### Perfectly coupled with Click & Collect

SMS texts for customer notifications are templates in **Flow Admin → Settings → Templates**: **Customer welcome SMS**, **Order arrived at store SMS**, **Pickup note SMS** and **Delivery confirmation SMS**.

* **Ready for pickup:** give the order handling a **Template on completion** in **Flow Admin → Settings → Order Handlings**. When the handling is completed in Flow Client, the SMS is pre-selected if the customer has a telephone number.
* **Welcome:** tick **SMS** under **Send welcome message** when creating a customer. It is available once the Customer welcome SMS template exists.
* **Delivery confirmation:** when receiving goods, Flow Client can send an SMS to the customers with reservations on the purchase order.

## Handling SMS messages with more than 160 characters

One SMS holds up to 160 characters. Longer messages are split into several SMS messages, as in the table below, and billed per part. The customer's phone joins them back into one message.

{% hint style="info" %}
To split an SMS message into multiple parts, 7 characters out of the 160-character limit are used to include a User Data Header (UDH). This header contains metadata that allows the receiving phone to reassemble the message correctly. As a result, each part of a multi-part SMS can contain 153 characters instead of 160. This applies to every segment of the message, not just the first.
{% endhint %}

{% hint style="warning" %}

#### Emoji and special characters cut the limit

A message containing any character outside the standard SMS alphabet — an emoji, for example — holds only **70** characters, or **67** per part when split. The characters `^ { } \ [ ~ ] | €` each count as two.
{% endhint %}

We recommend keeping messages under 160 characters where you can, but a clear 210-character message is better than a vague short one.

| Characters           | Number of SMS messages required |
| -------------------- | ------------------------------- |
| 1 - 160 characters   | 1 SMS message                   |
| 161 - 306 characters | 2 SMS messages                  |
| 307 - 459 characters | 3 SMS messages                  |
| 460 - 612 characters | 4 SMS messages                  |
| 613 - 765 characters | 5 SMS messages                  |
| 766 - 918 characters | 6 SMS messages                  |

*Last updated 24.09.2026*


---

# 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/day-to-day-operations/customers/sending-sms-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.
