✉️ Agent email, end to end

Each agent can own a real inbox - sending and receiving as itself (nina@agents…, or on your own domain once connected in Settings → Email Domains). The Email screen shows every inbox unified or one at a time, with filters for Received / Sent / Unread / Drafts / Escalations / Scheduled.

Threads, not messages: conversations group into threads - every message card shows its status (Draft / Scheduled / Sent / Escalated), attachments, and quoted history you can expand. The 📎 and count pills on the list tell you what’s inside before you click.

The draft flow is the heart of it: agents write, you approve. A draft thread gives you ✓ Approve & send, an inline editor (your edits also teach the agent your voice), and Revise with [agent] to send it back with notes. Escalations are the inverse - the agent explicitly hands you something (“refund outside policy”) with a Dismiss and an Instruct path into chat.

Scheduled sends show a live countdown and a Cancel send that works until the moment it fires. Compose (✎) lets you send as any agent yourself - it counts toward that agent’s cap like everything else.

The safety stack, in order: the briefing (standing instructions per inbox - what to handle, what to escalate, what tone), allow/block rules (per agent or workspace-wide; allow beats block, exact beats domain, agent beats workspace), and the daily send cap - the hard ceiling nothing can talk its way past.

💳 Cost note: Email is a flat monthly add-on per inbox - sends and receives don’t use credits. Deliverability tip: connect your own domain and keep outreach volumes inside the playbook patterns; reputation is yours to protect.

A minimal first briefing (any inbox)

Handle: [the categories this agent owns]. Draft-for-review everything else that deserves a reply. Escalate (ticket, don’t reply): [your red lines]. Tone: [two adjectives + sign-off]. When unsure whether something is yours: it isn’t — flag it.