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?
- Paste the promptGive Fenech's prompt to your lead agent; it audits first and changes nothing yet.
- Check the urgent listReview what it classed as urgent and tighten or widen the criteria.
- Pick your windowsApprove two review times that fit your day, such as late morning and mid-afternoon.
- Approve the changesLet it update notification rules agent by agent once you agree with the plan.
- 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_)
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)
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?
Does it change anything without asking?
Can I use it outside Grok Bot?
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.