xAI's Team Bots: One Grok Coworker Your Team Shares

xAI opened public beta on September 28 for Team Bots: one Grok coworker your team builds around a role, shared so everyone works from the same files, connected apps and memory. Each person still gets a private conversation with it, but nobody starts from a different answer than the person next to them.

What shipped

The announcement, dated September 28, 2026, describes Team Bots as built from four parts: context (files, instructions, brand guides, documentation), plugins that connect to outside tools, credentials for secure access, and memories that carry learning forward instead of resetting each session. It is a public beta on Teams and Enterprise plans, so a solo free-tier user cannot turn one on yet.

Harper, an insurance company, is quoted saying it built a Team Bot in 24 hours to check customer policies across three platforms, and that it saved customers over $120,000 out of hundreds of policies. Inside xAI, a five-person engineering team used a Team Bot to ship more than 100 pull requests a day, and its own analytics team runs a Data Bot fielding dozens of requests daily against a library of more than 45,000 tables, remembering corrections so one person's fix improves the answer for everyone.

Why an owner should care

Every example here is one team working from one shared source of truth, instead of each person keeping a different version of the answer in their head. Any business with more than one person answering customers, scheduling jobs or quoting prices already has this problem: the answer depends on who picks up the phone. A shared bot fed the same documents and pricing everyone is supposed to use removes that variance without a trainer or a manual nobody reads. The catch: it needs a paid plan, it is still a beta, and Harper's number belongs to Harper, not any other business.

What it looks like inside a shop

Picture an AV or trades business with three people fielding calls: a scheduler, a salesperson, and whoever answers when both are out. Each carries a slightly different version of pricing, install timelines and warranty terms. A Team Bot on the Customer Bot template, fed the real price list, past proposals and warranty policy, gives all three the same starting answer when a customer asks how much or how long, while each person's own conversation with it stays private.

The same idea works past the front office. A shop running its own service tickets or purchase orders could build a Data Bot equivalent, so the same question gets the same answer on Monday or Friday, from the owner or a new hire.

What to do this week

• List the questions your team answers differently depending on who picks up: pricing, scheduling and warranty terms are the usual suspects.
• If you already run Grok on a Teams or Enterprise plan, check what a Customer Bot template needs loaded to answer those questions consistently.
• Write down where the real answer lives today: a price sheet, a shared doc, a person's memory. That is what any shared bot has to be built from.
• Treat Harper's $120,000 figure as one case study, not a benchmark for your shop.