> 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/readme.md). # Meet Samantha Samantha is Spara's AI Solutions Engineer. She joins your Zoom, Google Meet and Microsoft Teams calls, hands you answers as the prospect asks, and can answer out loud and demo your product. Spara staf **Samantha** is the AI Solutions Engineer for your sales calls. She joins your Zoom, Google Meet or Microsoft Teams meeting as a participant, listens, and hands you an answer card the moment a prospect raises something you need to address. When you let her speak, she also answers out loud when someone calls on her, puts your product visuals on her screenshare, and runs narrated demos. Most reps share a solutions engineer with several teammates and can't get one onto every call. Samantha gives every rep one on every call, so technical questions get answered in the meeting instead of in a follow-up email. {% hint style="warning" %} Samantha is open to Spara staff only for now. Customers can't see her pages in the app or reach the links on this site. {% endhint %} ## What Samantha does for you * **Answers as the call happens**: Every question from the prospect side becomes a card on your [Live session screen](/solutions-engineer/in-the-meeting/live-session-screen.md), with the answer and the supporting points. Only you see the cards. * **Speaks when you call on her**: Say "Hey Samantha" and she answers the question out loud, in the meeting, in her own voice. She stays quiet otherwise, so she never talks over you or the prospect. * **Shows your product**: With a product demo attached, she can put the right visual on her screenshare as she answers, and walk through a narrated AI demo of a topic the prospect asks about. * **Lets you practice**: An [AI Prospect and practice calls](/solutions-engineer/practice/ai-prospect.md) plays a buyer from a persona you write, so you can rehearse a call, with Samantha's cards alongside, before a real prospect is on the line. ## How it works 1. **Set her up.** Pick her wake phrase, voice and avatar, and whether she speaks or only listens. See [Set up Samantha](/solutions-engineer/getting-started/set-up-samantha.md). 2. **Send her to a meeting.** Paste the meeting link and she joins as her own participant. Or let your calendar send her to your meetings for you. See [Send Samantha to a meeting](/solutions-engineer/getting-started/send-samantha-to-a-meeting.md) and [Calendar auto-join](/solutions-engineer/getting-started/calendar-auto-join.md). 3. **Run the call.** Follow her cards, turn her voice on and off, and control what she shares from the [Live session screen](/solutions-engineer/in-the-meeting/live-session-screen.md). The prospect sees a participant named Samantha; see [What the meeting sees](/solutions-engineer/in-the-meeting/what-the-meeting-sees.md). ## Where to find her in the app Samantha is a **Live Assistant agent** on the [**Meeting Agents**](https://app.spara.co/meeting-agents) page, which the **Coseller** link under **Assist** in the sidebar opens. The page has four tabs: * **Dispatch**: Send agents to a meeting and reopen recent ones. * **Calendar**: Let your calendar send Samantha to your meetings. * **Live Assistant agents** and **AI Prospect agents**: Create and edit each type's agents. Each agent has a draft and a published version. You edit the draft, then publish it. ## Where to go next * [Set up Samantha](/solutions-engineer/getting-started/set-up-samantha.md): the name she joins with, her voice and her avatar. * [Live session screen](/solutions-engineer/in-the-meeting/live-session-screen.md): every part of the screen you run the call from. * [FAQ](/solutions-engineer/help/faq.md): the questions reps ask first. --- # 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/readme.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.