The Optimal Flowlearn
Artificial intelligence
Grok Bot

Build a team of agents with Grok Bot

Learn to define agents with distinct tasks and context in Grok Bot, coordinate focused work and review their results and permissions before using them.

Intermediate12 h · 6 × 2 hSpanish & English
Contact

Find your starting point

A good fit when you already give instructions to AI and want to explore Bot roles and handoffs in an authorised Grok Bot environment.

Another option to consider

Strategic AI adoptionIf you are still deciding which use case merits a pilot and who will supervise it, choose strategic adoption.
Hours and sessions
12 hours live · 6 sessions of 2 h.
Group size
Up to 12 participants per trainer as a reference, adjusted to the practice and feedback.

What you will learn

  1. 01

    Define roles, tasks and completion criteria for a small team of Bots.

  2. 02

    Prepare agreed context and access for a collaboration test.

  3. 03

    Review a task handoff and document results and approval points.

A proposed programme

Coordinate three Grok Bot Bots to compare supplier quotes: extract terms, prepare a table and review the brief for a person. Practise with fictional files, clear owners and visible handoffs. Distinguish this group of personal Bots from a Team Bot: one Bot that several team members can use.

We adapt the selection and depth of the modules to the group's starting point and goals.

01

Design the roles

Tasks, context, memory and limits for each Bot in a specific use case.

You will work on

  • Define three roles: gather terms, compare and review; assign a deliverable and completion criteria to each Bot.
  • Prepare the brief and fictional quotes, identifying the source of each fact and what must remain a question.
  • Distinguish each Bot's context and memory from the computer, files and sessions shared by the account.
Practice
Set up the three Bots and a shared brief to compare 40 stationery kits, leaving the purchase decision to a person.
How you will check it
Specific roles, identified sources and explicit limits; the participant explains that a role is not a permission boundary.
02

Coordinate a test

Messages, shared context and handoffs between Bots using available features.

You will work on

  • Coordinate the group through messages and mentions, with one person or Bot owning the next step.
  • Rehearse a handoff with a file reference, status, questions and outstanding work, using available features.
  • Correct an ambiguous request and prevent two Bots from editing the same deliverable at once.
Practice
Move from extracted terms to a comparison and then a review, making each Bot's source version traceable.
How you will check it
An understandable handoff with source, result and questions; the next Bot can continue without reconstructing the brief.
03

Review access and results

Permissions, shared files and criteria for keeping decisions and actions supervised.

You will work on

  • Check prices, quantities, delivery and exclusions against the original files, separating facts from inferences.
  • Review shared files, access and approvals; locate requests in the relevant individual conversation, as they do not appear in the group.
  • Document the result, blockers and next human step before reusing the process.
Practice
Find a quote that omits delivery costs, return the question to the responsible Bot and prepare the brief for human review.
How you will check it
A corrected comparison with references and outstanding facts, ending in a reviewable proposal without sending messages or making purchases.

Three Bots prepare a supplier comparison

Teaching example

You will prepare several Bots for a sample task, rehearse a handoff with test data and review the result before accepting any external action.

Fictional classroom case. An office team needs to compare quotes for 40 stationery kits. We use a brief and three invented supplier files. The Gather, Compare and Review Bots belong to one practice account; the participant retains the final decision.

Starting point
The quotes describe quantities and delivery differently. One includes delivery and another does not specify it, so ranking by price alone could lead to an incorrect conclusion.
First attempt
The Bots receive “find the best quote”. Two prepare different comparisons and one presents unknown delivery costs as free.
What we review
During the exercise review, the trainer asks for one owner per deliverable and a handoff with file, version and questions. The review Bot must check terms against the sources and return unconfirmed details instead of filling them in.
Result
The intended handover combines a sourced table, delivery costs awaiting confirmation and a short brief for a person. Handoffs show who continues and what is missing; comparison does not authorise contacting suppliers or making the purchase.

One owner at each stage

  1. Gather

    • Terms

      Quantity, price, delivery and exclusions

    • Sources

      File and reference for each fact

  2. Compare

    • Common criteria

      The same need across three quotes

    • Visible questions

      Delivery costs not confirmed

  3. Review

    • Source check

      Table and brief against the originals

    • Human decision

      Proposal ready to approve or correct

Teaching diagram of three collaborating personal Bots. A Team Bot is a different arrangement: one Bot shared with team members.

Before calling it complete

  • Each term can be found in a quote; missing information is marked as awaiting confirmation.
  • Each deliverable has an owner and the handoff identifies file, version and questions.
  • Roles share the account's computer and access; the workflow ends with human review.

Sessions to put it into practice.

Reference edition · 12 h live

Reference edition: 12 live hours across 6 sessions of 2 hours. Practice takes place during the sessions with fictional files. Plan, available features and any additional preparation are confirmed for each edition.

  1. Session 12 h

    Define the shared work

    Define the result, distinguish personal Bots from Team Bots and review the practice setup.

    By the end

    A shared brief with a human decision and fictional sources.

  2. Session 22 h

    Prepare the three roles

    Set up tasks, context and deliverables; check what the account's Bots share.

    By the end

    Three Bots with clear responsibilities and documented limits.

  3. Session 32 h

    Extract and hand off

    Gather quote terms and pass a result with references and questions to the next owner.

    By the end

    A reviewable extraction and a first visible handoff.

  4. Session 42 h

    Build the comparison

    Coordinate messages and files, avoid duplication and compare quotes against common criteria.

    By the end

    A table distinguishing known and outstanding terms.

  5. Session 52 h

    Review access and proposals

    Check the brief against sources and review limits and approval requests in the relevant place.

    By the end

    A corrected brief and a decision reserved for a person.

  6. Session 62 h

    Repeat with a variation

    Introduce a changed quote and review the workflow and its documentation with trainer feedback.

    By the end

    A classroom process the participant can explain and correct.

If your team needs to go further

  • Creating and publishing a Team Bot for several people requires a team plan, shared setup and an agreed scope.
  • Connectors, routines, real messages or actions in company systems require access review and a separate scope.

Learn with someone who develops projects for companies.

Borja Martínez

Borja Martínez

The Optimal Flow consultant

Over two years of experience developing projects for companies across industries and sizes.

Borja is the planned trainer for this programme. Dates, language and his availability are confirmed when the edition is agreed.

Once you have a foundation, go further.

Extensions with their own scope, agreed separately from the initial training.

Continuation · 8 h

Test and improve your AI agents and workflows

Learn to check whether a change improves your AI agent or workflow: compare versions using the same cases and decide what to fix using evidence.

View programme →

With guidance, practice and support.

Each delivery includes working materials, feedback on practical work and assessment against the agreed objectives.

See materials, support and terms

Materials you can keep

Downloadable, versioned guides, exercises and review criteria for internal use.

To prepare and complete the delivery

A short recommendation, an editable communications kit and a group learning report.

TOF’s own certificate

A certificate of achievement after the agreed assessment. It is not a vendor certification.

A month of email support

On the content covered, up to two accumulated hours for the whole group.

Your team carries out the practice. Implementation services are agreed separately. See the scope →

Keep learning

Other options for the task you want to work on. Each link explains what that programme adds.

Artificial intelligence

Prompting for generative AI

To formulate tasks, context and completion criteria that you can then check during the test.

View course
Automation

Process automation with AI

To explore how to scope an AI process and decide its human intervention points.

View course

What does your
team need to learn?

Tell us what you want to work on, how many people would take part and where you are based. We will prepare a proposal with scope, sessions and a budget.

Contact

Would you like to ask about FUNDAE?

We check eligibility for each company and edition, subject to requirements and available training credit in Spain. Funding is neither automatic nor guaranteed. Official FUNDAE information ↗

Discuss eligibility
The Optimal FlowlearnGrok Bot

Build a team of agents with Grok Bot

Learn to define agents with distinct tasks and context in Grok Bot, coordinate focused work and review their results and permissions before using them.

12 live hours6 sessions of 2 hoursIn Spanish or English

Reference edition: 12 live hours across 6 sessions of 2 hours. Practice takes place during the sessions with fictional files. Plan, available features and any additional preparation are confirmed for each edition.

Who it is for

People designing processes or coordinating tasks who want to explore Grok Bot agents. Suitable for participants with basic experience giving instructions to AI.

By the end you will be able to

  • Define roles, tasks and completion criteria for a small team of Bots.
  • Prepare agreed context and access for a collaboration test.
  • Review a task handoff and document results and approval points.

Before we begin

Grok Bot access and an authorised practice environment. Plan, availability and permissions will be confirmed; connections and actions are limited to the agreed scope.

Reference setup: the Grok Bot desktop app, an authorised practice account, three personal Bots, a group chat and fictional file attachments. Before each edition, we will check the plan, access, collaboration features and approval controls. An account's Bots share its computer, files, sessions and available credentials: assigning roles does not isolate permissions. The case uses prepared files and needs no supplier accounts, connectors or purchases. If a feature is unavailable, an adaptation is agreed before starting.

Your trainer

Borja Martínez
The Optimal Flow consultant

Over two years of experience developing projects for companies across industries and sizes.

Borja is the planned trainer for this programme. Dates, language and his availability are confirmed when the edition is agreed.

Course online · theoptimalflow.com/en/learn/courses/grok-bot-team-agentsinfo@theoptimalflow.comVersion 1 · Document reviewed: 13 October 2026
The Optimal FlowlearnBuild a team of agents with Grok Bot

Programme sessions

  1. Session 1 · 2 h

    Define the shared work

    Define the result, distinguish personal Bots from Team Bots and review the practice setup.

    Result: A shared brief with a human decision and fictional sources.

  2. Session 2 · 2 h

    Prepare the three roles

    Set up tasks, context and deliverables; check what the account's Bots share.

    Result: Three Bots with clear responsibilities and documented limits.

  3. Session 3 · 2 h

    Extract and hand off

    Gather quote terms and pass a result with references and questions to the next owner.

    Result: A reviewable extraction and a first visible handoff.

  4. Session 4 · 2 h

    Build the comparison

    Coordinate messages and files, avoid duplication and compare quotes against common criteria.

    Result: A table distinguishing known and outstanding terms.

  5. Session 5 · 2 h

    Review access and proposals

    Check the brief against sources and review limits and approval requests in the relevant place.

    Result: A corrected brief and a decision reserved for a person.

  6. Session 6 · 2 h

    Repeat with a variation

    Introduce a changed quote and review the workflow and its documentation with trainer feedback.

    Result: A classroom process the participant can explain and correct.

A fictional classroom case

Three Bots prepare a supplier comparison

Fictional classroom case. An office team needs to compare quotes for 40 stationery kits. We use a brief and three invented supplier files. The Gather, Compare and Review Bots belong to one practice account; the participant retains the final decision.

By the end of the exercise: The intended handover combines a sourced table, delivery costs awaiting confirmation and a short brief for a person. Handoffs show who continues and what is missing; comparison does not authorise contacting suppliers or making the purchase.

Course online · theoptimalflow.com/en/learn/courses/grok-bot-team-agentsinfo@theoptimalflow.comVersion 1 · Document reviewed: 13 October 2026
The Optimal FlowlearnBuild a team of agents with Grok Bot

What we will work on

Design the roles

  • Define three roles: gather terms, compare and review; assign a deliverable and completion criteria to each Bot.
  • Prepare the brief and fictional quotes, identifying the source of each fact and what must remain a question.
  • Distinguish each Bot's context and memory from the computer, files and sessions shared by the account.

Practice: Set up the three Bots and a shared brief to compare 40 stationery kits, leaving the purchase decision to a person.

Coordinate a test

  • Coordinate the group through messages and mentions, with one person or Bot owning the next step.
  • Rehearse a handoff with a file reference, status, questions and outstanding work, using available features.
  • Correct an ambiguous request and prevent two Bots from editing the same deliverable at once.

Practice: Move from extracted terms to a comparison and then a review, making each Bot's source version traceable.

Review access and results

  • Check prices, quantities, delivery and exclusions against the original files, separating facts from inferences.
  • Review shared files, access and approvals; locate requests in the relevant individual conversation, as they do not appear in the group.
  • Document the result, blockers and next human step before reusing the process.

Practice: Find a quote that omits delivery costs, return the question to the responsible Bot and prepare the brief for human review.

Extensions agreed separately. Creating and publishing a Team Bot for several people requires a team plan, shared setup and an agreed scope. Connectors, routines, real messages or actions in company systems require access review and a separate scope.

What accompanies the programme

  • A downloadable, versioned guide, exercises and review criteria; keep a copy for internal use.
  • A short recommendation, editable kit and group learning report. Responsibilities, a prior access check, handover and recipients are agreed for each delivery.
  • TOF’s own certificate of achievement after passing the agreed assessment. It is not a vendor certification.
  • Email support on the content covered for one calendar month after the last session. A maximum of two accumulated hours for the whole group, with a response time of up to two working days.

Clients provide licences unless expressly agreed otherwise. Recordings are agreed in advance. Implementation, work carried out independently by TOF, production deployment and ongoing maintenance are quoted separately. Delivery link access is agreed per delivery. Later updates and specific support require agreement. Structured documents and text alternatives; participation needs reviewed before starting.

Full format and terms → theoptimalflow.com/en/learn/how-we-teach
Course online · theoptimalflow.com/en/learn/courses/grok-bot-team-agentsinfo@theoptimalflow.comVersion 1 · Document reviewed: 13 October 2026