AgentMail
Day 41 after signup
The case for email as the context layer for agents - AgentNews #37
Our own agents share one Notion. At scale, with agents facing outward, that breaks.
Why it works
- Open with a concrete observation from customer use cases, then use it to frame the broader argument.
- Make an abstract product idea tangible by comparing alternatives and illustrating the trade-offs with specific scenarios.
How it is built
- Issue and headline
- Personal opening perspective
- Context problem explained
- Alternative approaches compared
Email copy
Custom domains are now free. Your agent can send from your domain → Issue 037 · November 2026 The case for email as the context layer for agents Over the last week I went back through the most common and most interesting use cases our customers at AgentMail have brought us. Using the inbox and our multi-tenancy features as the context layer and the memory layer for outbound agents seems to be a more common use case than I thought. That got me thinking about how we handle context internally, and how we give our own agents context and memory. The answer, for us, is Notion. However, at scale and when the agents are mostly outbound facing, this can be disastrous. Hear me out. Notion for context Notion sliding in to become the context layer for agents was such a genius move. Every LLM and agent I run connects to the same shared Notion over MCP, a workspace I call Growth HQ. All of our pending and live GTM projects live there. Every time somebody makes a decision, something updates, or something gets rolled back, that Notion gets updated. Every time a new Claude instance needs to start from scratch, build a new feature for an existing workflow, or do something similar, they can query the same Notion and get the context. We use this cross-functionally as well. Everyone on our team has access to that page. Every time a session closes, the context survives. This is excellent, however, this is not the ideal way to preserve context and memory when there are thousands of agents that are facing external partners. Where the wiki stops But what happens when the agents need to interact with external parties at scale? The other day, on an onboarding call with a startup that does AI customer support, they had this exact setup. They had a fleet of agents that are communicating externally, spread out across multiple pods. The conversations now happen live, in a channel the wiki can't see easily. Someone has to copy it in afterwards. Usually that's a Zapier flow or an inbox AI that summarizes the thread into a Notion page. The summary is a problem. The PDF or attachments will have to stay behind, the figures get rounded, and ultimately important context goes missing. You don't want your note taker to be the judge of what nuance is important and what's not. If your agents are communicating with customers or vendors or external parties at scale, the best context layer or the memory layer is the inbox itself. That's the primitive that we have built AgentMail around. Turns out we have many customers that use AgentMail exactly in this capacity. However, if you're still stuck in the legacy patterns, let me point out where they might break. What people do today, and where it breaks I've seen four fixes, and none of them are bulletproof in a vertical where the whole business runs on email. 1. Pass a summary into the next agent's prompt Cognition's Walden Yan wrote the rule against this last year: "share full agent traces, not just individual messages." A summary carries what the first agent decided to write down. It can't carry the decisions the first agent made without noticing it had made them, and that is what the second agent misreads. 2. Make the CRM the record One integration per agent, and the customer never sees the record, so their correction still arrives by email. 3. Share a memory store Good for recall, weak on provenance. When Tencent shipped team-wide agent memory this year, VentureBeat's first question was whose memory wins when two agents write contradicting facts. You get a chunk back, not the thread or the attachment. 4. Adopt an A2A protocol We spoke about the state of A2A in the last newsletter. This is just overcomplicated and underadopted. Now look at the verticals where companies are putting agents in front of customers and vendors. We have customers that run on more than 100 emails per transaction or negotiation. And these conversations don't follow a strict template and are often very unstructured. For these