> 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/ai-powered-unsubscribe-intent-detection.md). # AI-Powered Unsubscribe Intent Detection SMS compliance is evolving — and so is Recart. Today we're going beyond standard keywords like STOP and UNSUBSCRIBE to automatically detect unsubscribe intent in free-text replies like "please stop texting me" or "I don't want these anymore". Recart now uses AI to detect unsubscribe intent in free-text replies. When a subscriber sends a natural language opt-out message, the system recognizes the intent and processes the unsubscribe automatically — exactly like a standard STOP keyword. ### What the AI recognizes The system is designed to catch genuine opt-out requests while avoiding false positives. It correctly processes: * Natural language phrases (*"remove me," "I don't want this," "please stop texting me"*) * Stop-related emojis (🛑, ✋, 🚫) used alone or alongside opt-out text * Common misspellings and variations (*"cease all," "seize all," "Dtop"*) It correctly ignores: * Single-letter or short conversational replies (*"Y," "Yes," "No," "Thanks," "Ok"*) * Automated or carrier responses (*"This number does not accept SMS text messages"*) * Number-only messages (e.g. 2FA codes sent back in reply) ### What you'll see in your account Three updates are live alongside this feature: * **Subscriber chart** — AI opt-out counts are now visible on your Subscribers page, so you can track the trend over time ![AI\_optout1](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FEfgBBXnPFX7m1OqXu279%2Fai-powered-unsubscribe-intent-detection-1.png?alt=media) * **Subscriber profile** — each profile now shows which detection method triggered the opt-out (keyword or AI) and the exact message that was sent ![AIoptout2](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fu4uCNJlj6JjlZsz0K6oO%2Fai-powered-unsubscribe-intent-detection-2.png?alt=media) * **Settings toggle** — you can turn the AI opt-out mechanism on or off from [**Settings → SMS tab**](https://app.recart.com/settings/sms) ![SMS\_ai\_toggle](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FsbLlxtO5URH3F0VXaiKY%2Fai-powered-unsubscribe-intent-detection-3.png?alt=media) ### Why this matters SMS compliance requirements are evolving. Regulators increasingly expect brands to honor opt-out requests regardless of how they're worded. This feature ensures subscribers who express intent to opt out are always unsubscribed — reducing your compliance exposure from missed or ambiguous requests. No setup is required — the feature is enabled for all accounts automatically. If you have any questions or need support, feel free to reach out to us at — we're 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 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://help.recart.com/compliance-protections/ai-powered-unsubscribe-intent-detection.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.