Creating a bot
A bot is the thing people talk to. It belongs to one tenant, holds the model configuration, and carries the connections to the channels it appears on.
Bots are created in the admin console, under Bots. There is no way to create one from the web app.
Before you start
You need two things, and the order matters:
- A tenant to put the bot in. The tenant selector at the top of the Bots page decides where the bot is created; there is no default.
- An API key for the model provider. Without one, the bot is created but cannot answer. The page tells you when a key is missing. See API keys.
Creating it
Select the tenant, choose New Bot, and fill in:
| Field | Notes |
|---|---|
| Name | What people see |
| Description | For your own reference |
| Provider | OpenAI or Anthropic. These are the two choices. |
| Model | A model belonging to that provider |
Then save. The bot exists but is not reachable yet — it has no channels and no authorized chats.
Older documentation and some interfaces imply a third provider. There isn't one: the provider list is OpenAI and Anthropic, plus, on deployments that enable it, a private-LLM provider used for a separate purpose. Selecting anything else is rejected.
Making it reachable
Creating a bot is the first of three steps, and a bot that has only had the first done is completely silent — which is easy to mistake for a fault.
- Create the bot (this page).
- Connect a channel — see Integrations.
- Authorize the chats, and assign this bot to them — see Telegram.
What else is on the bot page
Beyond name and model, a bot carries settings for context and archival — how much history it is given, how long that history stays in fast storage, whether events are included. These are the per-bot layer of the resolution described in Context & memory; anything you leave alone falls through to the tenant or global value.
Several bots per tenant is normal — a customer-facing bot and an internal one can differ in model, channels and authorized chats without interfering.