> 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/scout/connections/text.md).

# Text

Text Scout from your phone the way you would in Slack: prep on the way into a meeting, and hear about drafts and signals wherever you are.

Scout can be your teammate by text, the same as in Slack. Ask it what to lead with on the way into a meeting, and hear about drafts and signals on your phone.

## Link your phone

* **From your signup email**: tap **Text Scout**. It opens Messages with the first text filled in. Send it.
* **Ask Scout** to text you, or to link your phone. It gives you a link to tap on your phone, or Scout's number and the exact message to send. The code in that message is yours alone, works once, and expires.
* **From your Scout page**: open [**Scout**](https://app.spara.co/scout) in Spara and, under **Accounts**, choose **Text Scout from your phone**.

You get a confirmation text once your phone is linked. Texts after that reach your Scout.

## Texting with Scout

Scout writes the way a person texts: a thought or two per message, nothing you have to scroll for. Links come through as text, and anything longer than a few messages Scout offers to email you instead.

Scout keeps the texts it starts on its own to a minimum. A job's result or a heads-up that doesn't fit waits for your next text, or goes to your Slack if you have one.

If you use both Slack and text, Scout answers where you wrote. Say "text me that" or "send it to my Slack" to get something on the other.

## Stopping texts

Tell Scout to stop texting you, in any words, and it stops. Ask for them back when you want them. If you text a stop keyword such as STOP instead, Scout holds its texts until you text the line again.

{% hint style="warning" %}
Scout's number is for you. Scout never texts a prospect, and the number isn't one to give to leads.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spara.com/scout/connections/text.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.
