> 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/workflows/steps/send-text.md).

# Send Text Step

The **Send Text** step sends an SMS message to a lead's phone number.

<figure><img src="/files/gL4TW0W6d32FOaZjGJUF" alt=""><figcaption><p>The Send Text step configuration panel.</p></figcaption></figure>

## Configuration

### Message Body

Write the SMS content in the message body field. The body supports variables: use the **Insert menu** (⚡) to browse available lead data fields.

Keep messages concise. SMS best practices recommend staying under 160 characters to avoid message splitting.

### From Number

The outgoing phone number is configured on the text agent's **Configuration** tab. It is shown read-only in this step. To change it, open the text agent settings; a link is shown at the bottom of this step's configuration panel.

## Tips

{% hint style="info" %}
**Opt-out compliance.** Ensure your SMS program complies with applicable regulations (TCPA, GDPR, etc.). Leads should have opted in to receive SMS messages from your account.
{% endhint %}

{% hint style="warning" %}
**Missing phone number.** If a lead has no phone number on record, this step is skipped and the workflow continues to the next step.
{% endhint %}

{% hint style="info" %}
**Outgoing time windows.** If your organization has a text outgoing window configured (Settings > Phone Numbers > Outgoing Times), this step only fires during that window. Leads that reach this step outside the window are held — not dropped — and the step retries automatically once the window reopens.
{% 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/workflows/steps/send-text.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.