01What Grok Bot Teams Is and How Shared Bots Work
Grok Bot Teams is the new shared bots feature in Grok Bot, where you build one bot for one job and your whole team uses it. Before this, ten people on a team meant ten different Grok Bots doing the same job ten different ways.
A shared bot takes a role that already exists on your team, such as the person who writes proposals, and turns it into one Grok Bot. The people who know that job best build it and keep it up to date. Everyone else just chats with it.
Here is what makes shared bots useful:
- Each person gets their own private chat with the same bot, so nobody sees anyone else's conversations.
- When someone finds a better way to do the job, they update the bot once and everyone gets the new version.
- Nobody has to change their own setup.
The sales team at the company that makes Grok already runs its deals this way. One Grok Bot preps every sales call and updates Salesforce afterwards. One writes the quotes.
One reviews unusual deals. And the bots hand work to each other, so the job moves along without someone copying it from tool to tool.
02How the Grok Team Set Up Its Shared Bots
The way the Grok sales team set up its bots is the real lesson. They did not guess what to automate. They started with real data.
- They had Grok Bot read their Salesforce activity logs to find which work was worth automating.
- The answer was clear: reps were losing hours updating deals after customer calls.
- So that was the first job they automated.
- Each shared bot then got shared skills and connections to the company's sources of truth.
- Bots were set to hand work to each other when a job moved to a new stage.
Because every bot connects to the same sources, every rep works from the same up-to-date rules. Nobody is using an old price list or last year's notes.
The hand-off part matters too. When the quote bot hits something unusual, it passes the work straight to the deal bot. That keeps each bot focused on one job it does well, instead of one giant bot trying to do everything.
For your own team, this gives you a simple plan: look at where people lose the most time, and automate that job first.
03Safety Rules Built Into Grok Bot Teams
Shared bots act on real company systems, so Grok Bot Teams comes with several layers of safety. These are worth understanding before you hand a bot to your whole team.
- Each person's permissions: the bot acts with the permissions of whoever is asking it, not one shared super account.
- Limits on sensitive actions: there are extra limits on actions that carry more risk.
- Limits on bulk changes: the bot can only make so many changes at once.
- Specialist-only actions: some actions can only be done by a specialist bot. For example, a rep cannot use the quote bot to approve their own exceptions.
- Human review: a person must review whenever the rules for a decision are not clear, and whenever the bot writes something a customer will see.
Secrets are also handled carefully. They are encrypted, and even Grok Bot itself cannot see the values.
These rules mean you can let a whole team use a bot without worrying that one person could push a bad deal through or that customer-facing text goes out unchecked. The bot does the busy work, and people still make the calls that need judgment.
04How to Build a Team Bot in Grok Bot Teams
Building a shared bot happens inside the Grok Bot app. The setup walks you through each part, so you do not need to be technical.
- Open the Grok Bot app and click New chat.
- Choose Create new team bot.
- Tell it what the team needs the bot for.
- Work through the four cards: plugins, secrets, skills and files.
- Connect a Slack app if you want, so your team can mention the bot in a thread.
Already have a bot that works for you? You can share it instead of starting again:
- Open the bot's share menu.
- Choose Publish to team.
- Pick which memories, skills and files go across.
Anything personal stays private. Only what you pick gets shared.
There are two kinds of memory to know about. Team memory is read by everyone's chat, so useful facts spread to the whole team. Each person also has private notes that stay with them. Every shared bot can get its own Slack app, which makes it easy to use the bot right where your team already talks.
05Shared Bots 1 and 2: Call Prep and Proposal Bot
Julian Goldie builds his own version of five shared bots for a normal business, each owning one job. The first is the call prep bot.
Before a call, it reads the client's history and gives you a one-page briefing: who they are, what they have asked for, open questions and what to bring up. After the call, it reads the transcript, updates the deal in your CRM following your rules and drafts a follow-up email in your voice for you to check. You can also put it on a schedule so briefings are waiting every morning.
- Connect: your CRM (each person signs in with their own account), your call recorder, Gmail, calendar and files.
- In the build prompt, ask it to show a preview before changing anything and to never send the email itself.
The second is the proposal bot. Once a call goes well, it takes over. Ask for three options, such as basic, standard and full service, and it shows them side by side in the chat.
Pick one, and it builds the proposal and order form from your template with two matching case studies, saved as Google Docs.
- Connect: Google Docs, Drive and your CRM.
- Files: your proposal template, services list and case studies.
- If anything falls outside your normal terms, it hands the work to the deal desk bot.
06Shared Bots 3 and 4: Deal Desk and Competitor Watch
The third shared bot is the deal desk. It handles the unusual deals the proposal bot passes along, the same way the Grok team does inside Salesforce.
It watches a deal request Slack channel. For each request, it checks every term against your rules and past contracts, tells you whether you have agreed similar terms before and recommends the right approver.
- Connect: Slack, your CRM and your contract folder.
- Files: your rules, what counts as standard, what needs sign-off and who signs off.
- It never approves anything itself. After a person decides, it logs the decision, the reason and who approved it on the deal.
The fourth is the competitor watch bot, which keeps your team ahead every week. It checks your competitors' websites, new offers and new reviews. Then it updates one shared page with what changed, what they are good at and how to answer when a client says a competitor does something you do not.
- Connect: web browsing and Google Docs.
- Files: a competitors file with names, sites and what you know so far.
- Ask it to only use facts it found, with a link for each.
Because it is one page for every rep, nobody works from last year's notes.
07Shared Bot 5: The Training Bot to Build First
The fifth shared bot is the training bot, and it is the one to build first. You upload your playbooks, SOPs, call scripts and FAQs. New starters can then ask anything, such as how to handle an objection or what to send a new client on day one.
Here is what the training bot does:
- Answers questions using only your uploaded files, quoting the file and section each time.
- Says when the answer is not in the files and tells people who to ask.
- Role-plays a sales call as a tough prospect and scores the person afterwards.
- Saves anything the whole team should know to team memory, so everyone gets the update.
It only needs Slack plugged in. For files, use your playbooks, scripts, SOPs, FAQs and examples of great sales calls.
Why start here instead of the sales bots? There are clear reasons:
- It only reads, so it cannot change anything.
- It needs no sign-ins and no secrets.
- Everyone can use it on day one.
- Every question your team asks shows where they get stuck, which tells you what to put in the sales bots next.
08Who Grok Bot Teams Is For and What to Do Next
Grok Bot Teams is for any business with more than one person doing the same kind of work. Sales teams, agencies and service businesses get the most out of it, because jobs like call prep, proposals and deal checks repeat every day.
The big win is consistency. One bot, kept up to date by the people who know the job best, means every person on the team works the same way with the same rules. Fix it once, and the whole team gets better at the same time.
Here is a simple order to follow:
- Build the training bot first so your team can use it on day one.
- Look at where your team actually loses the most time, the way the Grok team did with its Salesforce logs.
- Automate that job next. For many teams, that will be call prep.
- Add the proposal, deal desk and competitor watch bots once the first ones work.
You can build all five shared bots yourself one by one. Or you can use the setup guide inside Julian's AI Profit Boardroom, which includes the build prompts and files for all five, Grok Bot training, the agentic operating system and weekly coaching calls where you can bring your setup and ask questions live.
