Grok Bot meeting prompts: prep, sit-in, recap drafts
Field case: a Bot joins a meeting you miss, announces itself, and takes notes. These prompts keep speaking-for-you and sending-the-recap on your side.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Prep
4 promptsCall brief from the last 90 days
1/21✨ What it does
The Bot writes a one-page brief for [MEETING] with [ACCOUNT OR PERSON] on [DATE]: people, last touches, risks, and questions. You walk in with it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: One-page brief for [MEETING] with [ACCOUNT OR PERSON] on [DATE]. Sources: [CALENDAR EVENT], [CRM], [EMAIL], [LAST DECK]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email attendees. Do not create a new event. Deliverable: Attendees, last touches, questions, landmines, links. Review point: I walk in with it.
Pro tip: Name the CRM fields you trust. Notes fields lie.
1:1 prep
2/21✨ What it does
The Bot preps a 1:1 with [NAME] from [LAST NOTES]: open loops, five agenda items, and landmines. You run the 1:1.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Prep 1:1 with [NAME]. Open loops, 5 agenda items, landmines. Sources: [LAST NOTES], [SLACK DM], [GOALS DOC IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not message them. Deliverable: Agenda, loops, links. Review point: I run the 1:1.
Pro tip: Point at the last 1:1 notes. Do not invent their career goals.
Week-ahead: what needs prep
3/21✨ What it does
The Bot reads [CALENDAR] and lists next week meetings that need prep or a decision, not every event. You block time for those.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: From [CALENDAR], next week's meetings that need prep or a decision. Sources: [CALENDAR], [PRIORITIES], [DECK FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not move or decline events. Deliverable: Event, why, missing prep, decision at risk. Review point: I block time.
Pro tip: Ask "needs prep or a decision". You already have a calendar app.
Panel or interview loop brief
4/21✨ What it does
The Bot briefs the [LOOP] for [CANDIDATE OR PANEL]: order, owners, and score signals. You send the panel Slack if you want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Brief the [LOOP] for [CANDIDATE OR PANEL]: order, owners, score signals. Sources: [CALENDAR], [SCORECARD], [RESUME OR BRIEF]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email the candidate or panel. Deliverable: Order, owners, signals, draft panel Slack (unpublished). Review point: I send the Slack if I want.
Pro tip: For hiring loops, pair with the recruiting scorecard page.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
Sit-in
4 promptsJoin, announce, notes
5/21✨ What it does
The Bot joins [LINK] at [TIME TZ] as [BOT NAME], says it is a note-taking Bot, and does not speak for you or accept action items. You send the follow-ups.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Join [LINK] at [TIME TZ] as [BOT NAME]. Announce you are a note-taking Bot. Do not speak for me. Do not accept action items for me. Sources: [AGENDA], [PRIOR NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not share notes outside this conversation. Do not record if the host forbids it. Deliverable: Attendees, decisions, asks, timestamps, what I owe. Review point: I send follow-ups.
Pro tip: Silent lurker Bots surprise people. Announce.
Voice while walking
6/21✨ What it does
The Bot watches [CALENDAR] and [RESERVATION TASK] while you are in transit and drafts options under [BUDGET], without booking. You book.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: While I am in transit, watch [CALENDAR] and [RESERVATION TASK]. Draft options. Do not book. Sources: [CALENDAR], [VENUE CONSTRAINTS], [BUDGET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not book. Do not email the guest. Deliverable: Options, conflicts, draft messages. Review point: I book.
Pro tip: Reservations still need your last click. Put a budget in the brief.
Live slide updates I still present
7/21✨ What it does
The Bot updates slides [N] in [DECK] from [SOURCE] if you ask during [MEETING], and will not rewrite the story slides. You present.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: During [MEETING], update slides [N] from [SOURCE] if I ask. Do not change narrative slides. Do not email the deck. Sources: [DECK], [SOURCE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Keep a copy of the original deck. Deliverable: What changed, old vs new, path. Review point: I present.
Pro tip: Mark which slides are number slides. Do not let it rewrite the story mid-call.
Do not speak for me
8/21✨ What it does
The Bot writes a speak-for-me ban: notes only, no commitments, no jokes at anyone expense, announce at join. You paste that ban into the Bot description.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the speak-for-me ban: notes only, no commitments, no jokes at anyone's expense, announce at join. Sources: My comfort level: [PASTE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not join a meeting as part of this task. Deliverable: Ban text for the Bot description. Review point: I paste it.
Pro tip: If someone asks the Bot a decision, it must say it will take that to you.
Recaps
4 promptsRecap draft in my voice
9/21✨ What it does
The Bot drafts a recap of [MEETING] to [PEOPLE] in your voice, quoting decisions, and does not send it. You send it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a recap of [MEETING] to [PEOPLE] in my voice. Quote decisions. Do not send. Sources: [NOTES OR TRANSCRIPT], style examples. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send. Do not add calendar holds. Deliverable: Subject, body, open questions, promises. Review point: I send.
Pro tip: Quote decisions. Paraphrase is how "we might" becomes "we will".
Action list with owners
10/21✨ What it does
The Bot builds an action list from [MEETING] and marks the owner as unknown if nobody was named. You assign the work.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Action list from [MEETING]. Owner unknown if none was named. Sources: Notes or transcript. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not assign people in Jira or email them. Deliverable: Action, owner or unknown, due if stated, quote. Review point: I assign.
Pro tip: Unknown is a valid field. Invented owners start wars.
Decision log line
11/21✨ What it does
The Bot writes one decision-log line if [MEETING] decided something, and says "no decision" if it did not. You paste the line into the log.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: If [MEETING] decided something, write one decision-log line. If not, say no decision. Sources: Notes, [DECISION LOG FORMAT]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit the log file except as a draft copy. Deliverable: Log line or no-decision. Review point: I paste it.
Pro tip: Do not promote a vibe to a decision.
Customer-facing vs internal recap
12/21✨ What it does
The Bot writes two recaps of [MEETING], one internal and one customer-facing, plus a do-not-leak list. You send the customer one if you want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Two recaps of [MEETING]: internal and customer-facing. Do not send either. Sources: Notes, [WHAT IS PUBLIC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send. Deliverable: Two drafts and a "do not leak" list. Review point: I send the customer one if I want.
Pro tip: Customer recaps do not include the "they are a pain" aside.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Calendar hygiene
3 promptsDouble-book and travel time
13/21✨ What it does
The Bot flags double-books and missing buffers on [CALENDAR] for [WEEK] using [BUFFER RULE], and does not move events. You move them.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flag double-books and missing buffers on [CALENDAR] for [WEEK]. Do not move events. Sources: [CALENDAR], [BUFFER RULE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not decline or move. Deliverable: Conflicts, suggested moves, draft notes to attendees. Review point: I move.
Pro tip: Put travel time rules in the brief (city, buffer).
Hold vs real meeting
14/21✨ What it does
The Bot lists holds older than [N] days with no agenda and no attendees besides you. You delete the ones you no longer want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List holds older than [N] days with no agenda and no attendees besides me. Sources: [CALENDAR]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete holds. Deliverable: Hold, age, keep/ask-me. Review point: I delete.
Pro tip: Do not delete holds. You might still want them.
Focus-time defense
15/21✨ What it does
The Bot finds [WEEK] meetings that do not map to [PRIORITIES] and drafts a decline for each. You send the decline.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Which [WEEK] meetings do not map to [PRIORITIES]? Draft a decline. Do not send. Sources: [CALENDAR], [PRIORITIES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not decline. Deliverable: Meeting, why it is off-priority, draft decline. Review point: I decline.
Pro tip: CoS "say no" applied to calendar.
Make the meeting Bot durable
6 promptsMeeting Bot description
16/21✨ What it does
The Bot writes a meeting description named [NAME] with the join-announce script, never-send, and never-speak-for-you rules. You create that Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a meeting Bot description named [NAME] with the announce script. Sources: [CALENDAR], [REVIEW WINDOW]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Never send recaps. Never speak for me. Always announce. Deliverable: Description plus announce script. Review point: I create it.
Pro tip: Include the join-announce sentence verbatim.
Morning prep routine
17/21✨ What it does
The Bot writes a weekday routine at [07:45] [TZ] that briefs today meetings that need prep and skips [RECURRING JUNK]. You enable it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekdays at [07:45] [TZ], briefs for today's meetings that need prep. Skip [RECURRING JUNK]. Sources: [CALENDAR], [CRM]. If calendar is down, fail closed. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create events. Deliverable: Routine card. Review point: I enable.
Pro tip: Skip the daily all-hands if it never needs prep.
What meeting Bots never do
18/21✨ What it does
The Bot writes a never-do list for meeting Bots: no speaking for you, no accepting actions, no sending recaps, no joining unannounced, no recording against [POLICY]. You paste those twelve items.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for meeting Bots. Sources: My rules and any recording policy: [PASTE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. Deliverable: 12 never-do items. Review point: I paste it.
Pro tip: Paste this before you ever give it a meeting link.
Sit-in that announces itself
19/21✨ What it does
The Bot joins [LINK] at [TIME TZ] as [BOT NAME], announces it is taking notes, and refuses action items. You send the follow-up.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Join [LINK] at [TIME TZ] as [BOT NAME]. Announce you are a note-taking Bot. Do not speak for me. Sources: [CALENDAR], [AGENDA]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not accept actions. Do not send the recap. Do not record if [POLICY] forbids it. Deliverable: Notes: attendees, decisions, I-owe, timestamps. Review point: I send follow-up.
Pro tip: Silent lurkers burn trust. Write the announce line in the Bot description.
Prep brief the morning of
20/21✨ What it does
The Bot writes a one-page prep for [MEETING]: who, last touch, open asks, and landmines. You walk in with it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: For [MEETING], one-page prep: who, last touch, open asks, landmines. Do not create the event. Sources: [CALENDAR], [CRM], [ATS OR NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email attendees. Do not move the meeting. Deliverable: One page, sources. Review point: I walk in.
Pro tip: Skip the weekly all-hands. Prep the customer and the candidate.
Recap you still send
21/21✨ What it does
The Bot drafts a recap for [MEETING] with decisions and owners, and leaves out anything that was not actually said. You hit send so the voice is yours.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a recap for [MEETING] with decisions and owners. Do not send. Sources: [NOTES], [RECORDING IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email the thread. Do not create tasks in other people's tools. Deliverable: Subject, body, do-not-say. Review point: I send.
Pro tip: If a decision was not said, do not write it into the recap to be "helpful".
Free tool
Transcript Summarizer
Turn a meeting or video transcript into a summary with action items.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides