📬 AI Controls My Inbox: First Review After 72 Hours
So, was it perfect?
Nope.
Did I miss anything critical?
Two emails.
Fortunately, one person texted me, and the other email my wife asked if I saw it - so, there was no major negative impact.
But that is exactly why I am doing this experiment.
I do not want to know if AI can manage my inbox when everything goes perfectly. I want to know where the cracks show up when I am not looking every day.
Here is what I learned after the first 72-hour cycle.
📝 Lesson one: the first cycle had a built-in advantage.
Because I was already familiar with the current state of my inbox, I knew what I expected to see. I had a mental map of open conversations, active deals, pending follow-ups, and emails that might matter.
That made the first review easier, but that advantage starts to disappear in the next cycle or two. Once I stop carrying the recent inbox context in my own head, the system has to stand on its own.
That is when the real test begins.
📝 Lesson two: prompts matter.
📝 Lesson three: prompts matter even more.
Yes, this experiment is quickly becoming a lesson in prompt design. Even though I did not open my inbox during the 72-hour window, I did adjust the prompts based on what I expected to come in and what was getting through that should not have been.
  • Some spam and promotions still surfaced.
  • Some categories needed tighter language.
  • Some escalation rules needed more clarity.
That does not mean the system failed.
It means the operating instructions needed refinement.
And that is probably the biggest early takeaway. AI inbox management is not a set-it-and-forget-it system. At least not yet. It is more like training an operations assistant.
You give it a role.
You define the boundaries.
You observe the misses.
You tighten the rules.
Then you run the next cycle.
📝 Final lesson: redundancy matters.
At this stage, built-in redundancy has real benefits.
For this experiment, I used three AI layers:
  • Claude Cowork
  • ChatGPT Scheduler
  • Gmail AI Inbox
That gave me a way to compare what each platform noticed, what each one missed, and how each system interpreted importance.
It also created a form of A/B testing. If one platform missed something, another might catch it.
Anecdotally, that reduced the likelihood of missing something important.
This is not proof that redundancy solves the problem. But it does suggest that, at this stage, relying on a single AI system to manage a mixed personal and business inbox may be too fragile.
Multiple AI layers create comparison, backup, and confidence.
They also expose differences in judgment.
That may end up being one of the most valuable parts of the experiment.
The goal is not perfection on day one.
The goal is learning whether the system gets better with each 72-hour review.
First cycle complete.
Not perfect.
Not a disaster.
Useful enough to keep going.
9
41 comments
Michael Wacht
7
📬 AI Controls My Inbox: First Review After 72 Hours
AI Bits and Pieces
skool.com/ai-bits-and-pieces
AI lessons you can read in under 3 minutes and apply in everyday work and life.
Leaderboard (30-day)
Powered by