> 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/drafts.md). # Drafts and approval Everything Scout writes to a prospect is a draft in your own inbox. Nothing sends until you send it. Everything Scout writes to a prospect is a draft. It lands in your own Drafts folder, under your name and with your signature, and nothing sends until you send it. ## Where drafts land * **Your Drafts folder**, in Gmail or Outlook. A reply or follow-up sits in its thread, with the earlier email quoted beneath it. A new email is a fresh draft. * **In Slack**, as a card under Scout's message: the recipients, subject and full body, with **Edit**, **Discard**, **Open in Gmail** and **Send** buttons. Send is your click. It sends the draft from your own mailbox. * **By text**, Scout tells you the draft is ready in your Drafts and gives you the gist. Scout tells you what it drafted and why. Every draft carries its reasoning, what Scout saw, what it concluded and why now, which you and your team can read. ## Editing Edit in Gmail, in Outlook, or with **Edit** in Slack. Scout sees your edits: if you later ask it to change the draft, it builds on your version, not its own. If a draft is open in Gmail while Scout revises it, close and reopen it to see the new version. ## What goes into a draft * **Only what Scout can back up.** Every fact about the recipient, their company, their timing or your earlier contact comes from a record Scout read: their email, your CRM, a call note, a Spara conversation, or your own words. Anything Scout can't tie to a record is left out, or put to the recipient as a question. * **Nothing only you know.** Scout never invents a price, a date or a commitment. When a draft needs one, it asks you first. * **Checked recipients.** Addresses are checked when the draft is created. One that looks mistyped or likely to bounce is flagged to you. * **Files.** Scout can attach files, including from your Google Drive, and place images in the body. ## How drafts close A draft closes on its own when it's no longer needed: * You **send** it. Scout sees the sent email. * You **discard** it, with Discard in Slack or by deleting it in your inbox. Discarding in Slack removes it from your Drafts too. * The prospect **writes to you** another way, or you **write to them** yourself. Scout closes the draft rather than leaving a stale one behind. Scout keeps one open draft per person. If it already has one for someone, it revises that draft instead of making a second. ## Frequently asked questions ### Can Scout send for me if I tell it to? No. Scout has no way to send an email. The **Send** button in Slack sends from your mailbox on your click, and it's the only way a draft goes out without opening your inbox. ### What if I edit a draft in Gmail and then ask Scout to change it? Scout works from your edited version. Your changes 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/how-scout-works/drafts.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.