Teams, Slack and WhatsApp
Any agent, console-made or code, can answer people in Microsoft Teams, Slack or WhatsApp. You connect a channel to the agent, paste the webhook address it gives you into the vendor's settings, and from then on every message is answered by the agent's live version.
Channels are the one feature that needs the internet: Teams, Slack and Meta accept replies only on their own clouds, and their servers must reach your install's webhook address. Your operator lists the vendor hosts Orchestrate may call in channels.outboundHosts. With the list empty, the default and the air-gapped setting, no channel can be connected and nothing is sent. See Configuration.
Before you start
- The licence includes channels. A licence can also cap the number of channels and the messages accepted per month. See Licence.
- Your operator has allowed the vendor's hosts and made the API reachable from the internet at the webhook address.
- A vendor app. An Azure Bot for Teams, a Slack app, or a Meta WhatsApp Business app, which you create in the vendor's own console.
- The admin role on the agent's project.
Connect a channel
- Open the agent and go to Channels (a section on a console-made agent, a tab on a code agent).
- Choose the vendor, give the channel a name, and fill in the settings and secrets the form asks for.
- Save. The section shows the channel's webhook address,
https://<your API host>/channels/<channel id>/events. - Paste the address into the vendor's settings, as below.
- Choose Test to check the credentials against the vendor.
Secrets go to Vault. The console only ever shows which secrets are set, never their values.
Microsoft Teams
| Setting | What to enter |
|---|---|
| Microsoft App ID | Your Azure Bot's app (client) id. |
| App tenant id | Only for a single-tenant bot: its Entra tenant. |
| Allowed tenants | Optional. The Entra tenants whose users may use the bot. |
| App password (secret) | A client secret of the bot's app registration. |
In Azure, set the bot's messaging endpoint to the webhook address, add the Teams channel, and install the bot in Teams with an app manifest.
Hosts to allow: login.botframework.com, login.microsoftonline.com, smba.trafficmanager.net, and *.sharepoint.com to read attached files. A government-cloud tenant uses other service addresses: add those.
Slack
Create a Slack app with the bot scopes app_mentions:read, chat:write, im:history and files:read, and subscribe it to the events app_mention and message.im. Set the Events API request URL to the webhook address. For reactions as feedback, also add reactions:read and the events reaction_added and reaction_removed.
Secrets: the app's signing secret and its bot token. Optionally enter the workspace id, so events from any other workspace are ignored. Test fills in the bot's own user id, so it never answers itself.
The agent answers when it is mentioned in a channel, in that message's thread, and in direct messages. Plain channel messages are ignored.
Hosts to allow: slack.com, and files.slack.com for attachments.
WhatsApp
Use the Meta WhatsApp Cloud API. Enter the phone number id, and the secrets: the app secret, a system user's access token, and a verify token you choose. In Meta's webhook settings, use the webhook address as the callback URL and the same verify token.
WhatsApp allows free-form replies only within 24 hours of the user's last message. An answer that comes later, for example after a day-long approval, is sent as a template. Name an approved utility template with one body variable in the channel's settings. Without one, a late answer fails with a clear error on the channel.
Hosts to allow: graph.facebook.com, and lookaside.fbsbx.com for media.
What end users see
| Situation | Message |
|---|---|
| The run finished | The agent's answer, with "Sources: ..." when it cited documents. |
| A tool call needs approval | Once: the agent needs a person to approve an action, and will reply in the conversation. The answer follows when someone decides, minutes or days later. |
| The approval was rejected, or the run failed | A fixed sentence. Never the error text. |
| The previous message is still being answered | The agent is still working on it. |
| Over the rate limit | The person is sending messages faster than the agent can answer. Sent at most once a minute. |
| The agent has no live version | The agent isn't available right now. |
Each vendor conversation is one thread: a Teams conversation, a Slack thread or DM, or a WhatsApp number. Text attachments (txt, md, csv, json, xml, yaml, html and log files, up to 256 KB) are read as text. Other attachments are noted but not read.
Approvers decide in the console, not in the chat. See Human approval.
Who the message runs as
The run is started as the end user: its Started by reads, for example, Sam (WhatsApp).
A Teams user whose Entra object id matches exactly one Orchestrate account that signs in through your identity provider runs as that account. A connector that acts as each user then uses that person's own connection. The message still grants nothing beyond running this agent: the account's console roles are not used. To match, set Directory object id claim on the identity provider. See Identity and single sign-on.
Slack and WhatsApp users aren't matched to accounts, because those vendors give no directory identity.
Feedback
A message that starts with a thumb (👍 or 👎, Slack's :+1: or :-1:, Teams' (y) or (n), or +1 or -1), optionally followed by a comment, rates the conversation's last answer instead of going to the agent. A native reaction on one of the agent's answers rates that answer. Removing the reaction takes the rating back. See Online evals and feedback.
Limits
Each channel has two limits, set on the channel:
- Messages per user per minute, default 6. This is counted per API replica.
- Runs per hour for the whole channel, default 300.
The Channels section shows this month's inbound messages, answers, replies sent and failures per channel. With metrics on, Orchestrate also exports vois_channel_messages_total.
Not available yet
- Approving from a Teams or Slack card. Approvers use the console.
- Token streaming and typing indicators. Each run posts one answer.
- WhatsApp delivery statuses after Meta accepts a message.
- Teams Emulator tokens and government clouds' sign-in endpoints.