> For the complete documentation index, see [llms.txt](https://answeringservicecare.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://answeringservicecare.com/docs/ai/ai-features/sms-ai.md). # SMS AI Use AI to manage structured text conversations, collect details, and route messages to the right next step. SMS AI helps ASC handle structured text conversations alongside calls. It can send an initial response, collect the details your workflow needs, and route each conversation based on your rules. ### What SMS AI can handle * Send an automatic first response to an inbound text. * Guide callers through intake and follow-up questions. * Route conversations by message content, schedule, or availability. * Hand conversations to a live agent or a client-facing inbox when needed. ### Consistent workflows across channels SMS AI can use the same assistant logic as your voice workflows. This keeps prompts, routing behavior, and service rules consistent across calls and text conversations. ### Work with live agents Agents can view and handle SMS conversations when a text needs human attention. This gives your team one operational view across calls, chats, and messaging workflows. ### Get started SMS AI is configured around your business rules, message flows, and routing needs. Contact your account manager or to discuss SMS AI for your account. ### Related * [AI Answering Services](/docs/ai/ai-answering-overview/readme.md) * [How AI answers your calls](/docs/ai/how-ai-answering-works/how-ai-answers.md) * [Get started with AI](/docs/ai/ai-answering-overview/get-started.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://answeringservicecare.com/docs/ai/ai-features/sms-ai.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.