AI Identification in Email

Every email an agent sends says clearly that it was written by AI, and who is responsible for it

When an agent sends, replies to, or forwards an email on your behalf, Operator automatically adds AI identification. You don't configure anything — it applies to all agents, all mailboxes, and both Microsoft 365 and Gmail.

What recipients see

A short disclosure line at the top of the message and a footer with a verification link. For example:

Sent by Anna, an AI assistant acting for Ivan Petrov. This message was generated by AI.

…the agent's message…

AI-generated by Operator.net · Verify: https://operator.net/provenance/01JB…

The sender is never presented as a person

An agent never sends as plain Ivan Petrov. The sender is always shown as an AI identity:

When you use a user-defined agent, its own name is shown. The built-in agent name is used only as a fallback when no user-defined name exists.

Replies go to the responsible person's address, so recipients still reach a human.

Microsoft 365 note: Microsoft always shows the mailbox owner's own name as the sender, and this cannot be overridden. For those mailboxes, the disclosure line at the top of the message carries the AI identification instead.

What machines see

Alongside the visible text, each message carries machine-readable identification so mail clients, filters, and compliance tools can detect AI-generated mail:

Longer messages (over 200 characters) also carry an invisible watermark that survives copy-paste.

Verification

Every message gets its own provenance record, cryptographically signed by Operator. Anyone can open the verification link in the footer to confirm:

The record never exposes the message content, subject, or recipients — only a fingerprint that proves the text hasn't been altered.

Why this exists

The EU AI Act requires that people are told when they're interacting with AI-generated content. Beyond compliance, it's a trust boundary: an autonomous agent acting for someone is never the same as being that person, and Operator enforces that distinction at the platform level.