> 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 have a character limit of 160, which means there's no customizable template for editing the reminder text. The default message is: *** **Hello %client\_first\_name%,** Get ready: your activity starts soon: **%session\_title%** - **%start\_date%** **%location%** - **%meeting\_point%** %post\_booking\_message% Have a good session! *** ### Directions for use * **Note: Character count**: SMS text is limited, and exceeding this limit may result in multiple SMS messages being sent, which could increase costs. Be especially careful with the texts you have included in your products on the post-booking message %post\_booking\_message% * **No customization for reminders**: Unlike post-activity SMS, reminders cannot be customized via templates. ### Post-activity SMS Text messages sent after activities can be customized to include, for example, a link to a satisfaction form. As with reminders, it's essential to monitor the character count to avoid sending multiple text messages. *** ### Conclusion **SMS reminders** are a useful feature to **notify clients of upcoming sessions** and improve business organization. However, their use must be carefully managed due to the **character limit**, to avoid sending **multiple SMS messages and additional costs**. By integrating these best practices, you guarantee **smooth and effective communication** with your customers 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 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://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=&goal= ``` `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.