grokbotwiki

Dispatch

by Filippo Fonseca ↗Inbox & calendar Share link liveChecked

Nightly scan of email, Slack, LinkedIn and X DMs that books the missing calls

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

A close-the-day desk. Nightly scan of email, Slack, LinkedIn, and X DMs; if someone agreed to a call and no calendar invite exists, book it. Morning briefing and evening roundup emails covering missed messages, plus a short language lesson and frontier AI + robotics news in the morning mail. Never send email without a go-ahead except those two pre-approved briefs.

Description as published on the x.ai share page when last checked (2026-11-01).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Recurring work
Nightly scan of email, Slack, LinkedIn, and X DMs
Promised limits
Never send email without a go-ahead except those two pre-approved briefs
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

Busy people who agree to calls across email, Slack, LinkedIn, and X messages and lose track of which ones never got a calendar invite.

Not for

Anyone uncomfortable with a Bot creating calendar events on its own or reading private messages across several platforms.

What it does

Every night it scans your messages on four channels for one specific gap: a conversation where someone agreed to a call but no invite exists, which it then books. It also sends you two pre-approved emails, a morning briefing and an evening roundup of messages you missed. The morning email adds a short language lesson and news about frontier AI and robotics. Any other email waits for your go-ahead.

First messages to try

  1. Scan the last 7 days of email and Slack. List every agreed call that has no calendar invite, and don't book anything yet.
  2. For the morning briefing, make the language lesson beginner Spanish, three phrases a day.
  3. Show me tonight's roundup as a draft so I can adjust the format.

Apps and accounts

Its description mentions email, Slack, LinkedIn, X direct messages, and a calendar. Expect a connector or browser login for each of those.

Cautions

  • Once it decides a call was agreed, it books it without asking. A misread 'sounds good' can send an invite to the wrong person, so run it in list-only mode for the first week.
  • Reading LinkedIn and X messages usually means browser logins on the shared computer, which every other Bot on your account can use too.

Compare with: Gmail to-do and reply assistant by ED DRINGChief by SmoresBoy Jack

Before you add it

Specific to this Bot, from what its description says:

  • It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
  • It names Slack, X (Twitter), LinkedIn. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Slack ↗
  • Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Filippo Fonseca. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, ZeroPointRepo/GrokBotDev, elie222/botdirectory.ai and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/dispatch)

Or promote this template in the labelled Featured row, from $19.