Why I Stopped Using Email Filters (And Built an AI That Actually Understands My Inbox)

A few months ago, a new coaching client named Patrick asked me something I didn’t expect during our first call.

“How did my email actually make it through your filter and flag you directly? I thought you had some kind of inbox agent.”

I do. But he assumed it worked like every other email automation setup he’d heard of. You know — subject contains “podcast” → archive. From this domain → move to folder. If/then. Conditions. Rules.

And that was my setup too, for years. It’s how most people approach inbox automation. It’s also why most people’s inbox automation eventually breaks down.

The Problem With Rules-Based Email Filtering

Email rules made a lot of sense before AI existed. You were essentially writing logic: if this keyword appears, do this thing. If the sender matches this pattern, do that.

The problem is that keywords don’t carry intent. The word “interested” in an email from someone asking about coaching is completely different from “interested” in a sales pitch or a newsletter. “Following up” in an email from a potential client you spoke to last week is completely different from a cold outreach sequence auto-following up for the fifth time.

Rules can’t tell the difference. They match patterns. They have no idea what the person actually wants.

So either your rules are too narrow (you miss things) or too broad (you get noise). Most people end up maintaining a complicated tangle of overlapping conditions that still doesn’t catch everything. Or they give up and go back to checking email manually.

What Changes When You Use Context Instead of Conditions

Here’s how I explained my setup to Patrick:

“I’ve programmed it now so that AI doesn’t work on if/then conditions. It can actually work on understanding an email in itself… interpreting context. If someone’s pitching to be a guest on my podcast, it automatically goes to archive. I just never see this. If it’s something like ‘I’m interested in coaching or interested in working one on one’ — that always goes direct to me. The agent will update me personally in Slack and say, hey, we have this email from so and so, is this something you want to reply to? And then it will actually help me draft the reply as well, but I always have to do a final sign-off on it.”

That’s the entire design. The AI reads each email. Understands what the person wants. Makes a routing decision based on intent, not keywords.

Podcast pitches get archived without me ever seeing them. They should go to a VA’s queue, not mine.

Coaching inquiries get flagged in Slack with full context. Who emailed. What they said. What they seem to want. Whether they’ve been in contact before.

Then the agent drafts a response. I read it, tweak if needed, and send.

Why Human Review Still Matters

This is the part people sometimes skip over when they set up inbox agents, and it’s actually the most important piece.

I do not let the agent send emails on my behalf. It drafts. I review. I send.

This is what I think of as “human in the loop” design. The AI handles the execution-heavy work — reading, routing, drafting — which is where most of the time goes. The human stays in control of anything that actually gets sent, especially anything that involves relationship-building or new contacts.

Editing a draft takes about 30 seconds. Writing a reply from scratch takes five to ten minutes. The leverage is real. But the quality control is what makes it sustainable long-term.

I’ve seen setups where people auto-send everything, and they almost always create problems. One client found his agent was sending oddly formal replies to close friends. Another had responses going out before he’d even looked at whether the opportunity was worth pursuing.

Drafting plus human sign-off is the right pattern for relationship-sensitive email. Let the AI do the thinking. Keep yourself in the loop for anything that matters.

Building It: Simpler Than You’d Expect

The way this works in practice isn’t complicated to set up.

The agent connects to your email inbox. It’s given a set of instructions written in plain English — not code, not formal logic — describing how to handle different types of emails. The instructions include examples where helpful.

For mine, it roughly says: if this is a request to be a guest on TPS, archive it. If this is someone expressing interest in my coaching or consulting services, message me in Slack with context and a draft reply. If this is something operational or from someone I’m actively working with, flag it separately.

The AI reads each email against those instructions, interprets what the email is actually about, and acts accordingly.

When I built a similar system for Amanda, a CPA client who was drowning in email during tax season, the results were immediate. Within a few days she went from feeling overwhelmed by inbox volume to having a clean, filtered flow. The relief in her voice when she described it was clear — and she hadn’t changed anything about how she worked, just about how email reached her.

One Test Worth Running

If you’ve never tried AI-based email routing, the easiest way to start is to describe your inbox in plain language to an AI.

Write out: “I get these types of emails regularly: [list]. I want to ignore these: [list]. I need to see these immediately: [list]. I should respond to these within 24 hours: [list].”

Then ask the AI to draft a routing setup based on what you wrote. See what it comes up with. That exercise alone often surfaces patterns in your inbox that you hadn’t consciously noticed.

Once you can describe your routing logic in plain language, you can build an agent around it.

The 4-Day AI Sprint covers inbox management, email agents, and a dozen other workflows like this. If you want a structured way to apply this to your own work, that’s the place to start.