> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-send-sms.md).

# Send SMS / Text message

Journey step that sends a text message (SMS) from one of your campaigns to the contact.

The Send SMS / Text message step sends a text message to the contact. The SMS must already exist in a campaign: you can't create a new SMS from inside a Journey.

## Choose the SMS

When you add the step, a list of your text messages opens. It shows each message's name, the campaign it belongs to and when it was created. Search by name if the list is long, and click the SMS you want.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-dc8369abe7ac8a0b1e84666751dbadd0f33b5339%2Fjourney-step-send-sms-sms-list.png?alt=media" alt="Send SMS dialog with a search field and a list of text messages with name, campaign name and created date"></div>

## Settings

After you choose an SMS, the step shows its name, the sender and a preview of the message. To pick a different message, click **Choose other sms**.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-d0a111d92e56aa127bbdca6556d6b7d95c048249%2Fjourney-step-send-sms-sms-settings.png?alt=media" alt="Send SMS dialog with the name of the chosen SMS, the sender and a preview of the message"></div>

Click **Apply** to save the step.

## Good to know

* You can add the step before the SMS is ready, as a placeholder. A Journey with unfinished steps can be saved, but not activated.
* The report for the SMS is in the campaign where you built it.


---

# 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://support.emarketeer.com/guides/journeys/journey-steps/journey-step-send-sms.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.
