Product guide
Chat channels
Put the assistant where your team already talks — Teams, Slack, WhatsApp, the website widget and more.
A channel puts the assistant inside a messaging tool people already use, instead of a separate web chat — answers work exactly the same underneath: grounded, cited, access-controlled, only the doorway changes. Sixteen platforms are covered, from the website widget and workplace suites like Slack and Teams, through consumer apps like WhatsApp and Telegram, to email, SMS, self-hosted team chat, and a developer Messaging API/MCP.
Every channel authenticates the same way: one platform-issued credential — a bot token, an app secret, an access token — created in that platform's own developer console and pasted in here. None of them use a “Sign in with…” flow. They differ in how messages arrive: most register a webhook, so the platform calls this server directly and needs a public https address (set once, under Settings); Telegram, Matrix, Mattermost and email instead have the assistant reach out, and need no public address at all.
Choosing between them is mostly about where the conversation already happens: Slack, Teams, Google Chat, Mattermost, Zulip or Matrix for a team already working there; WhatsApp, Telegram, Messenger, Viber, LINE or a phone number for people outside the organisation; the website widget for anonymous visitors, who only ever ask as guests; email for people who'd rather send a message than open an app; and the Messaging API/MCP to wire the assistant into your own application or an AI tool directly. Every channel can also be opened to guests, on top of whoever you set up by hand.
The channels
- OverviewA channel puts the assistant inside a messaging tool: Microsoft Teams, Slack, Google Chat, Telegram, WhatsApp, Viber, a Twilio phone number (SMS), Discord, Facebook Messenger / Instagram, email,…
- TelegramThe fastest channel to set up: no server exposure, no approval process, no webhook to register — the assistant picks up messages itself within seconds, even from a deployment with no public address.
- WhatsAppWhatsApp Business Cloud API, hosted by Meta. It needs a Meta developer app, and this server reachable from the internet — set the public base URL in Settings before you start.
- SlackA Slack app your team DMs, or @mentions in a channel for an answer everyone sees (it replies in a thread).
- ViberA Viber bot people message directly, one to one. Viber IDs are private — unlike a Telegram username or a phone number, nobody can be set up by their Viber identity ahead of time; people are assigned…
- Phone number (Twilio SMS / WhatsApp)A phone number people text — plain SMS through Twilio, and WhatsApp too when the number is WhatsApp-enabled in Twilio. The admin-friendliest channel: a phone number is a person's identity, so enter…
- DiscordA Discord app your team uses with /ask — in servers and in DMs. Server answers are private to the asker by default (ephemeral), so document access never leaks to the room.
- Email (auto-reply)A mailbox people email their questions to; the answer comes back as a reply, citing its sources (a “Sources:” link to the sender's own web chat, where each citation opens the exact passage). Senders…
- Microsoft TeamsThe assistant inside Microsoft Teams — personal chats, and @mentions in team channels. Everything else is ready in the product; the only prerequisite is a one-time Azure Bot registration, about ten…
- Facebook Messenger / InstagramMessages to your Facebook Page — and to the Instagram professional account connected to it — answered automatically, one to one, as the Page. Typically customer-facing: pair it with guest access…
- Google ChatThe assistant inside Google Chat (Workspace) — direct messages, and @mentions in spaces. People are matched to their accounts by their work email automatically, and replies are instant HTTP…
- Matrix / ElementA bot account on your Matrix homeserver — for teams on Element or any other Matrix client, including fully self-hosted servers. The assistant connects out to the homeserver, so no public URL is…
- MattermostA Mattermost bot your team DMs or @mentions — the self-hosted option where nothing leaves your network: the assistant connects out to your Mattermost server, which never needs to reach this…
- ZulipA Zulip bot your team DMs or @mentions — created as an “outgoing webhook” bot in Zulip's own settings, nothing else to run. Zulip delivers each message to the assistant and reads the reply straight…
- LINEThe assistant on a LINE official account — people message it directly, one to one, or @mention it in a group chat. Replies are push messages, so they work on every LINE plan.
- Website widgetA chat bubble on your own site or intranet — one script tag, no third-party platform, no account, no cost: the widget talks straight to this deployment and makes no other request. Visitors are always…
Webhook, or the assistant calling out
Most channels work by registering a webhook: the platform posts to this server the moment someone messages, so it needs a public https address, set once under Settings → Public address. Telegram, Matrix, Mattermost and email never need that, because the assistant reaches out to the platform instead. Slack and Discord can work either way: turn on Socket Mode (an app-level token, in that channel's settings) or “Plain direct messages” (Discord) and the assistant connects outward for those too — useful on a private network, or before a public address exists.
Last updated 20 Sep 2026