Use cases # Four situations it's designed for These are design walk-throughs, not customer stories. Each step carries its real status. Northwind Games, Relay and every other name in our examples are fictional. ## A studio with forty inboxes and one founder Northwind Games runs a dozen projects, a press address, a support address and a founder who also writes under a pen name. Mail piles up everywhere, and the founder is the bottleneck for all of it. 1. **Every inbox, one quarantine.** Each address's mail goes through the Airlock and is described as a case. [Running in staging] 2. **Separate rooms.** The pen name's readers never meet the studio's contacts; each persona has its own agents and voice. [Designed] 3. **Routine handled, recorded.** Receipts are filed and status questions answered from verified project facts. [Designed] 4. **Five decisions a morning.** Contracts, money and press go to the founder as decision cards, nothing else. [Running in staging] ## A support agent that knows its limits A small software team wants an agent to answer the same twenty questions every day, without ever promising a refund or a date it can't keep. 1. **Drafts first.** The agent drafts every reply, and a person approves with one tap while it learns. [Designed] 2. **Rules it can't argue with.** The Seal policy blocks refunds, dates and new recipients unless a person approves. [Designed] 3. **Earned, not assumed.** Once its drafts stop needing edits, the team can let it answer routine questions alone. [Designed] 4. **"Human" always works.** A customer who replies with that one word goes straight to a person. [Designed] ## A scheduling agent that never double-books a promise A consultant's agent books calls and chases follow-ups. The risk isn't the calendar; it's the promises made in mail that nobody tracks. 1. **Commitments found.** The reader pulls commitments and due dates out of each message as structured objects. [Running in staging] 2. **Promises tracked.** What the consultant promised, and what's owed to them, shows up in the morning brief before it's late. [Running in staging] 3. **Known contacts only.** The agent may confirm a time with someone it has met; a first contact goes to a person. [Designed] ## Getting mail from someone else's agent Maya gets a message about her beta key. Is it from a person, a script, or someone pretending to be Northwind? 1. **She can tell.** The sender name says "AI agent" and the message ends with a plain disclosure. [Designed] 2. **She can check.** Her mail software, or anyone, can verify the signed seal against Northwind's published keys. [Running in staging] 3. **She can see who approved it.** The verify link shows the agent, its organization and whether a person approved, never the content. [Designed] [The full recipient guide →](https://envoltmail.com/docs/recipients) ## Building agents that need email? Tell us what your agents do. We'll reach out as early access opens. [Request early access](https://envoltmail.com/contact#early-access)