> 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/inbox-replies.md). # Inbox replies When a prospect or customer writes to you, Scout drafts the reply in your inbox and tells you it's there. When a prospect or customer writes to you, Scout drafts the reply before you've opened the email. The draft sits in the thread in your Drafts folder, and Scout tells you it's there. **On by default** once your inbox is connected. See [Gmail and Outlook](/scout/connections/gmail-and-outlook.md). ## What it does * **Watches for mail that needs your answer**: a reply to an email you sent from a Scout draft, or any other incoming email that calls for a response from you. Newsletters and notifications don't count. * **Reads the whole thread** the way you would, and writes what you'd actually send next. * **Drafts in the thread**, in your voice, with your signature, so you open it, read it, and send. * **Asks when something's missing.** If the reply needs something only you know, such as a price or a date, Scout asks you first and drafts once you answer. It never fills the gap with a guess, because a draft in your inbox can go out without a second read. ## Tuning it Tell Scout how you want replies handled, in conversation: which senders to leave alone, how formal to be, what never to commit to. Scout updates the job rather than making a second one. --- # 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/inbox-replies.md?ask=&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.