01What a Grok Team Bot Is and How It Works

A grok team bot is a Grok Bot that your whole team shares, new in Grok Bot 1.0. You share it the way you would share a doc, and everyone works from the same bot.

Each person's chat with the bot stays private. The bot keeps a separate memory for every person, and it draws on the skills the whole team shares. So your chats stay yours, while the skills get better for everyone.

Before this, if a teammate wanted the same help, they had to build their own bot and teach it everything again. Now you build one bot around a role. You give it the files, apps and skills that role needs, and the whole team uses it.

xAI runs its own work this way. Every big sales account gets its own team bot. Each morning, the bot posts a briefing in that account's Slack channel with what changed and what each person should do next.

In this episode, Julian Goldie shows how this works by building a five-floor tower of bots, one for each job.

02What's New in Grok Bot 1.0

Grok Bot 1.0 brings a set of team features. Here is what a bot can now do:

  • Be shared: a bot can be a team bot that everyone works from.
  • Keep chats private: each person's chat stays their own, with separate memory per person.
  • Join Slack: you can invite it into a Slack channel, where it has its own handle. Everyone can ask it questions and see what it says.
  • Join meetings: it joins Zoom, Google Meet and Teams calls, takes notes, and sends you a summary and action items.
  • Learn safely: anything it learns for the team waits for the owner to approve it first.

Picture that in your business. An agency gets one bot per client account. A coach gets one bot per program.

A course owner gets one bot for the community.

Everyone asks the same bot, and nobody starts from zero. That is the main shift in this release: one well-built bot can now serve a whole team instead of just one person.

03How to Build and Share Your First Grok Team Bot

To show the idea, Julian pressed Plus in Grok Bot, chose to create a bot, and called it Team Tower. Then he gave it one prompt: build a glass tower with five floors and one robot teammate on each, with a screen showing its job.

About 25 minutes later, Grok Bot dropped a page into the chat. The camera cranes up all five floors, every robot has a name tag and its own screen, and a tube up the side carries messages between floors.

The basic steps to share a bot from this episode are:

  1. Press Plus and create a bot, then give it a name.
  2. Tell it in one clear brief what its job is.
  3. Add the files, apps and skills that role needs.
  4. Press publish when the bot says it is ready.
  5. Press share and choose your team, or only the people you invite.

Grok Bot also told Julian it tested the scene in a browser before sharing it and got no errors. It checked its own work, explained what it changed and asked him to say if anything looked off.

04Floors 1 and 2: The Meeting Bot and the Roundup Bot

Every floor came from what members of the AI Profit Boardroom asked that week.

Floor one is the meeting bot. A member said their meeting recorder never made it to the call. Here is how it works:

  1. Paste the Zoom, Meet or Teams link into your chat with the bot.
  2. Ask it to join and take notes.
  3. Approve the card it shows you.
  4. The host lets it in.
  5. When the call ends, the summary and action items land in your chat.

The brief Julian would paste tells the bot to join the call, take notes, and send a short summary and a list of action items with owners. For coaches and consultants, that is your follow-up written before you close the laptop.

Floor two is the roundup bot. A member runs five brands from one workspace and writes a daily roundup across all their chats. Create a bot and tell it in one sentence to read each brand's chats and write one roundup. Then open the bot's details and tap Create a routine.

Add it to Slack, and the roundup is waiting for the whole team every morning.

05Floors 3 to 5: Client System, Audit and Community Bots

Floor three is the client system bot. An agency owner wanted leads, follow-ups and bookings in one place. Build it as a team bot and share it. Collaborators can chat with it, managers can change how it works, and nobody can read anyone else's chats.

Its brief: track every lead from new lead to follow-up to booked, draft a first reply, suggest the next follow-up date, and keep a one-screen pipeline summary.

When a teammate shows it a better way to follow up, it suggests the change. You approve it under review learnings.

Floor four is the audit bot. Give the bot your audit checklist as a skill:

  • A process map.
  • Tools in use.
  • Three to five quick wins.
  • A 30, 60, 90-day road map.

After each session, drop in your notes and it fills in the report. Your second audit is faster than your first, because the bot kept what it learned.

Floor five is the community bot. One community owner has 55,000 members posting 300 times a day. The bot reads new posts each morning and posts a short list of the 10 most promising people, with a one-line reason and a suggested reply. It drafts, and you decide who to answer.

06Which Grok Team Bot to Build First

Which floor you hire first depends on your business. Julian's picks are:

  • Agencies: start with the roundup bot. It saves the most time across lots of clients.
  • Coaches and consultants: start with the meeting bot. Every call turns into a follow-up.
  • Course and community owners: start with the community bot. It finds the people who are ready to join.
  • AI automation builders: start with the client system bot, then build one for each client.
  • People who run audits: the audit bot makes every audit after the first one faster.

Another member asked how to organise Claude, ChatGPT, Hermes and Gemini all at once. The tower is the answer to that too. Give each job its own bot and keep them all in one place.

The idea is the same for every business. Start with the one job that eats the most of your time, give it a bot with a clear brief, and add the next floor once that one is working.

07Five Grok Team Bot Mistakes to Avoid

Before you share your first team bot, Julian lists five mistakes to avoid:

  1. Adding keys and files without thinking. Anything you add works in every teammate's chat, so only add what you are happy for everyone to use.
  2. Forgetting to publish. Until you press publish, the bot is a draft that only you can see.
  3. Ignoring review learnings. When teammates teach the bot something, it waits for you. Check it once a week.
  4. Building one giant bot for everything. Give each job its own bot, like the floors of the tower. Small bots with one role are easier to trust.
  5. Letting everyone share bots when you want control. Admins can set bot sharing to admins only, from the team dashboard.

Get those five right and your team bots stay useful and safe.

One honest note from the episode: on Julian's account, Slack showed as not connected, and the shared list said no shared bots yet, because he had not published this one. A few sample labels on the tower page were also swapped to agency and coaching examples for the video.

08Who the Grok Team Bot Is For and Why It Matters

A Grok team bot is for anyone who works with other people and keeps teaching the same things over and over. That includes:

  • Agencies with many client accounts.
  • Coaches with several programs.
  • Course owners running a community.
  • Consultants who run audits and calls.

The big change is that one bot can now learn from the whole team without anyone's private chat leaking. Skills get better for everyone, but each person's chat stays theirs, and the owner approves what the bot learns.

Putting the bot in Slack means the team can see its answers in one shared place. Sending it to meetings means notes and action items arrive without anyone writing them.

In short, Grok Bot 1.0 lets you share one bot with your whole team, put it in Slack, send it to your meetings and let it learn from everyone. Start with one small bot for one job, publish it, share it, and build the next floor from there.