> 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/set-up-samantha.md).

# Set up Samantha

Create Samantha as a Live Assistant agent: the name she joins meetings with, whether she speaks, her voice and her video avatar, then publish her.

Samantha is a **Live Assistant agent**. Her agent holds the name she joins meetings with, whether she speaks or only listens, and her voice and avatar. Set it up once, publish it, and every meeting you send her to uses the published version.

{% stepper %}
{% step %}

### Create the agent

On the [**Live Assistant agents**](https://app.spara.co/meeting-agents/live-assistant-agents) tab, click **New Live Assistant agent**, give it a name, and click **Create**. Its editor opens.

<figure><img src="https://821105055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTMt4EjieWT1FfljMBJHI%2Fuploads%2Fgit-blob-d19b56824cb892adeba46f1af4bcf914dc1b06f2%2FMeeting%20Agents%20Live%20Assistant%20List.png?alt=media" alt=""><figcaption><p>The Live Assistant agents tab</p></figcaption></figure>

1. **New Live Assistant agent**: Creates an agent. Only its name is asked for here.
2. **The agent**: Its name, the name it joins meetings as, and when it last changed. Click it to open the editor.
3. **Status**: **Draft** until you first publish it, then **Published**.
4. **Actions menu**: **Edit** or **Delete**. A deleted agent can't be sent to meetings, and its past sessions keep their history.
   {% endstep %}

{% step %}

### Name her and give her a voice

<figure><img src="https://821105055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTMt4EjieWT1FfljMBJHI%2Fuploads%2Fgit-blob-3b187c8e74386e5a6dbcfc09ec93742642cbdcf2%2FMeeting%20Agents%20Live%20Assistant%20Editor.png?alt=media" alt=""><figcaption><p>The Live Assistant agent editor, for an agent that speaks</p></figcaption></figure>

1. **Name in the meeting**: She joins as her wake phrase's name plus a descriptor, and people call on her by the name alone. Pick the **Wake phrase** from the list: **Hey Samantha** makes her Samantha, and **Hey Spara** makes her Spara. Only a phrase with a trained audio model can wake her, so those are the choices, and a new agent starts on "Hey Spara". Then pick a **Descriptor** (**Sales Engineer**, **Meeting Assistant** or **Assistant**), or **None** to join by the name alone. The line under the fields shows the result, for example "Joins as Samantha Sales Engineer · wakes on “Hey Samantha”".
2. **Speaks in the meeting**: Off, she only listens, and only you see her answers. On, she also answers out loud once someone says her wake phrase, and presents your product demos on her screenshare.
3. **Voice**: Shows once she speaks. Click it to pick from the voice catalog, filtered by gender and accent, and use the play button to hear a sample. An agent that speaks needs a voice before you can publish it.
4. **Video Avatar**: Shows once she speaks. Pick a provider (**Runway** or **Anam**) and an avatar to put a face on her camera tile in the meeting, or **None** for voice alone. If the list is empty, you can paste an avatar ID or leave it blank.

{% hint style="info" %}
The descriptor is the role the meeting sees after her name, so "Samantha Sales Engineer" is the name to expect in the participant list.
{% endhint %}
{% endstep %}

{% step %}

### Save and publish

Use the buttons at the top right of the editor (5 and 6 in the screenshot above).

* **Save draft** keeps your changes as the draft.
* **Publish** makes the saved draft the published version. It stays off while you have unsaved changes, or while the agent speaks without a voice.
* **Version history** lists past versions, so you can compare one with your changes or restore it.
* Once a published agent has a newer draft, the menu next to **Publish** offers **Discard unpublished changes**.
  {% endstep %}
  {% endstepper %}

Samantha goes into each meeting with her published version, or her draft if she has never been published. Spara pins that version when you send her, so publishing during a call doesn't change a Samantha who is already in it.

Next: [Send Samantha to a meeting](/solutions-engineer/getting-started/send-samantha-to-a-meeting.md).


---

# 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/set-up-samantha.md?ask=<question>&goal=<user_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.