> ## 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.

# Chat

> Post messages to the meeting's native chat as the bot, and read what participants send back.

`POST /v2/meeting_sessions/{id}/actions/send_chat` posts a message to the meeting's native chat as the bot.

```bash theme={null}
curl -X POST https://api.telnyx.com/v2/meeting_sessions/mtgsess_9b2f.../actions/send_chat \
  -H "Authorization: Bearer $TELNYX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "text": "I will send the summary after this call." }'
```

Native chat is supported on Google Meet, Zoom, and Teams. Webex does not support native chat, although joining and audio/video output remain supported.

Chat is two-way: messages other participants post are delivered as `chat.message` events, while the bot's own posts echo back as `chat.sent`. Read them on the [WebSocket stream](/docs/meeting/live-transcript) for live delivery, or from the stored [event history](/docs/meeting/events). There is no chat webhook -- [webhooks](/docs/meeting/webhooks) carry session status, transcript completion, recordings and artifacts only. The full request schema is on [Send chat in a meeting session](/api-reference/meeting-session-actions/send-chat-in-a-meeting-session).

Unlike [speak](/docs/meeting/control/speak), chat keeps working with a [Telnyx AI Assistant](/docs/meeting/ai-assistants) attached. The assistant owns the voice, not the chat.

To post a message automatically the moment the bot joins, see [Announce the Bot on Arrival](/docs/meeting/join-meeting/introductions).

## Related

* [Controlling the Bot](/docs/meeting/control) -- the WebSocket alternative and the action error envelope
* [Speak](/docs/meeting/control/speak) -- say it out loud instead
* [Announce the Bot on Arrival](/docs/meeting/join-meeting/introductions) -- `chat_on_enter`
* [Session Events](/docs/meeting/events) -- read `chat.message` and `chat.sent`