> 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/how-scout-works/jobs/morning-brief.md).

# Morning brief

Each workday morning, Scout tells you which accounts are worth your time and what it has ready for you.

Each workday morning, Scout sends you a brief: which accounts are worth your time today, what changed overnight, and what it has ready for you, with drafts waiting in your inbox.

**On by default** from the first workday after your inbox is connected. Your first brief is the one that ends onboarding. See [Your first brief](/scout/getting-started/your-first-brief.md).

## What's in it

* **Accounts worth your time today**, and why: a reply that came in, a deal going quiet, a signal Scout spotted.
* **What's ready**: the drafts waiting in your Drafts folder, one line each.
* **What's coming**: the meetings on your calendar that need prep.
* **One question** to start the day on.

It arrives in Slack, or by text if that's where you talk to Scout. Reply to it to take any item further, and Scout picks it up as a new conversation.

## Tuning it

Ask Scout to change when the brief arrives, what it leads with, or what to leave out. It's your job, and Scout updates it in place.


---

# 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/how-scout-works/jobs/morning-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.