> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/agents/channels/sms.md).

# SMS

The **SMS channel** automates sales interactions over text message, handling incoming texts from leads and sending outgoing texts through [Workflows](/agents/workflows.md).

<figure><img src="/files/g1bBh2ECxi9bWQrr44Br" alt=""><figcaption><p>The SMS channel configuration.</p></figcaption></figure>

* **Incoming replies**: Spara responds to incoming text messages from leads, answering questions and moving them through your sales funnel without rep involvement.
* **Automated outgoing texts**: Spara sends texts to leads as part of a workflow. For example, after a lead submits a form, a workflow can send an immediate text to prompt them to schedule a meeting.

Spara does not send cold or unsolicited outgoing texts outside of your workflows.

## Configuration

### Instructions

The SMS channel is configured through its [AI Instructions](/agents/channels/configuring/ai-instructions.md), the same way every channel is built. Use them to define the channel's persona, tone, and how it should handle common scenarios like questions, objections, and handoffs to a rep.

### Phone number setup

Each SMS channel can be assigned an incoming phone number on the **Configuration** tab. This is the number it answers texts on and sends outgoing texts from. Phone numbers are provisioned through Twilio. Contact your Spara account manager to enable texting and provision numbers for your account.

{% hint style="warning" %}
**Twilio registration required.** Before your SMS channel can send or receive messages, your brand and messaging campaign must be registered and approved through Twilio's A2P 10DLC process. This industry-wide requirement verifies your business and ensures your messaging complies with carrier standards. Your Spara CSM handles the registration, but you'll need to provide a campaign description, links to your Terms of Service and Privacy Policy (with SMS opt-in language), and sample messages. See the [https://docs.spara.com/guides/onboarding-guides/text-agent-onboarding](https://docs.spara.com/guides/onboarding-guides/text-agent-onboarding "mention") for full details.
{% endhint %}

{% hint style="info" %}
Each phone number can only be assigned to one published SMS channel at a time. If you try to publish one with a number already in use, you'll see a conflict error.
{% endhint %}

## Outgoing texts with workflows

The [Send Text Step](/agents/workflows/steps/send-text.md) step in workflows lets you send personalized outgoing texts to leads as part of a broader automated sequence. Pair it with **Wait** and **Condition** steps to build multi-touch SMS follow-up flows.

{% hint style="info" %}
**Per-recipient frequency cap.** Spara enforces a daily ceiling on outgoing texts sent to any single lead. When the cap is reached, further outgoing texts to that lead are skipped for the remainder of the day.
{% endhint %}


---

# 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://docs.spara.com/agents/channels/sms.md?ask=<question>&goal=<endgoal>
```

`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.