I've spent over 1,000 hours in Grok Bot. Here are the four levels I built for my team in 1.0, from a Slack ops bot to an assistant that joins my meetings, plus the templates to copy them.
The TLDR
Grok Bot 1.0 is the release that takes xAI's Grok Bot out of beta. You build a bot by describing its job in plain English, then connect it to your docs, Slack, calendar and email. This tutorial covers four levels: a Slack bot that answers ops questions from your own docs, sharing that bot with the whole company on each person's own logins, a bot that makes phone calls, and a personal assistant that joins your meetings, keeps your to-do list and triages your inbox. In JJ Englert's tests it refused to make sales calls and could not speak out loud in meetings.
I’ve spent over 1,000 hours inside Grok Bot, and most people still use it like a chatbot. That’s the wrong mental model. A chatbot answers you. A bot does a job, for you or for your whole team, with your docs, your tools and its own rules.
Grok Bot 1.0 is out of beta, so I built three bots on camera across four levels, each one a step up from the last. Here’s every step, what worked, what broke, and the templates so you can copy them.
Download my Grok Bot templates
The copy links for my Ops bot and my executive assistant, plus the exact prompts for all four levels. Subscribe to ultrathink, Tenex's free AI newsletter, to download them.
You're subscribed. Your templates are downloading.
If the download didn't start, download the templates (Markdown). The file has all four prompts. Swap the [brackets] for your own details before you paste.
Copy the bots straight into Grok Bot:
What is Grok Bot 1.0?
Grok Bot 1.0 is the release that takes xAI’s Grok Bot out of beta. It’s a tool for building bots that do a job instead of just answering a chat. You describe the job in plain English, feed the bot your docs, and connect it to tools like Slack, Notion, your calendar and your email. In 1.0 you can share a bot with your team, with roles, per-person logins and usage analytics. Bots can also join meetings and make phone calls.
Level 1: How do you build a Grok Bot for Slack that answers your team’s questions?
Start with one job and one source of truth. Ours was ops. Tenex is almost 90 people and one person leads ops. Brett has written great docs in Notion, but Notion is hard to search, the docs change all the time, and every “how do we do this?” question still lands on him.
So the first bot answers those questions in Slack, straight from his docs.
- Create the bot. In Grok Bot, open Create a bot in the top left. Give it a name and a color.
- Give it an identity. Tell it what it is and what its one job is. Mine: “You are our operations bot. You answer the FAQs for anyone with an ops question. I’m going to feed you our docs and our source of truth.”
- Feed it the docs. Share the Notion hub with it and ask it to read everything, answer the common questions and save it to memory. Tell it the personality you want. I asked for friendly, quick and helpful, without drowning us in text.
- Add it to Slack. Ask the bot itself, “How do we add you to our main Slack channel?” It shows a Connect card. Approve it, then add the bot to the channel.
- Test it with a real question. I asked, “@TenexOps, help me figure out how we book travel.” It found our travel policy and told me to pay with our company card or book through our travel tool.
That’s level one. The bot lives where the questions already get asked, and it answers from the same docs your ops lead would point to.
Level 2: How do you share a Grok Bot with your whole team?
Share it, set the roles, and let each person bring their own logins. While I was still filming, one of our engineers asked it to message him. It replied that it couldn’t, because it was only JJ’s bot. Sharing is what fixes that.
- Open Share in the top corner. Set everyone at your company as a Collaborator.
- Give your owner the keys. I made Brett an owner, so the person who owns ops can now change and manage the bot.
- Changes go through approval. If a collaborator wants to change a skill or a plugin, they request it and the owner approves. No GitHub, no pull requests.
- Logins stay personal. The bot was connected to my Notion and my Slack. Brett connects his own, and neither of us sees the other’s credentials. You can choose shared logins too, so pick on purpose.
- Check Permissions. It shows the bot’s channels, connectors, the shared vault, knowledge sources, skills and analytics on who uses it and how.
Teammates on a team or enterprise plan can also browse team bots and add the ones they don’t have yet, with a count of how many people already use each one.
This is the jump from single player to multiplayer. When I told Brett what I’d built, I offered to delete it. He told me to let it live. It’s our ops bot now.
Level 3: Can Grok Bot make phone calls for you?
Yes, Grok Bot can make phone calls out of the box. In my test, it refused to make a sales call.
My plan was to give it a skill for selling, have it research a phone carrier and a competitor, and then call my teammate Anthony to pitch him a new plan. I gave it rules: say you’re an AI at the start, admit it if asked, and hang up politely if someone says stop. It wrote the sales skill, said it was ready, and then refused to make the call. Sales pitches aren’t allowed, role-play included.
Honestly, that’s probably a good thing. So I changed the job. The bot became a gratitude helper: call Anthony and tell him what I appreciate about him. It tested on my number first, left a voicemail that opened with “I’m a virtual assistant calling for JJ Englert on a recorded line,” and then called Anthony.
The real use is anything a small team needs on the phone that isn’t a pitch: appointment reminders, support calls, FAQ calls. If you’re a 5 or 20 person business that needs help on the phones, that’s the bot to build.
Level 4 (God Mode): How do you set up Grok Bot as an AI assistant that joins your meetings?
Give it one long brief with every job it owns, then connect your calendar, email and a Notion database.
My brief gave it four jobs:
- Meetings. Join every meeting on my calendar unless I say not to. Take notes. Answer questions in the meeting chat. If I need help mid-meeting, DM me privately instead of posting to the room.
- To-dos. After each call, suggest to-dos and keep the list on a Page, the built-in artifact, split into what it can do for me and what I’ll do myself.
- Coaching. At the end of each day, read the meeting notes and coach me on how I did.
- Prep. Use my Notion meetings database to prep me, and message me 30 minutes before each meeting.
Then I shared the Notion meetings database, connected my work calendar and work email, and told it to write its meeting notes into the same database with a clear status for prep vs. notes. One source of truth for every meeting.
To test it, I started an instant meeting, pasted the link and told it to join. It joined as a guest and started taking notes. It couldn’t answer out loud, and at first it didn’t answer in chat either. I asked how to make it do that every time, and it made chat answers the default for every meeting.
Last, I added inbox triage: archive clear spam and newsletters I don’t need, flag what needs me, and never reply or delete without my permission.
When I checked back in, it had been busy. It had booked itself into 17 meetings for the week. It had started my to-do Page. It archived 61 of the 191 emails from the week before, and flagged the ones I should handle. It also found that it had made two copies of 11 meeting pages, merged them, and asked me before deleting the leftovers.
What’s our take on bots like this?
Most teams roll out AI as a chat window and wait for people to use it. That’s a license, not a rollout. The bots that stick have one job, one source of truth, and live where the work already happens: a Slack channel, a calendar, an inbox.
The trade-off we accept on purpose: a narrow bot does less. An ops bot won’t write your marketing plan. That’s the point. A bot with one job is easy to trust, easy to fix when it’s wrong, and easy for the person who owns that job to manage. You’d be right to push back if your docs are thin. A bot built on a messy wiki will hand out the mess faster.
How would we roll this out at your company?
The same four moves we use for any AI work. Embed with the team that owns the job and find the questions that keep landing on one person. Ship one bot against the docs that already exist. Train the owner to manage it: roles, approvals, logins, analytics. Then hand it off, so it’s their bot, not ours.
If you want help picking the first job and building the bot around it, that’s what our AI transformation work is for. For the security side of shared bots and logins, start with our guide to AI governance for safe employee use.
Where does Grok Bot 1.0 break?
- Your docs are the ceiling. If two docs disagree or the policy changed last month, the bot will say the old thing with confidence. Fix the docs first.
- Defaults are conservative. The meeting bot didn’t answer in chat until I told it to. Expect to train behavior, not just set it up.
- It makes messes, then cleans them. My assistant duplicated 11 meeting pages before it fixed them. It asked before deleting, which is the rule you want.
- No sales calls, no voice in meetings, in my tests. Plan around both for now.
- Cost. It’s gotten more expensive lately. For work I’d give it a 9 out of 10. For personal use, I’d look elsewhere.
Don’t start with God Mode. Start with the one question your team asks most, and build the bot that answers it.
Still want the templates?
Subscribe to ultrathink and download the copy links for both bots and all four prompts.
You're subscribed. Your templates are downloading.
If the download didn't start, download the templates (Markdown). The file has all four prompts. Swap the [brackets] for your own details before you paste.
Copy the bots straight into Grok Bot:
Common questions
Questions leaders ask us
Can Grok Bot make sales calls?
Not in my test. It refused a sales pitch, even a role-play one, but it made a thank-you call for me and opened by saying it was a virtual assistant on a recorded line.
When I share a Grok Bot, can my team see my logins?
No. Each person connects their own accounts, like Notion and Slack, and those logins stay private to them. You can also choose shared logins on purpose.
Can Grok Bot talk in a meeting?
Not yet. In my test it joined, took notes and answered questions in the meeting chat once I told it to make that the default. It couldn't answer out loud.
What plan do you need for team bots?
In my setup, browsing and adding shared team bots was available on team and enterprise plans. Check xAI's current plan list before you buy.
Is Grok Bot 1.0 worth it?
For work, I give it a 9 out of 10. It got more expensive recently, so for personal use I still reach for other tools.
Sources
Keep reading


