xAI brings Grok Bot into video meetings to take notes and answer in chat

xAI’s Grok Bot can join video meetings as a note-taker and answer questions in chat, part of the Grok Bot 1.0 release announced November 2, 2026. The feature brings the assistant into live team discussions, with separate controls for admitting it, letting it respond, and stopping its access to meetings.

A meeting link starts the handoff

According to xAI’s meeting documentation, Grok Bot supports Google Meet, Zoom, and Microsoft Teams calls. Users paste a meeting link into their chat with the Bot, ask it to join and take notes, then approve the card it presents. The meeting host must admit it when the call starts.

A Bot that follows a user’s calendar can also join scheduled meetings automatically. In the participant list, its displayed name identifies it as either the user’s Bot or a Team Bot and includes a transcribing label. That makes its role visible inside the call rather than leaving note-taking entirely in a separate chat.

Users can check the Bot’s details to see meetings it is scheduled to join or already attending. The Upcoming area shows a countdown, the next scheduled join time, or a Taking notes status during a call. Meetings are available on Team, Enterprise, and Ultra plans; Enterprise administrators can enable the feature in settings.

Replies stay in the meeting chat

Participants address the Bot by name in the meeting chat, and it answers there. xAI’s launch announcement says Bots can bring information from earlier conversations into video-call discussions. The described participation is through text chat, alongside listening and note-taking, rather than a voice conversation with the Bot.

Some exchanges have a narrower audience. On Zoom, a private chat message to the Bot gets a private answer. A request from a conference-room device, however, counts as coming from the room rather than an individual. That distinction affects who the Bot treats as making the request.

xAI also describes a check on information sharing: if a participant requests something the Bot has held back, it tells the user who asked and offers to send it. The documentation says the Bot will not share the user’s credentials in a meeting. Those are product commitments, not independently tested security results.

Stopping replies is not stopping access

The meeting menu separates three actions that might otherwise sound interchangeable:

• Disable Interactivity keeps note-taking active but stops answers. Users can reverse this while the meeting remains scheduled; once the Bot is joining or attending, they must quit and add it again.
• Cancel removes a scheduled meeting from the Bot’s queue.
• Quit removes the Bot from a meeting it is joining or attending.

Enterprise administrators have a broader switch under Bot Capabilities in the team dashboard. Turning Meetings off prevents Bots from joining or reading meetings. A Bot previously scheduled to attend then tells its user that meetings are no longer available. Meetings otherwise use the settings of the person who started them.

After a call ends, the Bot sends a summary and action items in its chat. Users with Pages also get a longer report on a page, linked from that conversation. They can later ask the Bot for a past meeting’s summary or transcript, extending the workflow beyond the live discussion.