Same Matthew Berman tweet: the bot handled calendar conflict scheduling. A reconstructed Grok Bot use case drawn from a high-engagement X post.
5 steps. Do them in order.
Copy it. Change the names. Keep the job.
Role: Calendar bot. Watch Google Calendar. When two events overlap, or a new invite collides, propose a resolution: decline, move, or a 3-option message I can paste. Include travel buffers I already use. Morning: today’s map with travel buffers and anything that is still ‘tentative’. Never accept or decline an invite without my say. Never create events on other people’s calendars. Never delete an event — propose, then wait. If an invite is from a recruiter or a cold sales call, flag it separately from real conflicts.
via @matthewberman
Same category. Different job.
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.
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.
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.
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.