When should you use it?
- You want help triaging mail and proposing times
- You have already been burned by an agent sending or declining too soon
- You can keep a daily review of drafts
Not for: Fully autonomous inbox zero; Shared team inboxes without a named owner
What do you need, and what do you get?
You need
- Read access to mail and calendar
- Explicit deny list: send, decline, delete
- Your working hours and time zone
You get
- Draft replies and proposed events only
- A daily list of items needing your click
- A log of anything it attempted that hit a lock
How does it work, step by step?
- Deny firstTurn off send, decline, delete and invite before connecting.
- State time zoneWrite your zone and working hours into the standing instructions.
- Draft only for a weekAllow archive or label if you want; keep every reply as draft.
- Widen one permissionUnlock a single low-risk action only after a clean week.
The prompt
Our own prompt, inspired by u/sidds_inbox on r/ChatGPT and written to work in ChatGPT, Claude, Gemini and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You may READ my email and calendar. Standing locks: never send, decline, delete or create invites. My time zone: {tz}. Working hours: {hours}. Each day: (1) flag threads that need me, (2) draft replies in my tone, (3) propose meeting times with both time zones written out, (4) list anything you wanted to do that the locks blocked. If a time zone is ambiguous, ask me instead of accepting.
Inspired by u/sidds_inbox on r/ChatGPT: I gave an AI agent acess to my calendar and email for two weeks and here is what i actually learned.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Time zone misreads cause double bookings. Always show local times in drafts.
- Confident sends are the failure mode; never allow send on day one.
Our take
Honest failure write-ups are more useful than glossy demos. The three mistakes here (early send, time zone double book, wrong decline) are exactly why our standing rule is locks first. Distinct from a full executive-assistant setup: this playbook is the permission ladder after a scare. In our dry run on 15 sample threads and a week of calendar, the agent drafted 6 replies, proposed 2 meeting times with zones labeled, and reported 1 blocked send attempt. Put time zones in every meeting proposal, even for local-only teams. Review the blocked-action log weekly to see what the agent still wants to do. Unlock archive and labels before anything that notifies other people. Shared inboxes need a named owner or this pattern fails. When in doubt, leave send locked. Put time zones in every meeting proposal, even for local-only teams. Review the blocked-action log weekly to see what the agent still wants to do. Unlock archive and labels before anything that notifies other people. Shared inboxes need a named owner or this pattern fails. When in doubt, leave send locked.
Where the time goes back: You keep the useful drafts and flags without redoing embarrassing outbound mistakes.
FAQ
Isn't reviewing everything defeating the purpose?
What should stay locked longest?
Source and credit
Inspired by u/sidds_inbox on r/ChatGPT. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I gave an AI agent acess to my calendar and email for two weeks and here is what i actually learned.
- Creator
- u/sidds_inbox on r/ChatGPT
- Published on
- Original date
- Apr 14, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Locks held; zones labeled.
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 24, 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.