How it works

Doorman is not an inbox assistant. It only ever sees copies you deliberately send — forward a thread, CC it on a send, or Bcc a copy. Nothing arrives unless you put it there.

Getting started

Accounts are invite-only for now. An admin creates your account and sends a set-password link by email. Click it, choose a password, and sign in. Your inbound address and sender verification are provisioned automatically.

On first login, Doorman sends a short setup interview by email. Reply in plain language — your answers seed the spheres, people, and matters that later mail routes into.

Give it mail

Forward, CC, or Bcc your Doorman address. Each copy is classified, routed to a matter (or held in unsorted when uncertain), and distilled into plain-text memory: status, commitments, people, and a log of what changed.

Ask your memory

In the app, open Chat and ask what's stalled, who owes you a reply, or what changed this week. The same query layer is available over MCP and a small HTTP API — connect Claude, ChatGPT, or any harness you already use.

Correct mistakes

You never have to reply by email to fix routing:

• Unsorted — bulk-file pending mail into one matter, park it, or forget it.
• Matter detail — merge, split, or rename; routing keeps working via slug history.
• Memory — browse every file Doorman knows, edit stored paths, export, or delete.

Email replies with instructions still work too — the converse stage handles file, park, ignore, snooze, note, merge, split, rename, and answer verbs.