> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Meeting Presence

> How the bot appears to everyone else in the meeting: its roster name, its camera tile, and what it says on arrival.

The bot is a participant, not just a recorder. Everyone in the room sees something -- a name in the roster, a camera tile, and often a message in chat as it joins. This section covers that identity. For making the bot *act* once it is there, see [Controlling the Bot](/docs/meeting/control).

## Roster Name

The bot joins as a visible participant with its own entry in the meeting roster. By default it appears as **Meeting Bot**; set `bot_name` (1-100 characters) when you create the session to control the name other attendees see:

```bash theme={null}
curl -X POST https://api.telnyx.com/v2/meeting_sessions \
  -H "Authorization: Bearer $TELNYX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "meeting_url": "https://meet.google.com/abc-defg-hij",
    "bot_name": "Q3 Decisions Scribe"
  }'
```

You can also rename the bot before it joins with `PATCH /v2/meeting_sessions/{id}` while the session is `scheduled`.

There is no API for a custom profile picture. The bot uses the meeting platform's default profile for its account, so its roster entry is the name above plus the platform's standard bot appearance.

## Identity

What the bot shows on camera is a three-way choice, because the service treats it as one:

* **Nothing** -- the default. A plain roster entry with no camera tile.
* [**Still image**](/docs/meeting/presence/still-images) -- a static JPEG shown as the bot's camera tile.
* [**Digital avatar**](/docs/meeting/digital-avatars) -- a rendered avatar, lip-synced to everything the bot says.

An active digital avatar takes precedence over a still image: the image is ignored and its URL is never fetched. A session can hold both, but only the avatar will ever be seen.

## Introductions

The bot can announce itself the moment it is admitted, by voice, in chat, or both. Because these are create parameters rather than actions, they are documented with the rest of the create request -- see [Announce the Bot on Arrival](/docs/meeting/join-meeting/introductions).

## Related

* [Controlling the Bot](/docs/meeting/control) -- make the bot speak, post to chat, or run an assistant
* [Still images](/docs/meeting/presence/still-images) -- a static camera tile for the bot
* [Digital avatars](/docs/meeting/digital-avatars) -- render the bot as a speaking avatar on camera
* [Announce the Bot on Arrival](/docs/meeting/join-meeting/introductions) -- `speak_on_enter` and `chat_on_enter`
* [Join a Meeting](/docs/meeting/join-meeting) -- create a meeting session and send the bot