build.allanninal.dev

Part 2 of 7 · Email assistant series ~4 min read

How an email enters the assistant

Not every email deserves the brain. Newsletters, “your package shipped” receipts, and DMARC reports should be filed silently. VIPs should reach you without an AI in the way. Everything else gets the assistant. Three lanes at the door.

Inbound routing: three lanes before the brain runs A vertical flow. At the top, a single envelope marked “Inbound email” representing every message that arrives at the business address. Below it, a Receiver box labeled “SES inbound, lands in S3.” An arrow leads down to a diamond-style decision point: “Sender, headers, address.” From the decision point, three labeled lanes branch out. Left: “Auto-archive” for noreply addresses, list-unsubscribe headers, and DMARC reports — the email is logged and stored, no reply is sent, no human is notified. Centre: “AI handle” for normal business mail — passed to the brain. Right: “Direct escalate” for senders on the allowlist (existing customers, partners, the operator’s personal address book) — the email skips the brain and lands in the human inbox right away. A bottom note reads: by the time the brain runs, the noise is gone and the VIPs are already through. Inbound email to your address Receiver SES inbound, raw mail dropped to S3 Sender, headers, address classify before any AI runs noreply, list-unsubscribe normal mail on the allowlist Auto-archive log to audit table, store the raw mail, no reply, no ping. newsletters, receipts, delivery reports AI handle pass to the brain, one of four moves per email. questions, requests, cold outreach Direct escalate forward straight to the human inbox, untouched. existing customers, partners, family By the time the brain runs, the noise is gone and the VIPs are already through.
Fig 2. Three lanes at the door. The brain only sees mail that’s actually for it.

Why route before you read

It’s tempting to send every email to the brain and let the AI sort it out. Don’t. Two reasons.

First, cost. A typical small-business inbox is half noise — receipts, newsletters, calendar invites, unsubscribe-style mass mail, vendor pings. Running each of those through a language model is paying for thinking you don’t need. Cheap rules at the door drop most of it before any AI runs.

Second, trust. Some senders should never be answered by an AI. A long-time customer asking about their order, a partner pinging you about a contract, a friend emailing the business address — if the assistant replies to those, you’ve damaged a relationship to save a minute. The allowlist sends those straight to your inbox.

Lane 1 — Auto-archive

The first thing the receiver checks is whether this email even wants a reply. Three signals usually answer that:

  • The sender is a noreply address. noreply@, no-reply@, donotreply@, mailer-daemon@ — the sender is telling you, in their address, not to write back.
  • The email has a List-Unsubscribe header. A standards-compliant signal that this is bulk mail, not personal correspondence.
  • The email is a delivery or auth report. DMARC reports, bounce notifications, calendar invites with auto-handle headers.

If any of those match, the email goes to the auto-archive lane. The raw message is stored in S3, a row is written to the audit table, and the lane ends. No reply, no notification. If you ever need to look back — “did the package-tracking email come in?” — you can; the data is there. But it doesn’t live in your inbox.

Lane 2 — AI handle

The default. Anything that isn’t obviously noise and isn’t obviously a VIP goes to the brain. This is where the work happens, and it’s the subject of the next three posts: how the reader cleans the message, how the brain picks one of four moves, and how a reply stays accurate.

The receiver does one more thing before passing the email through: it stores the raw mail in S3 and writes a small “message envelope” record — sender, subject, timestamp, message ID, threading headers — into a small DynamoDB table. The brain reads from that envelope; the raw mail stays in S3. This separation matters when the assistant has to send a reply that threads correctly, weeks later, against an old message.

Lane 3 — Direct escalate

The allowlist. A short list of email addresses, domains, or patterns that always skip the AI. Examples that usually belong on it:

  • The personal addresses of your most important clients.
  • Domains of partners or vendors you’re actively working with.
  • Anything from your own staff’s personal addresses.
  • Anything that arrives in reply to a thread a human already started.

For senders on the list, the receiver forwards the message to your normal inbox unchanged, with a small header tag (X-Assistant-Lane: direct) so you know it bypassed the AI. The thread stays intact, the sender notices nothing, and you stay in the loop on the relationships that matter most.

In plain words

Most of what hits a business inbox doesn’t need an AI to handle, and some of it shouldn’t. Three short rules at the door — archive the obvious noise, escalate the people you always want to see, send the rest to the brain — mean the AI only ever runs on what it’s actually good at.

All posts