Matt Palmer: "Grok Bot 1.0 - What's new in Grok Bot". Facts on this page cite the primary sources below, not the video.

The claim: Grok Bot is now a teammate. It sits in your meetings, works for your whole team and starts work before anyone asks.

The proof: On Wednesday, Nov. 11, 2026, at 1:22 PM ET, the official @bot account announced Grok Bot 1.0, the first release out of beta. The changelog for v1.0.1, dated the same day, is specific: a Bot can join a Google Meet, Zoom or Microsoft Teams call from a link, answer in the meeting chat, and send a summary afterward. One Bot can now be shared with a person, a group or a whole company. Those parts are in the release notes. "Takes initiative" and "hours saved" are SpaceX SI's own descriptions.

Editorial Thesis

For three months Grok Bot was mostly a personal assistant: your Bot, your logins, your chats. Version 1.0 changes who it works for. A Bot that sits in a meeting and answers for a team is a coworker-shaped product, and that is a bigger change than any single feature. But "coworker" is the marketing word. What actually shipped is narrower and easier to check: a Bot can join a call and type in the chat, a Bot can be shared in place, and what teammates teach it waits for an owner to approve.

Honest Verdict

  • Confirmed (@bot and @SpaceXSI on X, Nov. 11): Grok Bot 1.0 launched on Wednesday, Nov. 11. Elon Musk reposted SpaceX SI's announcement that evening.
  • Confirmed (changelog v1.0.1, Nov. 11): Bots join Google Meet, Zoom or Microsoft Teams calls from a link, answer in the meeting chat and send a summary afterward, on Team, Enterprise and Ultra plans. Team Bots can join Microsoft Teams after admin approval. What teammates teach a Team Bot waits under Review learnings until the owner or a Manager approves it.
  • Confirmed (SpaceX SI's 1.0 page): Team Bots are on Team and Enterprise plans; Meetings on Team, Enterprise and Ultra; Enterprise admins must switch Meetings on.
  • Shown, not measured (Matt Palmer's walkthrough, Nov. 15): an Analytics tab that shows how many hours a Team Bot has saved and how many messages it got. That is the product's own count, not an outside audit.
  • Company description: Bots "recognize work that needs to be done and offer to take it on." In Palmer's demo that starts from a routine you set up, like a 7 AM check-in.
  • Not known: how many teams use Team Bots, how "hours saved" is calculated, and whether meeting time eats into a plan's weekly usage.

What changed in 1.0

Meetings. Tell your Bot "join my meeting at 11 AM" and it joins the Google Meet, Zoom or Microsoft Teams call. According to the changelog, it answers in the meeting chat and sends a summary afterward. Palmer's demo shows it pulling answers from connected apps such as Slack and Notion during the call. Its icon shows up in the meeting, and it can be an animated GIF.

Team Bots, in place. Team Bots have been in public beta since Sept. 28 (we covered that on Oct. 6). The 1.0 change is that any Bot becomes a Team Bot with a switch, instead of a copy, and can be shared with one person, a group or the whole organization. Team admins can now limit who shares Bots.

Learning, with a gate. A Team Bot picks up how teammates work. Under 1.0, those lessons sit in Review learnings until the owner or a Manager approves, rejects or edits them. That gate matters: a shared Bot that learns from everyone could also learn the wrong thing from anyone.

Initiative. SpaceX SI says Bots "take initiative." Palmer's example is concrete: a 7 AM routine where the Bot looks through Slack and connected apps for a launch's status and suggests work it can start. That is a scheduled check you set up, not a Bot deciding on its own what your job is.

Analytics. Team Bots get an Analytics tab with messages received and hours saved. Useful for deciding whether a shared Bot is worth keeping, as long as you remember the Bot is grading its own homework.

What this does not prove

  • It does not prove Bots save teams time. The hours-saved figure is the product's own estimate.
  • It does not mean every plan gets meetings. Team, Enterprise and Ultra only, and Enterprise admins must switch it on.
  • It does not make the Bot a voice in the room. The release notes say it answers in the meeting chat.
  • It does not settle the usage question. Weekly limits were reset on Nov. 9 after complaints, and SpaceX SI hasn't said how a long meeting counts.

What to watch next

  1. Whether SpaceX SI publishes how "hours saved" is calculated.
  2. How meeting time counts against weekly usage on each plan.
  3. The next changelog after v1.0.1 (still the latest when we checked).
  4. Any customer numbers for Team Bots from SpaceX SI or an outside source.

Bottom Line

Grok Bot 1.0, out of beta since Nov. 11, can join your Zoom, Meet or Teams call, answer in the chat, send a summary, and work for a whole team from one shared Bot. That is real and documented. "Takes initiative" and "hours saved" are SpaceX SI's words and SpaceX SI's count, so test them on your own team before you believe them.

Source notes

Launch date and wording from @bot and @SpaceXSI on X (Nov. 11, read Nov. 17). Feature details from the Grok Bot changelog v1.0.1 and SpaceX SI's "Introducing Grok Bot 1.0" page (the page's date field says Nov. 2; we use the Nov. 11 date from the X posts and changelog). Demo details from Matt Palmer's walkthrough video (Nov. 15) and TeslaNorth's recap (Nov. 16). Video: Matt Palmer, who works on Grok Bot at SpaceX SI; alternate: Nate S. Hartman (Nov. 12).

Sources