Grok Bot for Your Team · Online Course · Catalyst88
Catalyst88

Courses

Grok Bot for Your Team

Get Your People Working with Bots, Not Around Them

Get your people working with bots, not around them. In eight short modules you'll take the bots you already run on your own and turn them into shared Team Bots your staff actually use: each with a written lane, one coordinator that routes requests, a verifier on anything that ships, draft-before-send on every outgoing message, a task log that shows the hours saved, and routines that stay quiet when nothing changed. You keep the final say on anything that leaves the building.

34 lessons · 159 min

Buy for $99 Included with Chairman's Circle

Welcome to Grok Bot for Your Team

  1. Welcome to Grok Bot for Your Team

    5 min

    Understand what changes when a team, not just a founder, works with bots, and what the eight modules and the 30-day capstone will build.

From My Bots to Our Bots

  1. What Changes When Bots Are Shared

    5 min

    Name the three things that change when a bot is shared: who can use it, who can change it, and whose logins it carries.

  2. Pick the First Team Job

    5 min

    Choose a first team job that is frequent, costs real hours, and is low risk if a draft is wrong.

  3. Set Up Team Bots

    5 min

    Create your first Team Bot, share it with the right people, and write the access list for your first three bots.

Design the Roster

  1. One Bot per Job, with a Written Lane

    5 min

    Write each bot's lane as what it owns, what it never touches, and who it reports to.

  2. The Coordinator Bot

    5 min

    Set up one bot that takes requests, routes each to a single owner, and reports status back.

  3. Builder, Then Verifier

    5 min

    Add a second bot that checks work before it ships.

  4. Make the Roster Visible

    5 min

    Give the team one place to see every bot, its owner and its lane.

Share Bots Safely

  1. Who Can Use Each Bot

    5 min

    Share a bot with one person, the whole organization, or a group you invite, and know why you picked each.

  2. Who Holds the Keys

    5 min

    Decide which logins each shared bot needs and who adds them. Creators and managers can add credentials.

  3. Who Can Change a Bot's Memory

    5 min

    Set who is allowed to update what a shared bot remembers.

  4. Routines for Each Person

    5 min

    Use per-user routines so each teammate gets the same job run on their own work.

Guardrails the Whole Team Follows

  1. Draft Before Send, for Everyone

    5 min

    Make every outgoing email and Slack message arrive as a draft card the sender approves. Draft cards can carry attachments, so the files get checked too.

  2. Approvals: Who Can Say Yes

    5 min

    Write which actions anyone may always allow, which need the bot's owner, and which always need the founder.

  3. Hidden Instructions

    5 min

    Teach the team what a hidden-instruction warning means and what to do when one appears.

  4. When a Login Lapses

    5 min

    Name who reconnects each app when Grok Bot sends a sign-out notice with its refresh link.

Teach the Team to Work with Bots

  1. The Team Request Template

    5 min

    Give staff a shared template with outcome, sources, limits, deliverable, and stop point.

  2. Where the Team Talks to Bots

    5 min

    Pick the right surface for each job: the bot's own chat, a group chat, Slack, or the iPhone share sheet sent to a chosen bot.

  3. Find It Again

    5 min

    Use chat search, which now includes older messages by default, plus Library filter chips, instead of asking the founder.

  4. Hand Off Hold Time

    5 min

    Use phone calls for queues, phone trees, and supplier or insurance calls, with a live transcript and takeover. US only, not Washington or Illinois, and each call needs a person to start it.

  5. A Teammate's First Week with Bots

    5 min

    Run a short onboarding for each new teammate.

Write Decisions Down So Bots Reuse Them

  1. Memory Is Not the Source of Truth

    5 min

    Have bots reopen the current record before any decision that costs money.

  2. A Decision Log Bots Read

    5 min

    Keep one log of decisions with date, owner, reason and source, and point every bot at it.

  3. Turn Procedures into Skills

    5 min

    Convert a team procedure into a saved skill the whole roster can use.

Measure the Work

  1. Log Every Task with an Accountable Bot

    4 min

    Record each piece of bot work with the bot that owns it, the request, the output, and its status.

  2. Put a Human-Hour Value on It

    5 min

    Give each task type a standard number of human hours so the log adds up to a real figure. Bot analytics now show hours saved; compare them with your log.

  3. The Weekly Bot Review

    5 min

    Keep, fix, or retire each bot based on its numbers.

Keep Usage Lean as the Team Grows

  1. Where Usage Goes

    5 min

    Know that every reply, every bot-to-bot message, and every routine run spends usage.

  2. Routines That Stay Quiet

    5 min

    Write routines that report only when something changed.

  3. No Duplicate Work

    5 min

    Keep one owner per stage, and have big jobs check with the coordinator before they start.

Capstone: Your Team's First 3 Bots in 30 Days

  1. Days 1 to 7: Coordinator, Lanes, and the Roster

    5 min

    In the first week, set up the coordinator bot, write a three-line lane for each bot you plan to launch, and ask the coordinator to keep a visible roster page.

  2. Days 8 to 14: The First Specialist and a Verifier Checklist

    5 min

    In the second week, launch the first specialist bot on the job you picked in Lesson 1.2, and write the checklist a verifier will use before anything ships.

  3. Days 15 to 21: Share, Guardrails, and Two Teammates

    5 min

    In the third week, share the coordinator and the first specialist with the team, put draft-before-send and the approvals table in place, and onboard two teammates.

  4. Days 22 to 30: The Third Bot and the Evidence

    5 min

    In the last week, add the third bot, start the task log with human-hour values, run the first weekly review, trim one noisy routine, and gather the day-30 evidence.

Related courses

Loading Community