# Give your Grok Bots office hours so questions wait for a briefing instead of interrupting you > A builder shared a prompt for a Chief of Staff bot that sorts every bot notification into urgent, decision and FYI, batches decisions into two daily review windows, rolls FYI into one end-of-day summary, and flags approvals that would expire before the next window. - URL: https://paperchasewebb.ai/bots/marketplace/items/give-your-grok-bots-office-hours-so-questions-wait-for-a-briefing-instead-of-interrupting-you/ - Type: Agent use case pack - Category: Solo business - By: PaperChaseWebb - Works with: Grok Bot (named in the listing); Plain .md - Price: Free USD - Difficulty: Beginner - Setup time: 15 min - Time to result: One working session - Format: Markdown (.md) file, give-your-grok-bots-office-hours-so-questions-wait-for-a-briefing-instead-of-interrupting-you.md - Version: 1.0, updated 2026-10-30 - License: Personal and commercial use. Credit the original source when you share the workflow. ## What you end up with The step people skip is the expiry check: batching approvals is only safe if nothing time-sensitive quietly expires while it waits. ## What you get - A plain-language summary of the workflow - A fill-in prompt template - What to watch out for - A link to the original source ## Who it is for Builders who already use AI agents and want a proven workflow they can copy into their own project. ## Tools needed - Grok Bot: a Chief of Staff bot that audits and reroutes the team's notifications - The owner: reviews decisions twice a day and approves the new rules - You need: An AI coding agent or chat model - You need: A small real task to try it on Cost to run: Free with the agent plan you already use. ## How it works 1. **Have one bot list every bot and routine that sends you questions, appr.** Have one bot list every bot and routine that sends you questions, approvals or updates. Expected: Done before you move to the next step. 2. **Sort each into urgent, decision or FYI, and write what counts as urgen.** Sort each into urgent, decision or FYI, and write what counts as urgent for each bot. Expected: Done before you move to the next step. 3. **Pick two daily review windows and merge decisions into one briefing wi.** Pick two daily review windows and merge decisions into one briefing with context, a recommendation and the cost of waiting. Expected: Done before you move to the next step. 4. **Roll FYI updates into a single end-of-day summary.** Roll FYI updates into a single end-of-day summary. Expected: Done before you move to the next step. 5. **Flag approvals that expire before the next window and schedule that wo.** Flag approvals that expire before the next window and schedule that work for when you are available. Expected: Done before you move to the next step. 6. **Change no routine or notification setting until you approve the plan.** Change no routine or notification setting until you approve the plan. Expected: Done before you move to the next step. ## Sample prompt: Workflow template (Grok Bot, The owner) ``` Apply this workflow to [your project]: 1. Have one bot list every bot and routine that sends you questions, approvals or updates. 2. Sort each into urgent, decision or FYI, and write what counts as urgent for each bot. 3. Pick two daily review windows and merge decisions into one briefing with context, a recommendation and the cost of waiting. 4. Roll FYI updates into a single end-of-day summary. 5. Flag approvals that expire before the next window and schedule that work for when you are available. 6. Change no routine or notification setting until you approve the plan. Stop and ask me before anything irreversible: deploys, payments, sends or deletes. ``` Adapted by PaperChaseWebb. Not the original author's prompt. ## Free preview of give-your-grok-bots-office-hours-so-questions-wait-for-a-briefing-instead-of-interrupting-you.md ````markdown # Give your Grok Bots office hours so questions wait for a briefing instead of interrupting you PaperChase agent use case (free feed entry), version 1.0. Source: [Michael Fenech (@Michael_Fenech_)](https://x.com/Michael_Fenech_/status/2115884875844624558), 2026-10-29. ## What they did He asks the Chief of Staff bot to list every bot and routine that pings him, sort each message type into urgent, decision or FYI, and propose two daily review windows. Decisions arrive as one briefing with context, a recommended action and the cost of waiting. FYI items go into an end-of-day summary. Each bot gets written escalation rules for what may interrupt outside office hours, and the bot checks which approvals would time out before the next window so that work is scheduled when he is around. Nothing changes until he approves the plan. ## Worth knowing The step people skip is the expiry check: batching approvals is only safe if nothing time-sensitive quietly expires while it waits. Keep security, money and outage alerts in the urgent lane no matter what the schedule says. ```` ## Worth knowing - The step people skip is the expiry check: batching approvals is only safe if nothing time-sensitive quietly expires while it waits. Keep security, money and outage alerts in the urgent lane no matter what the schedule says. - Figures are as reported by the original author and were not re-measured by us. ## Questions **Where does this come from?** A public post credited to Michael Fenech (@Michael_Fenech_). Source: https://x.com/Michael_Fenech_/status/2115884875844624558 **Is it free?** Yes. Feed entries are free to read and download. ## How to get it Free sample. Download it directly at https://paperchasewebb.ai/bots/marketplace/items/give-your-grok-bots-office-hours-so-questions-wait-for-a-briefing-instead-of-interrupting-you/, no signup. Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com