> 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/solutions-engineer/in-the-meeting/what-the-meeting-sees.md). # What the meeting sees What the prospect and everyone else in the meeting see and hear when Samantha or an AI Prospect is in the call, and what stays private to you. Samantha joins as a participant with her own name, so the prospect knows she's there. What else they see depends on whether she speaks. * **A recording notice**: Every agent posts one in the meeting chat when it joins. On Teams, the notice may not appear: an agent can post only when the meeting host's Teams setup lets anyone chat. * **A Samantha who only listens**: A participant with her meeting name, for example "Samantha Sales Engineer". She doesn't show a camera feed or share her screen. * **A Samantha who speaks**: A camera tile with her avatar, or the Spara logo when she has none. A ring lights up around the tile while she speaks, and the about-to-speak signal plays just before. While she presents, she also shares her screen, showing the visual or AI demo. * **An AI Prospect**: A camera tile with its avatar, or an "AP" badge labeled "AI Prospect". A ring lights up while it speaks. ## What stays with you Nobody in the meeting sees your [Live session screen](/solutions-engineer/in-the-meeting/live-session-screen.md). The answer cards, the transcript, the participants panel and the voice and screenshare controls are only in Spara. The meeting sees and hears only what Samantha says and shares. --- # 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/solutions-engineer/in-the-meeting/what-the-meeting-sees.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.