xAI Opens Team Bots Public Beta for Shared AI Coworkers

xAI's Team Bots enter public beta today for Teams and Enterprise plans, letting groups share AI coworkers that keep separate memories and private chats per member.

Sep 28, 2026
•
5 min read
Technobezz
xAI Opens Team Bots Public Beta for Shared AI Coworkers

Don't Miss the Good Stuff

Get tech news that matters delivered weekly. Join 50,000+ readers.

xAI has opened a public beta of Team Bots, a version of its Grok Bots built for shared team work, and it is available today. The beta is limited to Teams and Enterprise plans, according to the announcement. Team Bots are meant to sit inside a group rather than beside one person: a Bot is organized around a shared role or workflow, and every member works with the same Bot and the same accumulated expertise, while still holding their own individual conversations with it.

Each Team Bot has its own Slack handle and can be invited into channels to answer group questions. Under the hood xAI lists four parts: Context, which carries files, instructions, and skills; Plugins, which connect to tools such as Salesforce, Notion, and GitHub and can be attached per person or for the whole team; Credentials, for reaching third-party APIs that have no plugin; and Memories, which hold what the Bot learns so it performs better in its role over time. Conversations stay private to each user, and the Bot keeps separate context and memories per person even as it draws on skills the team shares.

xAI is also shipping pre-built Team Bots for sales, product management, marketing, and data analytics, and existing Grok Bots can be shared with a team. The company did not disclose pricing for Team Bots, and beyond the public beta it gave no general availability date.

The sales example shows how the pieces fit together. SpaceXAI gives each major sales account its own Team Bot, with one Bot serving the account executive, customer success manager, solutions architect, and sales leader on that account. That Bot reviews news, Gong calls, Notion docs, and Slack threads overnight, then posts a weekday morning briefing in Slack covering what changed and what to do next, along with role-specific next steps. It remembers decisions and builds context over time, and during staff rotations it becomes the system of record.

Other teams get narrower jobs. An engineering Bot lives in a project Slack channel, follows decisions, triages bugs, files tickets, and can launch Cloud Agents for well-defined fixes, with the shipping process taught through skills covering PR reviews, escalation, and evidence. One Bot steered a Cursor Project that orchestrated hundreds of Cloud Agents, and a five-person team shipped more than 100 PRs daily. A marketing Bot checks Slack drafts against brand guidelines, blog posts, and social copy, gives regional teams feedback without an HQ approval cycle, and pushes approved website and SEO changes to preview so the team ships without tickets or engineering.

A data Bot answers one-off analyses without an analyst or warehouse access, using shared read-only credentials on approved Databricks tables and connections to Datadog, Hex, and Statsig. The data analytics team spent two years building a skills library covering more than 45,000 tables, and the Bot remembers query corrections so everyone's answers improve.

Harper, an insurance company, built a Team Bot for lapsed policies that helps reinstate coverage and cuts manual work. Its CEO, Dakotah Rice, said the company had been checking every customer by hand across three platforms, pulling balance details, and sending personalized emails, and that the Bot was built in 24 hours and has saved customers over $120,000 from hundreds of policies. xAI says Team Bots themselves were launched in a few weeks.

Share