> 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/talking-to-scout.md). # Talking to Scout Ask Scout for what you need in plain words, in Slack, by text or by email. It does the work, or asks one question when it needs something only you know. Scout is a conversation. Ask for what you need in plain words, and it does the work or asks one question when it needs something only you know. ## Where you talk * **Slack**: message Scout in its direct message. Each thread is one conversation, so reply in the thread to continue it. When a job has something for you, Scout posts a new message, and your reply to it starts a fresh conversation. * **Text**: text Scout from your linked phone. Scout writes the way a person texts, a thought or two at a time, with nothing you have to scroll for. Ask it to email you anything longer. * **Email**: ask Scout to email you a result, and reply to any email from Scout to continue the conversation. If you use both Slack and text, Scout answers where you wrote. Say "text me that" or "send it to my Slack" to get something on the other. ## What to ask * **Prep before a meeting**: "Heading into Linear in 10 minutes. What should I lead with?" * **What's worth your time**: "Who should I reach out to today, and why?" * **What changed**: "What's new at Ramp since last month?" Scout reads your mail, your CRM, your calendar and anything else you've connected. * **A draft**: "Draft a follow-up to Marshall about the routing question." It lands in your Drafts. See [Drafts and approval](/scout/how-scout-works/drafts.md). * **Research**: "Who runs security at Asana?" Scout researches companies and people, and finds the right person at an account. * **A job**: "Every Monday, find deals in my pipeline that haven't moved in two weeks and draft a check-in." See [Jobs](/scout/how-scout-works/jobs.md). * **A reminder**: "Check back with me at 3 about the Rippling proposal." * **Your CRM**: "Log a note on the Houzz deal: budget approved, legal next." Scout updates HubSpot or Salesforce as you, when you ask. * **Your calendar**: "Move my Tuesday call with Brex to Wednesday morning." Scout says exactly what it will change, and changes it only after you say yes. * **Memory**: "Remember that I don't pitch on Fridays." "Forget what I said about Vercel." * **Connections and teammates**: "Connect my HubSpot." "Invite ." You can also send a voice note, and Scout transcribes it. ## What Scout won't do on its own Scout drafts; you send. It never sends an email. It messages someone on LinkedIn, changes your calendar or updates your CRM only after you say yes in the conversation. A job that runs while you're away only reads and drafts: it brings you anything it would change, for you to apply. When Scout can't do something, such as read a tool that isn't connected, it says so rather than guessing. --- # 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/talking-to-scout.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.