v2.6.46Latest

Microsoft Teams bots that join as guests now receive the meeting chat and forward it as bot.chat_message, and signed-in Teams bots can post their entry message and API chat messages again. Integrators who rely on chat from Teams meetings, who leave bots that were retried after a failed join, or who want custom data retention windows for their team should read on. Google Meet and Zoom bots are unchanged.

✨New Features

• Custom data retention windows for teams with stricter data-minimisation requirements. On top of the plan's data retention, a team can be given its own, shorter windows for webhook payloads, participant names and bot metadata, and data past a window is deleted automatically. Ask support to configure one for your team.
• The dashboard's bot details show whether a Teams bot joined signed in or as a guest, the same teams_login information GET /v2/bots/{bot_id} returns. See authenticated Teams bots.
• Self-hosted deployments can run the pre-release bot channel by adding a beta bot pool and its queue URL. Admins can then route a share of bots to it, and the bots page shows and filters the build each bot ran. Installs without a beta queue are unchanged. See the self-hosting configuration.

⚡Improvements

• Teams bots post their entry message about 3.5 seconds after entering the call, roughly a second sooner than before.
• The bot.chat_status event for Teams bots now reflects whether the meeting chat actually works for the bot, not whether its chat panel opened, and is sent as soon as that is known instead of up to 25 seconds later. A chat the organizer restricted is reported as organizer_disabled. See webhooks.

🐛Bug Fixes

• Teams bots that joined as guests received almost no chat messages, so bot.chat_message rarely fired for Teams meetings. Messages written by participants are now forwarded within about a second of being sent, including when the chat loads slowly.
• Signed-in Teams bots failed to post their entry message and POST /v2/bots/{bot_id}/send-chat-message did not deliver, even though the bot was in the meeting. Both now work.
• POST /v2/bots/{bot_id}/leave returned 200 but the bot stayed in the meeting when that bot had been retried after a failed join. The leave now reaches the bot.

↩ All releases