> For the complete documentation index, see [llms.txt](https://university.mindstudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.mindstudio.ai/video-courses/masterclass-sessions/ai-agents-for-partnerships-masterclass.md). # AI Agents for Partnerships Masterclass AI agents can support partnerships, sales, and business development teams {% embed url="" %} We show how real AI agents can support partnerships, sales, and business development teams. Led by our Director of Partnerships, Dannielle Sakher, and CEO, Dmitry Shapiro, this practical session explains how to use AI agents that scale your GTM motion, with no costs or setup. ✅ Personalize outreach\ ✅ Prep for meetings\ ✅ Surface red flags in deals\ …and more. --- # 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://university.mindstudio.ai/video-courses/masterclass-sessions/ai-agents-for-partnerships-masterclass.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.