# 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.

## Workflow template

```text
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.
```

## Steps

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.
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.
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.
4. **Roll FYI updates into a single end-of-day summary.** Roll FYI updates into a single end-of-day summary.
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.
6. **Change no routine or notification setting until you approve the plan.** Change no routine or notification setting until you approve the plan.

## Credit

Workflow reported by Michael Fenech (@Michael_Fenech_): https://x.com/Michael_Fenech_/status/2115884875844624558

Summary and template written by PaperChaseWebb in our own words. Questions: mgmt@paperchasewebb.com