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

# Jobs

A job is work Scout does on its own: a signal to watch for and what to do when it fires. Some run by default, some are offered, and you can describe your own.

A **job** is work Scout does for you on its own: a signal to watch for, and what to do when it fires. Some jobs run on a schedule, like your morning brief. Others run when something happens, like a prospect replying to your email. Scout runs them in the background and brings you the result in Slack, or by text if you'd rather.

## On by default

Scout turns the core jobs on as soon as it has what they need:

* [Inbox replies](/scout/how-scout-works/jobs/inbox-replies.md), once your inbox is connected.
* [Morning brief](/scout/how-scout-works/jobs/morning-brief.md), from your next workday.

## Offered, one at a time

Other jobs depend on how you sell, so Scout offers them one at a time, each with a real result from your own book. You see what the job does before you decide. Say yes to keep it running, or no, and Scout moves on. [Stalled deals](/scout/how-scout-works/jobs/stalled-deals.md) is the first of these, once your CRM is connected.

## Your own jobs

Describe a job to Scout, and it runs it from then on:

> Every weekday at 8, look for target accounts that visited pricing this week with no open deal, and draft a short note to the economic buyer.

Tell Scout the signal and what you'd send. In conversation you can run a job now to see what it does, pause it, change its schedule or time zone, or delete it. Scout names each job so you can refer to it later.

## What a job can and can't do

A job reads with your access and drafts in your voice. It doesn't send email, and it doesn't change your CRM or any other connected tool on its own: when a job would make a change, it brings you the change to apply. If a job's instructions are unclear while it runs, Scout takes the most reasonable reading and tells you what it assumed, rather than drafting on a guess.

A job may also stay quiet. When there's nothing worth your time, it doesn't message you.

## Catalog

<table data-full-width="true"><thead><tr><th>Job</th><th>What it watches</th><th>What you get</th><th>How you get it</th></tr></thead><tbody><tr><td><a href="/scout/how-scout-works/jobs/inbox-replies.md">Inbox replies</a></td><td>Prospects and customers writing to you</td><td>A reply drafted in your Drafts, in the thread</td><td>On once your inbox is connected</td></tr><tr><td><a href="/scout/how-scout-works/jobs/morning-brief.md">Morning brief</a></td><td>Your accounts, inbox and calendar</td><td>Which accounts are worth your time today, with drafts ready</td><td>On from your next workday</td></tr><tr><td><a href="/scout/how-scout-works/jobs/stalled-deals.md">Stalled deals</a></td><td>Deals in your pipeline that stopped moving</td><td>A check-in drafted for each</td><td>Offered once your CRM is connected</td></tr><tr><td>Your own</td><td>Any signal you describe</td><td>Whatever you told Scout to do</td><td>Describe it to Scout</td></tr></tbody></table>


---

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