Open Loop Closer

Finds VIP threads you went silent on in Slack or email and drafts a paste-ready follow-up

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

Finds VIP hangs where you went silent on work Slack or email, then drafts a paste-ready follow-up in chat. HITL only — never sends without your yes.

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

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.

Apps it names
Slack
Promised limits
never sends without your yes
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

Someone juggling a lot of relationships across work Slack and email who keeps losing track of conversations that went quiet with people worth staying in touch with, and wants a ready-to-paste nudge instead of a blank cursor.

Not for

Someone who wants it to actually send the follow-up for them, since it is built to stop at a draft you copy in yourself.

What it does

The bot scans your work Slack and email for threads with the contacts you've told it to watch, looking for the ones where the other side replied last and nothing followed. For each stalled thread it writes a short, ready-to-paste message that picks up the original context instead of a generic check-in. Because it is built as a human-in-the-loop tool, it stops once the draft exists and leaves copying, editing, or sending entirely up to you.

First messages to try

  1. Here are the people and projects I don't want to go quiet on: [list]. Watch my Slack and email for threads with them that have stalled, and tell me what you're tracking before you start.
  2. Show me every open thread where I'm the one who hasn't replied in over a week, sorted by how important the contact is.
  3. Draft a follow-up for the [name] thread that references what we last discussed, but don't send anything — I'll paste it in myself.

Apps and accounts

Its description mentions work Slack and email as the two places it watches, plus a chat drafting step, so expect it to need read access to both. It names no specific connector, so check which workspace and mailbox it's actually reading before approving access.

Cautions

  • A bot reading both Slack and email at once can see more of your working life than one task needs; scope which channels and folders it may enter.
  • Confirm the never-sends rule actually holds the first time it drafts something to a sensitive contact, like a client or your manager, rather than taking the description's word for it.
  • Watching many contacts across two tools can add up quickly; ask for one weekly summary instead of constant pings if the checks start to climb.

Compare with: Chief by SmoresBoy JackFollow-Up Keeper by aaron creechPost Call Assistant by Priya Patel

Before you add it

Specific to this Bot, from what its description says:

  • It names Slack. 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, Scott Metcalf. 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, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev 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/open-loop-closer)

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