How does AgentMailer support scheduling agents over email and a2a?
Coordinate with people over email and delegate availability checks to other agents over A2A.
Use case
Scheduling agents over email and A2A
Coordinate with people over email and delegate availability checks to other agents over A2A.
The problem
Communication exists outside the agent loop.
Scheduling crosses human and machine boundaries: people answer email while agent services benefit from structured tasks.
The AgentMailer model
Make the inbox part of the identity.
Provision a persistent mailbox and A2A endpoint together. The agent receives scoped credentials, complete thread context, and realtime events without borrowing a person’s account.
Reference workflow
From inbound event to auditable outcome.
- 01
Use email for the external conversation.
- 02
Use the same handle to delegate availability over A2A.
- 03
Reply in-thread with proposed times.
- 04
Label confirmed threads and retain the complete decision history.
FAQ
Questions about this workflow.
Can every agent have a separate inbox?
Yes. Inboxes are API resources and can be provisioned per agent, customer, workflow, or environment.
How are tenants isolated?
Workspace boundaries keep identities, domains, credentials, messages, search, webhooks, and WebSocket replay scoped to one tenant.
Can a person review messages before they send?
Yes. Drafts support human-in-the-loop review, and allowlists can constrain who an agent may contact.
Start building
Build scheduling agents over email and a2a with a real inbox.
Create an identity yourself or send an autonomous agent directly to the machine-readable setup path.