> 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/getting-started/send-samantha-to-a-meeting.md).
# Send Samantha to a meeting
Send Samantha into a Zoom, Google Meet or Microsoft Teams call from the Dispatch tab, choose what she can present, and follow her from Recent meetings.
Start or join the meeting yourself, copy its link, then fill in the form on the [**Dispatch**](https://app.spara.co/meeting-agents) tab. Samantha joins as her own participant and posts a recording notice in the meeting chat when she arrives. The host may need to admit her from the waiting room.
To skip the form for your own meetings, connect your calendar instead: see [Calendar auto-join](/solutions-engineer/getting-started/calendar-auto-join.md).
## The Dispatch form
Fields 4 to 6 appear only when they apply.
Sending a Samantha who speaks and an AI Prospect to a Zoom call
1. **Meeting link**: A Zoom, Google Meet or Microsoft Teams link. You can leave off the `https://`.
2. **Live Assistant agent**: Samantha, or another of your Live Assistant agents, or **None**. Agents that have never been published are marked **Draft**.
3. **AI Prospect agent**: One of your AI Prospect agents, or **None**. Pick at least one agent across 2 and 3. See [AI Prospect and practice calls](/solutions-engineer/practice/ai-prospect.md).
4. **Product demos (optional)**: Shows once you pick a Live Assistant. The product demo agents whose visuals and topics Samantha can present. Only a Samantha who speaks presents them; the cards of one that only listens offer no visuals or demos. See [Product Demo](https://docs.spara.com/build/channels/product-demo) for setting up visuals and topics.
5. **Sales Engineer leads the call**: Shows only for a Samantha who speaks. On, her voice is on from the start and she answers whatever is meant for her with no wake phrase; only your live session screen turns it off. Off, her voice starts off until someone says her wake phrase or you turn it on from the live session screen.
6. **About-to-speak signal**: Shows only for a Samantha who speaks. What the meeting sees on her camera tile just before she speaks.
7. **Send to meeting**: Sends each agent as its own participant. With Samantha, her [Live session screen](/solutions-engineer/in-the-meeting/live-session-screen.md) opens right away. With only an AI Prospect, you see "Sent to the meeting. The host may need to admit it."
The about-to-speak signal options:
| Signal | What the meeting sees |
| ----------------------- | ------------------------------------------------------------------------- |
| **Spotlight** (default) | The middle of the tile brightens and the edges shade. |
| **Glow while on** | A steady glow whenever her voice is on, breathing just before she speaks. |
| **None** | The tile never changes. |
| **Pulse** | The tile pulses brighter and back. |
| **Glow** | A steady glow comes in from the edges. |
| **Breathing glow** | The glow slowly swells and fades. |
| **Edge sweep** | A band of light circles the frame. |
Each agent goes in with its published version, or its draft if it has never been published. Spara pins that version when you send, so publishing during a call doesn't change an agent that's already in it.
## Recent meetings
Under the form, **Recent meetings** lists everything sent to meetings from this Spara account, newest first.
Recent meetings, with one call still in progress
1. **The meeting**: Its platform and link, who sent the agents, and when.
2. **Each agent sent**: Its name, type and status.
3. **Open**: Opens Samantha's [Live session screen](/solutions-engineer/in-the-meeting/live-session-screen.md), during or after the call. AI Prospect sessions have no live screen.
4. **Leave**: Takes that one agent out of the meeting after you confirm. Anything it saved so far stays.
| Status | Meaning |
| -------------------------- | --------------------------------------------------------------------------- |
| **Joining** | She is on her way into the meeting. |
| **Waiting to be admitted** | She is in the waiting room. The host needs to admit her. |
| **In call** | She is in the meeting. |
| **Ended** | She left, or the meeting ended. |
| **Failed** | She couldn't join, or her call failed. The reason shows next to the status. |
## Getting her out of the call
Click **Leave** next to Samantha in **Recent meetings**, or **Leave meeting** on her live session screen. She also leaves on her own about two minutes after the last person leaves. An AI Prospect sent with her has its own **Leave**.
---
# 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/getting-started/send-samantha-to-a-meeting.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.
