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

# Chatwoot (Support Bot)

> Connect Chatwoot to KnoxCall for the support widget and the assistant's proactive messages — a dedicated agent account, its API access token and your Chatwoot base URL.

# Chatwoot (Support Bot)

Backs the in-app support widget and the messages the assistant posts into conversations.

**Scope: Global defaults** only — a platform operator feature. A self-hosted deployment that does not run its own Chatwoot can leave it unconfigured; the widget stays off.

## 1. In Chatwoot

1. Create (or pick) a **dedicated agent account** for the integration and add it to the support inbox. An agent token inherits that agent's access, so do not use your own account, and give the agent only that inbox.
2. Sign in as that agent → **Profile settings** → copy the **Access token**.
3. Note your Chatwoot base URL: `https://app.chatwoot.com`, or your own host if self-hosted.

## 2. Enter it in KnoxCall

**Settings → Integrations → Global defaults → Chatwoot (support bot)** → *Configure*:

| Field            | Value                                  |
| ---------------- | -------------------------------------- |
| **Access token** | The agent's API access token           |
| **Base URL**     | e.g. `https://support.your-domain.com` |

**Save credentials.**

## 3. Verify

Open the support widget in the app and send a message; it should appear in the inbox as a conversation.

## Things that bite

* **Rotating the agent's token invalidates the old one immediately.**
* **Environment fallback**: `CHATWOOT_*` variables are used on a self-hosted host when no token is stored, so an empty row does not prove the widget is off.

## Related

* [Support chat](/support/support-chat)