xAI opened a public beta of Team Bots, a version of its Grok chatbot that a whole team shares instead of each person running a separate copy. One Bot can hold the files, logins, and app connections a group needs, and it keeps a running memory of decisions the team has made, according to the company’s own announcement.
That shared memory is the actual pitch. Most workplace chatbots reset with every new conversation or belong to one person’s account. xAI is selling continuity: a Bot that remembers what a sales team decided about an account last month, or which bug fixes an engineering group already tried, so a new hire or a rotating account manager does not start from zero.
Each Bot draws on four ingredients, per xAI: context documents such as brand guides, plugins into apps like Salesforce, Notion, and GitHub, credentials for APIs that lack a plugin, and the accumulating memory itself. Teams can also talk to a Bot inside a shared Slack channel, where it has its own handle and everyone can see the same thread. Individual conversations, xAI says, stay private even when the Bot itself is shared.
xAI’s write-up leans heavily on its own usage, which it says happens inside “SpaceXAI,” an internal unit it does not otherwise describe. The company says an engineering Bot there triaged bug reports and dispatched fixes to autonomous coding agents, and that a five-person team used the setup to ship more than 100 pull requests a day while building Team Bots itself. Those are xAI’s own figures from its own product launch post, not an independent benchmark.
The company also supplied two customer quotes. Dakotah Rice, chief executive of the insurance company Harper, said his team built a Bot in 24 hours that found customers with lapsed policies and recovered “over $120,000” for them. Angela Ferrante, head of marketing at Amplitude, said her team wants a Bot for “every marketing function.” Both are testimonials xAI chose to publish, and neither figure carries outside verification.
Team Bots puts xAI in the same lane as Microsoft’s Copilot Studio and Salesforce’s Agentforce, both of which already sell persistent, tool-connected assistants that a team shares rather than a single employee. The distinguishing claim here is memory that compounds across a group over time rather than resetting per user, which is harder to fake in a demo and harder to verify from outside. xAI has not published adoption numbers, pricing tiers beyond “Teams and Enterprise plans,” or any detail on how a Bot’s memory is walled off if an employee with access leaves the team.
For any operator already paying for a team based AI assistant, the open question is whether shared memory actually reduces the ramp time for new hires and rotating staff, or whether it just centralizes more sensitive context in a system with no published access controls beyond “credentials.” Run a small pilot with one account team before extending it company wide, and check what happens to a Bot’s memory when the person who built it leaves.
Reported by xAI in its own company blog post announcing Team Bots; the post did not carry a publication date.
