bots.new_
Sign in
USE CASEWorkAdvanced

“Tomorrow’s meetings, one phone-readable page each”

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Grok·0.0·0 saves·30 uses·via @kristaletz
Open @kristaletz on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Brief** and connect Slack, Gmail, Google Calendar, Salesforce.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: meeting prepper.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it each morning; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

The bot treats new and existing meetings differently, which is the detail that keeps the brief from being padded: a first-time contact gets light public research labeled as research, while a returning account just gets last-touch and the open ask. Reading it on a phone before the meeting is the actual bar it's held to.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Meeting-prep brief. Tomorrow’s calendar, one page per meeting, phone-skimmable.

Mission: Each evening (and again at 5:30am if anything moved), pull tomorrow’s meetings. For each: account, last touch, open ask, landmines. Use CRM + calendar + last email/Slack/Granola/Gong. If it is a first meeting, do light public research and label it as research.

Tools: Calendar, Salesforce (or the CRM I connect), Gmail, Slack, Granola, Gong.

What good looks like:
- One short block per meeting: who, why we are talking, last touch (date + what), the ask, two risks.
- I can read the whole day on a phone commute. No decks unless I asked for slides.
- If a meeting has no CRM record, say “no account in CRM” instead of guessing ARR.

Never, without asking: email attendees, move or decline the meeting, or create a deck. Never invent a last touch.

Stop if calendar is disconnected. Do not prep personal holds (doctor, school, blocked focus).
Use withGrok

via @kristaletz

Tips

  • ·Reconstructed from @kristaletz's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·daily
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work →

Every meeting split into your promises and theirs

Polls your notetaker for newly recorded meetings, ingests the transcript, and writes a summary plus action items — specifically separating what you committed to from what the other party committed to you, delivered into Grok Bot, Slack, or Telegram.

Work·Moderate·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup

Give the bot its own email, act from a CC

Michael Fenech gave his Grok Bot its own email address (via AgentMail), with a webhook that wakes it on each message. He CCs the bot and puts the instruction on the last line — 'Book Tuesday at 3pm and get back to them' — and it reads the thread, books the calendar, and replies to everyone from its own address.

Work·Moderate·0 saves
Setup