AgentMail
Day 27 after signup
Agents should have their own calendar - AgentNews #35
Every AgentMail inbox gets one. Here is why that matters.
Why it works
- Open with the new capability, then use a specific scheduling mishap to make the need for it concrete.
- Explain the feature through practical scenarios and technical details before ending with one clear documentation CTA.
How it is built
- Issue header
- Feature headline
- Personal scheduling story
- Case for agent calendars
Email copy
Every AgentMail inbox now comes with its own calendar → Issue 035 · October 2026 Agents should have their own calendar Yesterday, I saw a YouTube ad from a different provider that said "AgentMail does not have a calendar, and we do." That is a lie. Every AgentMail inbox gets its own calendar. You don't have to do anything new. When you create an inbox, the calendar gets created with it. Today I wanted to write about why agents need a calendar in the first place. Let me walk you through a real scenario that happened last week. I have an in-house-built sales agent called Jordan that interacts with leads before calls. It books a demo with a prospect and sends them a custom quote 30 minutes before the call. Last Wednesday, one of the prospects moved the call to Friday. But Jordan sent the quote 30 minutes before the previous time. If Jordan had a calendar, it would have probably not done that and sent the invite at the right time. More on this later. Why an agent needs one Agents can already schedule reminders and book calls. But a reminder is often a timer the agent sets for itself, while something like a meeting belongs to other people too, and they can move it without the reminder being notified. You could connect the two things yourself by parsing calendar updates, expanding recurring events, converting time zones, and basically running a scheduler app. But that's a service you'd have to actually maintain for the agent. We believe that if you're paying actual money for a personal agent, your work should be done for you, and not the other way around. You shouldn't have to lay down any groundwork. Something as basic as managing a calendar should be built into agent infra. Most of what an agent agrees to, like a demo or a renewal call, gets agreed in email. The calendar gives each of those a start and end time the agent can act on. Read yours, write its own Usually, what happens is you give the agent read and write access to your personal calendar, so it will see calls that you have with lawyers or one-on-ones where you talk about letting someone go (basically, calls that the agent or anybody else probably should not see). Your agent does not need to know when you're free and what you're up to at all times. This is where the "share free/busy only" feature Google and Outlook provide comes into play. The agents will be able to see that 2 to 3 pm is taken, but not what the call is about. Everything it books goes into its own calendar with you invited, so you can accept or decline. Agents as AI employees When a new employee joins a company, the first thing that happens is that IT gives them a new email address and the rest of the Google Suite products, including a calendar and a drive folder. That's often treated as the basic access layer for an employee. We believe that agents should start the same way. Agents should have the same access to the same infrastructure that we already have in order to become the best employee they can. That starts with email and a calendar, cheap enough that every agent you run can get them. We started with email, added accounts at other apps through AgentID, and now it has the calendar. The future is A2A The not-so-distant future will be full of agents working together with you on the sidelines. This is a good thing. You can probably think of many different things you'd rather have somebody else manage for you. This includes scheduling and coordinating with third parties such as vendors. Say your agent is booking a demo with a prospect, and the prospect has their own agent handling their schedule. Your agent emails that agent two times that work. Their agent picks Thursday at 3. Your agent sends the invite to that agent's address, it accepts, and the demo lands on both calendars. If the prospect later moves it to Friday, their agent updates the invite and your agent's calendar moves with it. Neither company built an integration with the other. Each agent only needed an email addre