> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/email-and-communication/email-settings/auto-follow-ups/sms-follow-ups.md).

# SMS Follow-Ups

Improve SMS delivery and avoid spam filters with these helpful tips.

We’re enhancing our auto follow-up feature to improve the delivery and consistency of SMS text messages, especially as carriers tighten regulations to reduce spam.

## Why This Matters <a href="#h_9d5be95bbc" id="h_9d5be95bbc"></a>

Long SMS messages are automatically split into multiple segments before they’re sent. This can increase the risk of messages being flagged as spam, as phone carriers now more closely monitor message content and sending patterns.

To help your messages get through smoothly, we’re introducing a character limit for SMS follow-ups to prevent unnecessary segmentation. Here’s what to keep in mind:

* **Length**: SMS messages over the character limit will be split into segments, increasing the chance of being flagged by spam filters.
* **Content**: Messages with certain keywords, links, or promotional language are more likely to be flagged as spam, especially when split across multiple segments.
* **Sending Rate:** Sending a high volume of long or repeated messages quickly can trigger red flags with carriers.

For a smoother experience and better results with SMS follow-ups, please review your messages to ensure they meet the new requirements.

&#x20;&#x20;


---

# 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.paintscout.com/support/email-and-communication/email-settings/auto-follow-ups/sms-follow-ups.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.