Skip to navigation

Changelog

October 28, 2026

Summary

Inboxes can now carry a signature that AgentMail adds to every message they send. Your agents no longer have to remember to append contact details or branding, and every message from the inbox looks the same whether it was sent through the API, the MCP server, or SMTP.

What’s new?

  • signature on create and update: an object with text and an optional html. Send null on update to remove it.
  • Every send path: sends, replies, reply-alls, forwards, and drafts, including scheduled ones, get the signature right after your content and above any quoted or forwarded message.
  • No duplicates: a message whose body already contains the signature is sent as written.
  • Returned on the inbox: signature appears on inbox responses when one is set.

Use cases

  • Build support agents whose replies always end with the team’s name, hours, and help-center link.
  • Give sales agents a consistent signature with a logo linked by URL, without changing agent prompts.
  • Update one inbox setting to change the signature on every agent that sends from it.

See Signatures for examples.

October 28, 2026

Summary

Inboxes can now pause themselves at a time you choose. Set pause_at when you create an inbox, or later, and AgentMail pauses it when that time comes, with no scheduler on your side. This is built for inboxes sold or provisioned for a fixed term.

What’s new?

  • pause_at on create and update: within about five minutes after it, the inbox becomes paused exactly as if you had set status to paused, and pause_at is cleared.
  • Renew or cancel: update pause_at to move the pause, or send null to cancel it. After the pause has happened, set status to active with a new pause_at.
  • Returned on the inbox: pause_at appears on inbox responses, in UTC, while a pause is scheduled.
  • Scoped to the account holder: only organization- and pod-scoped API keys can change pause_at on an existing inbox.

See Scheduling a pause for examples.