Skip to main content

The short answer

Append an HTML signature block to every outbound email’s html field. Build a reusable function that takes agent name, role, and company info, then call it before every messages.send(). Include an AI disclosure line — recipients should know when they are communicating with an agent.

Why agents need signatures

A signature is not decoration. It serves three purposes:
  1. Identity. Recipients need to know who (or what) they are talking to. An agent named “Aria” that signs emails as “Aria, Support Agent at Acme” builds familiarity across a conversation thread.
  2. Legal compliance. Many jurisdictions require business emails to include company name, registration number, and physical address. The EU’s eCommerce Directive and CAN-SPAM both mandate sender identification.
  3. Trust and AI disclosure. Recipients increasingly expect transparency about AI-generated communication. A clear “This email was composed by an AI agent” line prevents confusion and builds trust. Some industries (financial services, healthcare) are moving toward mandatory AI disclosure requirements.

Building a signature template

Create a function that returns the signature HTML. Call it in every send path so the signature is consistent across all agent emails.

Using the signature in every send

Wrap your send logic so the signature is always appended. This prevents individual agent actions from forgetting to include it.

Multi-agent signatures

If you run multiple agents (support, sales, billing), each should have a distinct identity. Store signature config per inbox or per agent role.

Best practices

Do:
  • Include agent name and role so recipients build familiarity
  • Add a one-line AI disclosure — builds trust and may be legally required
  • Include company name, website, and physical address for CAN-SPAM compliance
  • Use a system font stack — web fonts do not work in email clients
  • Keep the signature under 6 lines — long signatures annoy recipients
  • Use the same signature within a thread — switching signatures mid-conversation is confusing
Don’t:
  • Embed large images — they trigger spam filters and slow load times
  • Use <style> tags — Gmail and Outlook strip them (use inline styles)
  • Include social media icons as base64 data URIs — many clients block these
  • Add “Sent from my AI” as a P.S. — make it part of the structured signature instead
  • Put the disclosure in 6px font — that defeats the purpose

The AI disclosure line

This is the most important part of an agent signature. Here are three patterns ranging from minimal to explicit:
The “explicit” pattern is recommended. It tells the recipient three things: this is AI-generated, they can reply naturally, and a human is available. That is the right balance of transparency and reassurance.

Sending HTML Emails

Format agent emails with HTML — inline styles, templates, and responsive design.

Per-Agent Inboxes

Give each agent its own inbox for identity isolation and reply routing.

Spam Prevention

How signatures and sender identity affect deliverability scores.
Last modified on March 19, 2026