Channels are the ways users talk to agents: Telegram, MAX, Bitrix24, SIP
telephony, the web widget, the mobile client and generic webhook channels. The
screen shows installed channels only: their state, capabilities, connector
configuration, agent bindings and access control. New connectors are installed
on the Plugins screen — an uninstalled connector
does not appear here.
List and statuses
Each channel is a row with a connector icon, name, a single state badge (online /
error / transitional / “no connector”) and its conversation and message volume.
There is search and sorting by name or volume.
Channel features
Each channel has a collapsible features block — toggles grouped as:
Features a channel doesn’t support are shown disabled. Toggling is applied
optimistically and reconciled with the server.
Configuring installed channels
The collapsible “Configure installed channels” block shows cards for the
installed channel connectors — this is where their credentials and parameters
are edited (a form built from the plugin manifest), with live status while a
deploy is in progress.
Bindings: which agent serves which channel
The “Bindings” block sets a default agent per channel — the rule “new
conversations on channel X are handled by agent Y”. Existing conversations keep
their agent (the per-conversation binding wins); an empty value means the
connector’s default agent. The choice is saved immediately on change.
Access control: reply only to known users
The “Access control” block is a single switch — “Reply only to known
users” (ON by default). While it is on, agents reply only to people
provisioned in AiHummer (users bound to the instance) — random members of a
connected chat and unknown senders get no reply: the agent turn never
starts, and the unknown sender receives a one-time hint to ask the
administrator to add them. Turn the switch off to let agents reply to anyone.
The setting is stored in the settings catalog under the key
AIHUMMER_INBOUND_REQUIRE_BINDING.
Voice and SIP
The voice accordion shows the state of duplex, echo cancellation (AEC), the VAD
threshold and barge-in. Telephony details are in SIP and
STT/TTS.
Connecting a channel
The connectors themselves (Telegram, MAX, Bitrix24, SIP, widget) are installed
as plugins on the Plugins/Marketplace screen —
the full catalog lives there. Once installed, the channel appears here: set its
credentials in “Configure installed channels”, then enable features and assign
an agent in “Bindings”.
**Channels** are the ways users talk to agents: Telegram, MAX, Bitrix24, SIP
telephony, the web widget, the mobile client and generic webhook channels. The
screen shows **installed channels only**: their state, capabilities, connector
configuration, agent bindings and access control. New connectors are installed
on the [Plugins](/en/v1.0/webui/marketplace) screen — an uninstalled connector
does not appear here.
## List and statuses
Each channel is a row with a connector icon, name, a single state badge (online /
error / transitional / "no connector") and its conversation and message volume.
There is search and sorting by name or volume.
## Channel features
Each channel has a collapsible **features** block — toggles grouped as:
- **Messages** — replies, threads, edit, delete, mentions, pins.
- **Reactions & statuses** — reactions, typing, read receipts.
- **Interactive** — keyboards, streaming.
- **Sending** — drafts, scheduled messages.
Features a channel doesn't support are shown disabled. Toggling is applied
optimistically and reconciled with the server.
## Configuring installed channels
The collapsible **"Configure installed channels"** block shows cards for the
installed channel connectors — this is where their credentials and parameters
are edited (a form built from the plugin manifest), with live status while a
deploy is in progress.
## Bindings: which agent serves which channel
The **"Bindings"** block sets a **default agent** per channel — the rule "new
conversations on channel X are handled by agent Y". Existing conversations keep
their agent (the per-conversation binding wins); an empty value means the
connector's default agent. The choice is saved immediately on change.
## Access control: reply only to known users
The **"Access control"** block is a single switch — **"Reply only to known
users"** (ON by default). While it is on, agents reply only to people
provisioned in AiHummer (users bound to the instance) — random members of a
connected chat and unknown senders get **no reply**: the agent turn never
starts, and the unknown sender receives a one-time hint to ask the
administrator to add them. Turn the switch off to let agents reply to anyone.
The setting is stored in the settings catalog under the key
`AIHUMMER_INBOUND_REQUIRE_BINDING`.
## Voice and SIP
The voice accordion shows the state of duplex, echo cancellation (AEC), the VAD
threshold and barge-in. Telephony details are in [SIP](/en/v1.0/channels/sip) and
[STT/TTS](/en/v1.0/voice/stt-tts).
## Connecting a channel
The connectors themselves (Telegram, MAX, Bitrix24, SIP, widget) are installed
as plugins on the [Plugins/Marketplace](/en/v1.0/webui/marketplace) screen —
the full catalog lives there. Once installed, the channel appears here: set its
credentials in "Configure installed channels", then enable features and assign
an agent in "Bindings".
## Next
- [Telegram](/en/v1.0/channels/telegram), [MAX](/en/v1.0/channels/max),
[Bitrix24](/en/v1.0/channels/bitrix24),
[Web widget](/en/v1.0/channels/web-widget) — per channel.
- [Plugins/Marketplace](/en/v1.0/webui/marketplace) — installing connectors.
- [Schedules](/en/v1.0/webui/notifications) — scheduled messages into channels.