> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/communication-client/envoyer-un-rappel-automatique-au-client-avant-sa-session-via-yoplanning/envoi-dun-rappel-par-sms.md).

# Sending a reminder via SMS

You can send a reminder via SMS to your session participants. It's important to note that SMS messages are limited to 160 characters, meaning there's no customizable template to modify the reminder text. The default message sent is:

***

Hello, your %product\_title% session will start soon: %start\_date% Have a good day

***

### Usage tips

* **Beware of the number of characters**: SMS text is limited, and exceeding this limit may result in sending multiple SMS messages, which could increase costs.
* **No personalization for reminders**: Unlike post-activity SMS, reminders cannot be personalized via templates.

### Post-activity SMS

Text messages sent after activities can be personalized to include, for example, a link to a satisfaction survey. As with reminders, it is essential to monitor the character limit to avoid sending multiple text messages.

***

### Conclusion

**SMS reminders** are a useful feature for **notifying clients of their upcoming sessions** and improving activity organization. However, their use must be carefully managed due to the **character limit**, in order to avoid sending **multiple SMS messages and incurring additional costs**.

By integrating these best practices, you guarantee **smooth and efficient communication** with your clients while optimizing your resources.


---

# 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.yoplanning.support/en/yoplanning-academy/yoplanning-au-quotidien/communication-client/envoyer-un-rappel-automatique-au-client-avant-sa-session-via-yoplanning/envoi-dun-rappel-par-sms.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.
