> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/compliance-protections/built-in-protections/sms-smart-sending.md). # SMS Smart Sending Explains Smart Sending, which limits how often a subscriber receives promotional texts, and how to adjust its timing. Avoid bothering your SMS subscribers by setting up Smart sending properly **Smart sending makes sure you do not send promotional text messages too often to your subscribers. If a message is not sent due to Smart Sending, it will not be queued or delayed. It simply won't be sent at all.** You can set smart sending between 0-168 hours. We'd recommend the default 8 hours as your smart sending period, which means that after receiving a promotional SMS the user won't get a new message for 8 hours. The Smart sending timeframe can be set up on your [SMS Settings page](https://app.recart.com/settings/sms). ![Screenshot 2024-01-31 at 16.34.47](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FmGdiugpSw5NmeYWFt8mg%2Fsms-smart-sending-1.png?alt=media) They can be turned off per SMS Campaigns. ![SS 1](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FY4TG0el6tywgH3AVUpbR%2Fsms-smart-sending-2.jpg?alt=media) ### Message sent during Smart Sending timeframe Usually, transactional messages such as Welcome, Help, Order and Receipt, and Fulfilment will still be sent even if the Smart Sending time frame is active. ### Messages that Activate the Smart Sending timeframe Welcome, Help, Fulfilment, and Custom trigger flows **WILL NOT** activate the Smart sending timeframe. This means that promotional messages can be sent after these types of messages. Receipt and order-related messages, as well as Abandonment messages, **WILL** activate the Smart Sending time frame. This means that promotional messages will not be sent after these types of messages. If Smart Sending is enabled but the time frame is not active, all types of messages will be sent. The Smart Sending time frame can only be activated by messages that are sent. ### Messages not sent during the Smart Sending time frame: Campaigns and Abandonment messages will not be sent if the Smart Sending time frame is active. #### Smart Sending does not affect any flows related to Integrations. ### Sending frequency Sending Frequency is a type of Smart Sending that applies specifically to Custom Trigger flows. ![Screenshot 2024-01-31 at 16.30.30](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FGv3ShLhlsj4ep06gcjQ1%2Fsms-smart-sending-3.png?alt=media) You can determine how many times you want to send an automated Custom Trigger flow to your subscribers based on subscriber actions and events. This setting can be adjusted within the Trigger item of a Custom Trigger flow. Options for sending custom trigger flow when the subscriber joins the segment include: * `only for the first time` * `every time` By default, the option is set to `every time`. The sending frequency can be modified at any time, but please note that the changes will not affect messages that have already been sent. If the sending frequency is changed from "Every time" to "Only once," we take into account whether the subscriber has previously received the message. If they have received it once before, we will not send it out again if the subscriber enters the segment again. If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md) We'd be happy to help! --- # 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://help.recart.com/compliance-protections/built-in-protections/sms-smart-sending.md?ask=&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.