Compare

Ways to give an agent email

There are five common ways to put an artificial intelligence (AI) agent on email today. Each solves part of the problem. Here's how they compare with what Envolt Mail is designed to do.

This compares the usual shape of each approach, not any particular product. Products differ, and many can be extended. Envolt Mail's column shows its design, with what runs today on the status page.

What mattersShared inbox passwordMailbox APITransactional email serviceAgent inbox APIInbox assistantEnvolt Mail
Recipients can tell an agent wrote itShared inbox password No, it looks like a personMailbox API Only if you add itTransactional email service If you write it into templatesAgent inbox API VariesInbox assistant No, it writes as youEnvolt Mail Always: label, disclosure, seal
Anyone can verify which agent sent itShared inbox password NoMailbox API NoTransactional email service Domain only (DKIM)Agent inbox API Domain only, usuallyInbox assistant NoEnvolt Mail Signed per agent (Agent Seal)
Agent needs a person's OK to sendShared inbox password No, it holds the passwordMailbox API No, it holds the tokenTransactional email service No, it holds the API keyAgent inbox API Usually not by defaultInbox assistant Most only draft; some send by rules you setEnvolt Mail Yes, until it earns routine sends
Hidden instructions removed before the model readsShared inbox password NoMailbox API NoTransactional email service Not applicable (outbound)Agent inbox API VariesInbox assistant VariesEnvolt Mail Yes, in the Airlock
Tamper-evident record of every actionShared inbox password NoMailbox API Provider logsTransactional email service Delivery logsAgent inbox API VariesInbox assistant An activity historyEnvolt Mail Hash-chained, anchored ledger
Stays out of your people's mail pathShared inbox password No, it is your people's inboxMailbox API YesTransactional email service YesAgent inbox API YesInbox assistant Yes, it connects to your mailboxEnvolt Mail Yes, by rule
Separate identities for a studio, a pen name and each projectShared inbox password NoMailbox API One per mailboxTransactional email service By sender addressAgent inbox API One per inboxInbox assistant One per connected mailboxEnvolt Mail Persona rooms that never cross

Drafts for you, or acts under policy

Inbox assistants and Envolt Mail solve different problems. An assistant sits in your own mailbox and writes as you: it sorts, summarizes and drafts, and you press send. That works well while one person reads everything.

Envolt Mail is for mail an agent handles in its own name. The agent has its own address and says what it is. A policy your team owns judges every message before it can leave, a person approves until a narrow kind of reply has earned routine sends, and each send leaves a public receipt. The question it answers is who is accountable when no person pressed send.

When something else is the better fit

Building agents that need email?

Tell us what your agents do. We'll reach out as early access opens.

Request early access