Channel Setup Guides
Channels connect your agent to the platforms where your users communicate. Each agent can be connected to multiple channels simultaneously.
Supported Channels
| Channel | Status | Key Feature |
|---|---|---|
| Telegram | Full support | Real-time streaming, rich media |
| Slack | Full support | Workspace integration, threads |
| Discord | Full support | Server bots, DMs and channel messages |
| Full support | Inbound/outbound email | |
| Full support | WhatsApp Cloud API (business number) | |
| WhatsApp Web | Transport support | Personal WhatsApp with restricted sender trust; owner pairing intentionally unavailable |
| Matrix | Full support | Federated chat via a Matrix homeserver |
| Microsoft Teams | Transport support | Bot Framework integration; owner pairing intentionally unavailable |
| Web Chat | Built-in | Always available in the dashboard |
How Channels Work
When a message arrives on any channel:
- The channel transport receives the message
- Lenno routes it to the correct agent
- The agent processes the message using its AI provider
- The response is sent back through the same channel
Conversations are threaded per-channel, so context stays separate across platforms.
Owner Identity And Sender Trust
Connecting a bot, webhook, account, or sidecar authenticates the transport; it does not prove that an external sender is the agent owner. External channels start unlinked and fail closed. Ordinary senders are ignored, while an explicitly solicited contact may converse only with restricted trust.
The current effective owner can generate a one-time code for one exact channel
in Access & Trust, then send the exact provider-specific message shown
there. Pair in a private or direct conversation. In a shared room, Lenno also
requires the authenticated sender to match a separately configured stable
owner identity; the configured value never grants authority on its own. Slack
and Discord use the ordinary message lenno pair <code> because their current
transports consume ordinary message events rather than registered slash-command
interactions.
Email owner proof is intentionally unavailable until Lenno has an explicit mailbox-possession challenge; a delivery webhook or domain authentication is not proof of one human mailbox. Microsoft Teams owner pairing is likewise unavailable until its transport checks are hardened. WhatsApp Web owner pairing is disabled while its Baileys sidecar shares the agent container: a co-resident process cannot independently prove owner identity against that container. Allowed WhatsApp Web senders remain restricted and cannot command or approve as the owner. Each guide documents its exact flow.
Web Chat
Every agent has a built-in web chat interface accessible from the agent’s Chat tab in the Lenno dashboard. This requires no setup and is always available.