Channels

The same assistant, with the same knowledge, rules and actions, can answer outside your website. Each channel runs on your own provider account, so messages and phone numbers stay yours. Connect one in the dashboard under Assistants → your assistant → Channels (admins); the webhook URL to paste into the provider is shown there.

Every reply starts a thread with your AI disclosure, includes its sources as links, and appears in your inbox. Messages are checked against the provider’s signature before anything is read, and a provider retrying the same message gets one answer.

Email (Mailgun)

People email your support address; the assistant replies in the same thread, with its sources.

You need: A Mailgun account with a sending domain you’ve verified (for example mg.yourcompany.com).

In Mailgun, open Sending → Domains and note your sending domain and its region (US or EU).
Open Account → API Keys and create a private API key (used to send replies).
Open Sending → Webhooks and copy the HTTP webhook signing key (used to check that mail really comes from Mailgun).
Here, add the Email channel: your support address (for example help@mg.yourcompany.com), the sending domain, the region, the API key and the signing key. Save to get the webhook URL.
In Mailgun, open Receiving → Create route: expression type “Match recipient”, the support address, action “Forward” to the webhook URL from the dashboard, and tick “Store and notify”. Save.
Send an email to the support address. The reply arrives within a minute; you’ll see it under Recent messages here and in Conversations.

Replies keep the thread (In-Reply-To and References), so a customer’s follow-up continues the same conversation.
Auto-replies, bounces, mailing lists and your own messages are never answered, so two auto-responders can’t loop.
If your support address is on your main domain (help@yourcompany.com), forward it to the Mailgun address with your email provider instead.

WhatsApp (Meta WhatsApp Cloud API)

Customers message your WhatsApp Business number; the assistant answers there.

You need: A Meta Business account and a Meta developer app with the WhatsApp product added. A phone number registered for the WhatsApp Cloud API (the test number works for trying it).

In developers.facebook.com, open your app → WhatsApp → API Setup and copy the Phone number ID.
Create a permanent access token: Business Settings → Users → System users → add a system user, give it the app and your WhatsApp account, and generate a token with whatsapp_business_messaging and whatsapp_business_management.
Open App settings → Basic and copy the App secret (used to check that messages really come from Meta).
Here, add the WhatsApp channel with the Phone number ID, the access token and the app secret. Save to get the webhook URL and verify token.
In your app, open WhatsApp → Configuration → Webhook → Edit: callback URL the webhook URL from the dashboard, verify token the verify token from the dashboard. Verify and save, then subscribe to the “messages” field.
Send a WhatsApp message to the number. The answer arrives in a few seconds; you’ll see it under Recent messages here and in Conversations.

WhatsApp allows free-form replies only within 24 hours of the customer’s last message; the assistant always answers right away, so that’s met. It doesn’t start conversations (that needs approved templates).
Only text messages are read; for photos, voice notes and the like the customer is asked to type their question.

Slack (a Slack app)

Your team asks the assistant in Slack: mention it in a channel, or message it directly.

You need: Permission to create and install apps in your Slack workspace.

Open api.slack.com/apps → Create New App → From scratch, name it and pick your workspace.
OAuth & Permissions → Bot Token Scopes: add app_mentions:read, chat:write, im:history and im:read.
Install to Workspace, then copy the Bot User OAuth Token (it starts with xoxb-).
Basic Information → App Credentials: copy the Signing Secret.
Here, add the Slack channel with the token and the signing secret. Save to get the Request URL.
Event Subscriptions → Enable Events → Request URL the webhook URL from the dashboard (Slack checks it at once). Under “Subscribe to bot events” add app_mention and message.im, then Save Changes (reinstall the app if Slack asks).
App Home → Show Tabs: turn on the Messages tab and “Allow users to send Slash commands and messages from the messages tab”.
In Slack, invite the bot to a channel (/invite @your-bot) and mention it, or send it a direct message.

In a channel it answers in the thread of the message that mentioned it; direct messages are one ongoing conversation.
Every request from Slack is checked against the signing secret and must be less than five minutes old.

Microsoft Teams (an Azure Bot)

Your team chats with the assistant in Teams, or mentions it in a channel.

You need: An Azure subscription (the Azure Bot resource is free on the standard channels) and permission to add apps in Teams.

In the Azure portal, Create a resource → Azure Bot. Choose Single Tenant (your organization only) and “Create new Microsoft App ID”.
Open the bot → Configuration: copy the Microsoft App ID and, for a single-tenant bot, the App Tenant ID.
Next to the App ID, open “Manage Password” → New client secret, and copy its value.
Here, add the Teams channel with the App ID, the tenant ID (single tenant) and the secret. Saving checks them with Microsoft and shows the messaging endpoint.
Back in the bot → Configuration → Messaging endpoint: the webhook URL from the dashboard. Apply.
Bot → Channels → Microsoft Teams → accept the terms → Apply.
In Teams, open Developer Portal → Apps → New app → App features → Bot: choose “Enter a bot ID” with your App ID, scopes Personal and Team. Publish it to your organization (or upload it as a custom app).
Chat with the bot in Teams, or @mention it in a channel where it’s added.

Every message is checked against the Bot Framework’s signing keys, and replies only go to the Teams service address Microsoft vouched for.
With a tenant ID set, messages from other Microsoft 365 organizations are ignored.