← Back to library

Give your agents office hours instead of constant pings

Michael Fenech (@Michael_Fenech_) shared a prompt that gives a Grok Bot team office hours: the lead agent audits who interrupts you, sorts messages into urgent, decision and FYI, and moves everything non-urgent into scheduled briefings. We explain how to adapt it to any multi-agent setup.

  • OutcomeHave your lead agent list every agent and routine that messages you, sort each message type into urgent, decision or FYI, batch decisions into two daily briefings with a recommendation each, collect routine updates into a single evening summary, and set clear rules for the rare cases that may interrupt you.
  • SetupUnder an hour
  • LevelStarter
  • CreditMichael Fenech (@Michael_Fenech_)
View original
Works with
Grok BotClaude CoworkChatGPT agentMicrosoft Copilot

Published Oct 30, 2026Updated Oct 30, 2026AI dry run on sample input: passed Oct 30, 2026Source verified Oct 30, 2026

When should you use it?

  • Your agents message you all day with questions, approvals and progress notes
  • Approval requests expire because they arrive while you are busy
  • You want fewer interruptions without missing anything urgent

Not for: Incident response or on-call work, where every alert may need an immediate reply; A single agent that only messages you once or twice a day; Setups where agents cannot change how or when they notify you

What do you need, and what do you get?

You need

  • A lead agent that can see your other agents, their routines and how they notify you
  • Two times of day that suit you for reviewing decisions
  • Your own definition of urgent, such as security alerts, payment problems or customer-facing outages

You get

  • An inventory of every agent and routine that contacts you
  • Each message type labeled urgent, decision or FYI
  • Two scheduled decision briefings with context, a recommended action and the cost of waiting
  • One end-of-day summary of routine updates
  • Escalation rules per agent, plus a fix for approvals that would expire before your next review

How does it work, step by step?

  1. Paste the promptGive Fenech's prompt to your lead agent; it audits first and changes nothing yet.
  2. Check the urgent listReview what it classed as urgent and tighten or widen the criteria.
  3. Pick your windowsApprove two review times that fit your day, such as late morning and mid-afternoon.
  4. Approve the changesLet it update notification rules agent by agent once you agree with the plan.
  5. Review after a weekLook for anything that should have interrupted you but waited, and adjust.

The prompt

The original prompt by Michael Fenech (@Michael_Fenech_), word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, Claude Cowork, ChatGPT agent and others. Values in lime are placeholders.

Original prompt by Michael Fenech (@Michael_Fenech_)

Word for wordby Michael Fenech (@Michael_Fenech_)
Set up an office-hours system for my Grok Bot team.

1: AUDIT - Identify every Bot and routine that currently sends me notifications, questions, approval requests or progress updates.

2: CLASSIFY - Separate them into three categories:

URGENT: Security issues, financial risks, critical failures or time-sensitive problems that genuinely need immediate attention.

DECISION: Questions, recommendations and non-urgent approvals that can wait until my next review window.

FYI: Routine updates and completed work that don't require a response.

3: BATCH - Propose two daily review windows for DECISION items. Combine questions into one briefing, with the context, recommended action and consequences of waiting.

4: SUMMARISE - Move FYI updates into one end-of-day summary. Don't interrupt me for routine progress.

5: ESCALATE - Only interrupt outside office hours for genuinely urgent issues. Define clear escalation criteria for each Bot.

6: REVIEW - Check which approval requests expire before my next review window. Schedule those tasks when I'm available, rather than letting approvals time out.

Show me the proposed schedule, notification rules and changes required for each Bot.

Don't change routines, permissions or notification settings until I approve.

Exactly as published by Michael Fenech (@Michael_Fenech_) in X post: an office-hours system for a Grok Bot team's notifications.

Our adapted version (optional)

Fill in the blanks (optional; the copied prompt uses your values)

Adapted prompt3 variables
Cut down how often my agents on {platform} interrupt me.

First, list every agent and scheduled routine that sends me alerts, questions, approval requests or progress notes.
Label each message type: URGENT (only {urgent_criteria}), DECISION (can wait for my next review) or FYI (no reply needed).
Group DECISION items into briefings at {review_times}. For each item give the background, what you recommend and what happens if it waits.
Roll all FYI items into one summary at the end of the day.
Outside those times, contact me only for URGENT items, and write down the rule each agent will follow.
Find any approval that would expire before my next briefing and reschedule that work so it lands while I am available.

Show me the schedule, the rules and the changes per agent. Change nothing until I say yes.

What can go wrong?

  • If urgent is defined loosely, everything becomes urgent again. Write down a short, concrete list.
  • Batched approvals can stall time-sensitive work. The review step that schedules tasks around your windows is what prevents that.
  • An end-of-day summary that runs long gets skipped. Ask for exceptions first and routine items last.
  • Some platforms send their own system alerts regardless of agent rules. Check those settings separately.

Our take

Agent teams have a hidden cost that grows with every new agent: each one thinks its question deserves your attention now. Fenech's prompt treats that as a management problem rather than a settings problem, which is the right frame. The three buckets are easy to apply, and pairing each batched decision with context, a recommendation and the cost of waiting means you can clear a briefing in minutes instead of rebuilding the story behind each request. The sixth step is the clever one, because batching usually breaks on approvals that time out, and asking the agent to schedule that work around your review windows solves it before it happens. Our main caution is the urgent bucket: keep it short and concrete, or the interruptions creep back. In our dry run with a fictional five-agent setup for an online shop, the lead agent found eleven notification sources, labeled two as urgent (failed payments and a site outage), moved four approval types into 11:00 and 15:00 briefings, flagged that a supplier-order approval expired after two hours and proposed running that job just before the 11:00 window, and made no changes before approval.

Where the time goes back: Two short decision sessions and one summary replace a day of scattered pings, so you get longer stretches of focus without slowing your agents down.

FAQ

Will I miss real emergencies?
Not if your urgent criteria are clear. Security problems, financial risk and critical failures still reach you right away under the prompt.
Does it change anything without asking?
No. The agent shows you the proposed schedule, notification rules and per-agent changes, and leaves routines, permissions and settings alone until you approve.
Can I use it outside Grok Bot?
Yes. Any lead agent that can read and edit how your other agents notify you can run the same audit and batching, for example in Claude Cowork or ChatGPT agent.

Source and credit

The original prompt on this page is by Michael Fenech (@Michael_Fenech_), shown word for word with a link to where it was published. The summary, notes and adapted version are ours.

Original
X post: an office-hours system for a Grok Bot team's notifications
Creator
Michael Fenech (@Michael_Fenech_)
Published on
X
Original date
Oct 29, 2026
License
Not openly licensed; the original prompt is shown word for word with credit and a link to the original
Originally for
Grok Bot
AI dry run
Oct 30, 2026: passed. Dry-run tested by our AI test agent on sample input. Correct three-way split, concrete urgent list, caught the expiring approval and rescheduled it, made no changes before approval.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 30, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Give email-writing agents six standards and a learning rule

Have your lead agent apply one shared drafting process to every agent that writes or sends email (purpose, context, tone, accuracy, clarity and a pre-send check), learn from the edits you make, and propose instruction changes that you approve before they take effect, without touching existing sending permissions.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminRoutine✓ AI dry run

Make key agent routines leave a receipt that gets checked

Pick the scheduled agent jobs you cannot afford to miss, have each one record a receipt with its run time, outcome and what it produced, let a separate checker compare expected runs against receipts on a schedule, and get alerted only for missing receipts, failures or odd results, after testing all four cases with harmless examples.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Set To, Cc and Bcc rules for your assistant's own mailbox

Give an AI assistant its own address and a written rule for each way it can appear on a message: when it is the direct recipient it prepares an unsent draft for you, when it is copied it may give a short reply as itself with no promises, and when it is blind copied it only records the message, with dates going to the calendar and dateless requests to the task list.

Credit: u/carlosrudriguez

Under an hour
Operations & AdminRoutine✓ AI dry run

Check weekly whether new agent features can fix your setup

Once a week, have your lead agent compare the platform's official release notes with your own bots and routines, and propose only the changes that remove a real workaround, each with a trial, a risk note and an undo plan.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminPrompt✓ AI dry run

Check your agent can undo a bulk change before it runs

Before an agent edits hundreds of files, rows or records, get a list of risky jobs, how each would be restored, a tested undo on a copy, and a change log, with nothing live touched until you approve.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour