Grok Bot: Essentials

Get everyday work done with Grok Bot. Learners set up a focused Bot, write clear requests, attach files, sign in safely, connect apps, handle approvals, and start using one of their team's Shared Bots (formerly called Team Bots) in the app and in Slack. By the end they can take a read-and-prepare task from request to a reviewed, unsent result.

What this course covers

The course runs across 10 topics, each one a short adaptive session rather than a recorded lecture. The tutor explains the idea, works an example, checks understanding, and adjusts the next step to the answer given.

Install on desktop and phone and sign in with your company account — Install the Grok Bot desktop app (Mac, Windows or Linux) and the iPhone or Android companion app, and sign in with your Cursor account through your company's sign-in. Check that the same Bots and chats appear on both.
Create a focused Bot with one job, and ask it to remember how to work — Create a Bot with +, name it, and give it one main job in the first message: the job, its sources and what needs your approval. Ask it to remember, ask it to repeat what it remembers, and correct anything wrong.
Write a strong request: outcome, sources, limits, deliverable, where to stop — Turn a vague ask into a request that names the outcome, the sources that matter, the limits, the deliverable and the point where the Bot must stop for you. Compare the results of a weak and a strong request.
Attach files and ask for a result you can check — Attach the files the job needs and ask for a result you can check: a table with working, a document with source links or an unsent draft. Check one figure yourself before you trust the rest.
Sign in safely: saved logins, the secure form, and taking control for passwords and codes — When a site needs a login, let the Bot use a saved login or the secure form, or choose Open computer and take control to type a password or code yourself, then choose I'm done. Never paste passwords or codes into chat.
Connect apps, use @ for apps and Bots, and ask for skills by name — Connect apps such as email or Slack, knowing every one of your Bots can use them, and spot "Disabled by team admin". Type @ to bring in an app or another Bot, and ask for a saved skill by name.
Approvals: Allow once, Always allow, Deny, and asking for a plain-language explanation — Read an approval card and choose Allow once, Always allow or Deny, asking the Bot to explain in plain words first when unsure. Prefer Allow once for anything touching accounts, money or shared resources.
Shared Bots: find your team's Shared Bot, start your private chat, and @mention it in Slack — Find one of your team's Shared Bots (formerly called Team Bots) with + -> Browse shared Bots (then Add) or open a teammate's link and choose Start a chat, and @mention it in Slack after linking under Settings -> General -> Shared Bots -> Link, if your team has added it. Learn that it uses your own connected accounts, keeps your chat private, and keeps what it saves for the team separate from what it remembers about you.
Watch the computer, redirect mid-task, and stop work — Follow the Bot's work in the computer panel, send a new instruction to change direction, and say "Stop now" when it goes wrong, knowing that stopping doesn't undo what's already done.
Capstone: a read-and-prepare task from request to reviewed result — Use the Copperfen Logistics sample pack: brief a focused Bot, attach the files, get a checked list of late shipments and unsent customer drafts, and review them before anything goes out.

Skills you build

Results are measured against named skills in the OneRange taxonomy of more than 10,000 skills, so a manager sees proficiency per skill rather than a completion tick.

Who it is for

Anyone who hands work to Bots: sales, operations, finance, recruiting, marketing and managers. No technical background needed.. The material is pitched at beginner level, and takes roughly 120 minutes at a typical pace. Because every session adapts, someone who already knows a topic moves through it quickly instead of sitting through an explanation they do not need.

It sits in the Tool: Grok Bot track of the Vero AI Catalog, and can be assigned to one person, a team, or the whole company.

How it is delivered and assessed

Delivery is conversational and interactive, including guided lab, branching scenario exercises. There is no video to sit through and no slide deck to click past.

Understanding is checked with a lab assessment of 5 items, with a pass mark of 70%.

Administrators can copy this course into their own library and adapt it — edit the outline, change the duration, swap the assessment format, or ground it in internal documentation so answers cite the company's own source material.

Also in this track

Grok Bot for Developers: Essentials — Incidents & Performance Playbook — A focused 45-minute playbook for incidents and performance work with Grok Bot. Learners hand a Bot a sampled request log and the deploy log from a latency regression, have it measure before and after on its cloud computer, and separate facts from hypotheses with the highest-impact cause first. They finish by setting up a recurring, read-only health report as a Shared Bot (Shared Bots were formerly called Team Bots), or by writing that setup down, with no unsupervised production changes.
Grok Bot: Essentials — Sales & Accounts Playbook — A focused, 45-minute playbook for sales and account work in Grok Bot. Learners have a Bot research and score accounts against an ideal customer profile, prepare review-ready outreach drafts that are never sent, and build a weekly account-health watch list - then see the same job as one Bot the whole sales team can use through Shared Bots (formerly called Team Bots).
Grok Bot: Essentials — Chief of Staff Playbook — A focused, 45-minute playbook for running a daily digest with Grok Bot. Learners have a Bot pull email, Slack, calendar and notes into one source-linked digest, map it to priorities and the decisions an executive owes, tune out noise and schedule it - then see how a leadership team could share the same job through Shared Bots (formerly called Team Bots).
Grok Bot: Intro — A short first look at Grok Bot, the app where named AI teammates called Bots finish work inside your tools. Learners see how it differs from Grok, how a Bot uses its own cloud computer and stops for approval, and how Shared Bots (formerly called Team Bots), one Bot the whole team chats with, differ from your own Bots, then hand a first Bot one small read-only task.
Grok Bot: Essentials — Finance & Operations Playbook — A focused, 45-minute playbook for weekly expense review with Grok Bot. Learners have a Bot reconcile a week of expenses against policy with a cited section for every flag, prepare one follow-up draft per owner, and prove the totals tie back to the source - with nothing approved, changed or sent - then see how a finance team could share the same job through Shared Bots (formerly called Team Bots).
Grok Bot for Everyone Pathway — Hand real work to Grok Bot in any role: from your first Bot to skills, routines, Pages, Bot teams and guardrails, with Shared Bots (formerly called Team Bots) at every level, from using your team's Shared Bot to running Shared Bots across a department. Also includes 3 optional playbooks (Sales & Accounts, Chief of Staff, Finance & Operations) to take any time after Essentials; they don't count toward the certificate.
Cursor & Grok Bot for Everyone Pathway — One path for teams that use Cursor with Grok Bot included. A short placement check for each tool sends you to the right Cursor course and the right Grok Bot course. Also includes 6 optional playbooks (Cursor: Internal Tools, Data & Reporting, Prototypes; Grok Bot: Sales & Accounts, Chief of Staff, Finance & Operations) to take any time after Essentials; they don't count toward the certificate.

Frequently asked questions

How long does this course take?

It runs roughly 120 minutes at a typical pace. Because every session adapts, someone who already knows a topic moves through it quickly instead of sitting through an explanation they do not need.

How is it assigned to a team?

An administrator assigns it from the Vero dashboard to one person, a team, a department or the whole company, and sees progress and results per person and per skill.

Can we customise it with our own documents and terminology?

Yes. Administrators can copy this course into their own library and adapt it — edit the outline, change the duration, swap the assessment format, or ground it in internal documentation so answers cite the company's own source material.

Course code TUL-GBOT-101.