> 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/sms/automated-flows.md).

# Automated Flows

Covers automated flows: messages that send themselves when a subscriber abandons a cart, replies, or takes another action.

Everything you need to know about automated flows — messages that send themselves when a subscriber does something, like abandoning a cart or replying with a keyword. Set one up once and it runs on its own.

### Start here

* [Automated Flows - Getting Started](/sms/automated-flows/setting-up-sms-automated-flows.md)

### Abandonment flows

* [Automated Flows - Abandoned Cart](/sms/automated-flows/automated-flows-abandoned-cart.md)
* [Automated Flows - Abandoned Checkout](/sms/automated-flows/abandoned-checkout.md)
* [Automated Flows - Browse Abandonment](/sms/automated-flows/automated-flows-browse-abandonment.md)
* [Automated Flows - SMS Abandonment](/sms/automated-flows/abandonment-flows.md)

### Triggers

* [Automated Flows - Keyword Reply](/sms/automated-flows/automated-flows-keyword-reply.md)
* [Set up Custom Triggers in Automated Flows](/sms/automated-flows/how-to-set-up-custom-triggers-automated-flows.md)
* [Custom Triggers Automated Flow Use Cases](/sms/automated-flows/custom-triggers-automated-flow-use-cases.md)
* [Use Trigger Selections in Automated Flows](/sms/automated-flows/use-trigger-selections-in-automated-flows.md)

### Flow logic

* [Use Conditional Splits in SMS Flows](/sms/automated-flows/use-conditional-splits-in-sms-flows.md)
* [Schedule Delay in SMS Flows](/sms/automated-flows/schedule-delays-in-sms-flows.md)


---

# 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/sms/automated-flows.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.