> 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/readme.md).

# Meet Scout

Scout is the AI sales assistant for reps. It works your whole book around the clock and hands you the next move, already drafted.

**Scout** is the AI sales assistant for sales reps: an always-on teammate that works your whole book around the clock. It watches your accounts, inbox, calendar and CRM, spots the signals that matter, and hands you the next move with the reason why, already drafted in your voice. You read it, change a line if you want, and hit send.

Scout lives where you already work. It talks to you in Slack and by text, and its drafts land in your own Gmail or Outlook. There is no new app to keep open.

## What Scout does for you

* **Finds new prospects**: a target account back on your pricing page, a past champion who just joined a company that fits, a buying group forming around one account. Scout notices, and drafts the first note.
* **Finds dropped deals**: deals that stopped moving, warm leads that slipped through, closed-lost accounts that are back on your site. Scout drafts the check-in that picks up where you left off.
* **Keeps your CRM current**: Scout reads your CRM to understand your pipeline and, when you ask, logs notes and updates records as you.
* **Drafts everything for your approval**: every email Scout writes lands in your drafts. Nothing sends until you send it.

## How it works

1. **Sign up** with your work email, then meet Scout in Slack or by text. See [Sign up and say hello](/scout/getting-started/sign-up.md).
2. **Connect your tools.** Scout learns how you sell from your inbox, your CRM and LinkedIn, and shows you one piece of real work from each as you go. See [Connect your tools](/scout/getting-started/connect-your-tools.md).
3. **Get your brief.** At the end of your first day, Scout sends what it learned about you and the work waiting for you. From then on, that is how your morning starts. See [Your first brief](/scout/getting-started/your-first-brief.md).
4. **Let the jobs run.** Scout keeps working in the background: drafting replies to your inbox, briefing you each morning, and offering more jobs as it finds work worth doing. See [Jobs](/scout/how-scout-works/jobs.md).

## Every rep gets their own Scout

Scout is not one bot shared by the whole team. Each Scout knows one rep: your accounts, your voice, your jobs, and what you have asked it to remember. It reads your mailbox and your CRM under your own permissions, and brings what it finds to you.

## Where to go next

* [Talking to Scout](/scout/how-scout-works/talking-to-scout.md): what to ask, and how Scout answers in Slack, by text and by email.
* [Drafts and approval](/scout/how-scout-works/drafts.md): where drafts land and how you stay in control.
* [Privacy and data](/scout/trust/privacy-and-data.md): what Scout reads, and what it never does.


---

# 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/readme.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.