Sage now joins your Microsoft Teams calls

What changed

Until today, Sage joined Google Meet calls only. As of this release, Sage also joins Microsoft Teams meetings. Everything else stays the same: same post-meeting document, same 60-second delivery, same decision-tracking and action-item extraction with owners, same billing, same Sage you already know.

What you need to do

Nothing. Really. If you already have Sage on Google Meet, you're already on Teams too.

We kept the onboarding surface identical. The mental model is still: you connect your Google Calendar, Sage reads what's scheduled, and joins the calls. The only thing that changed under the hood is that Sage can now recognise Teams meeting links in your calendar events and join them as a guest, same as she joins Meet calls.

On your dashboard, Teams meetings appear in the same list as Meet meetings, with a small "Microsoft Teams" badge next to them so you can tell at a glance. Inviting Sage is the same click. The post-meeting document looks the same. The recap email looks the same.

If you paste a Teams meeting link into the "Join now" box on the dashboard (yes, that works now), Sage joins immediately — no lobby dance, no auth prompts on your side.

How it works (for the curious)

When a Teams meeting hits your calendar, we detect the link by pattern — teams.microsoft.com, teams.live.com, and the new teams.cloud.microsoft domain Microsoft is rolling out — and Sage joins via the Teams web client as a guest. She announces herself in the meeting chat the same way she does on Meet, listens to the conversation, and classifies what's being said into decisions, action items, and open questions.

Sage captures audio via the same real-time speech-to-text pipeline we use on Meet, so transcription quality, meeting documents, and recap emails are indistinguishable between the two platforms. If you're on the Team plan, the audio recording feature works exactly the same way too.

What's NOT in this release

Outlook Calendar as a meeting source. For now, Sage reads meetings from

your Google Calendar only. Most teams we talk to live in Google Calendar anyway — even if they run Teams calls — because it plays nicely with the rest of the Google ecosystem. If your team uses Outlook Calendar as your source of truth, let us know. We're planning a Microsoft Graph-based Outlook integration as a separate release and it'll move up the queue proportional to how many people ask.

Zoom. Zoom is still "coming soon". We went Teams first because the

technical work and user demand pointed that way. Zoom is on the list.

**Live meeting transcript in the dashboard while a Teams call is

running.** We have it for Meet; Teams parity is in the next iteration.

The boring details we're proud of

Seamless copy. We rewrote every place on the site that said "Google

Meet calls" to say "your meetings" or explicitly list both platforms. No UX treats Teams as a second-class citizen — the mental model is "Sage joins your meetings," full stop.

One click, both platforms. The "Invite Sage" button is the same

button whether the meeting is Meet or Teams. No mode switch. No checkbox. No "Teams Edition" upsell.

Same privacy, same consent. Sage's privacy policy applies equally to

Meet and Teams. She announces herself when joining a Teams call and sends a chat message identifying herself as an AI meeting assistant, same as on Meet. If anyone objects, the organiser can remove her.

Questions

Open a ticket at support@botzone.ai or hit reply on the welcome email if you're new. If something doesn't work the way you expected — a Teams link not being detected, Sage not joining, document looking different — we want to hear about it. This is a day-one release and we'll be watching for edge cases.