> 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/getting-started/your-first-brief.md).

# Your first brief

Onboarding ends with a brief of what Scout learned about you and the work waiting for you. It sets the pattern for every morning after.

Onboarding ends with a brief: what Scout now knows about you, and the work waiting for you. It arrives once you've been through your connections, or at the end of your workday if you haven't finished them.

## What's in it

* **What Scout learned about you**: what you sell, who buys it, how you work and what's in motion, in a few lines. Specific enough that you recognize yourself. Tell Scout if it got something wrong.
* **The work**: what's waiting on you, then what Scout has ready, including anything it held back while you were connecting things.
* **From now on**: what Scout keeps doing in the background, such as drafting a reply whenever a prospect writes to you.
* **One question** to start the work.

This first brief sets the pattern for the one you'll get each morning from now on. See [Morning brief](/scout/how-scout-works/jobs/morning-brief.md).

## What Scout learns

As you connect tools, Scout builds a picture of you that every job uses afterwards:

* **Your selling profile**: your product, your ideal customer, your territory and how you work. It starts from your email domain and grows with each connection: your inbox, your pipeline, your network.
* **Your voice**: how you write, learned from the emails you've sent, so drafts sound like you from the first one.
* **Your memory**: preferences, corrections and context you give Scout, such as "keep my emails shorter" or "Priya owns the Halden renewal". Ask Scout to remember or forget anything. When your CRM already records something, Scout points you there instead of keeping a second copy.

## Starting over

Write "redo my onboarding" and Scout starts again from its welcome. Your jobs, your settings and what it learned about what you sell stay.


---

# 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/getting-started/your-first-brief.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.
