# Agent Inbox {#agent-inbox}




> [!IMPORTANT]
> Every account has the agent inbox. Open the **Inbox** page in your dashboard to set up your first one.



An agent inbox is a real email address on your own domain, like `support@yourcompany.com`, where Nitrosend receives mail, triages it, and lets your AI agent and your team answer it together. Campaigns and flows send email; the inbox is where email comes back.


## Your domain, your existing mail untouched {#your-domain-your-existing-mail-untouched}


Use your own domain or a Nitrosend address. The setup flow shows the receiving options for that domain: keep your existing provider and forward a copy, or let Nitrosend receive first with the forwarding arrangement shown in setup. Verify delivery before relying on the inbox.

The exact DNS records for your domain are shown in **Settings > Domains** ([app.nitrosend.com/my/settings/domains](https://app.nitrosend.com/my/settings/domains)). Once the records verify, your claimed addresses start receiving.


## Separate inboxes, one brand view {#separate-inboxes-one-brand-view}


Each email address is its own inbox, with its own sender name, mail and storage. Create several inboxes on the same domain without using another domain slot. Open **Inbox** to see all of the selected brand's inboxes together, or filter by address.

Free includes one inbox per account; Starter, Pro, Growth and Scale include three. Additional inboxes cost US$1/month each, shared across the account's brands. Free supports up to three total. A paid base plan is not required. Your existing included capacity is preserved, with no retroactive charge.

[Coexist](https://docs.nitrosend.com/guides/inbox-coexist.md) adds optional copies to your existing provider;
[storage upgrades](https://docs.nitrosend.com/guides/inbox-storage.md) add space to one inbox. These are
separate from additional inboxes. See the [current prices](https://nitrosend.com/pricing).

Customer-added aliases are being replaced by independent inboxes with preserved capacity and history. Previous addresses kept after a rename continue receiving in the renamed inbox; they are not additional paid inboxes.

Archiving stops new mail and replies while preserving history and reserving the address. Archive unused inboxes before reducing paid capacity. If payment ends, extra inboxes keep receiving, while replies pause until capacity is restored.


## The action queue {#the-action-queue}


Every inbound message lands in the action queue in one of four states:

- **Needs you** — a human should look at this. Mail lands here when it needs judgment: a mismatched reply-to address, a provider spam flag, or suspicious content in the body.
- **Agent ready** — clean mail your agent can answer. Passed the applicable provider spam, authentication and content checks.
- **Handled** — resolved items, kept as an audit trail.
- **Quarantine** — mail that failed security checks or arrived on a disabled inbox. Quarantined mail that failed a virus check can never be released to the agent.

Nitrosend uses provider spam and authentication results and checks message content for prompt-injection attempts aimed at your agent. These checks do not certify attachment safety. Flagged content is marked in the queue so a human sees exactly why an item needs attention.


## Inbox vs Campaigns {#inbox-vs-campaigns}


- **Campaigns and flows** — designed, on-brand email to many people. Templates, sections, pixel-perfect layout.
- **Inbox** — plain 1:1 human email. No templates, no designer. A reply from your inbox reads like a person wrote it, because the recipient should never feel like a campaign target mid-conversation.


## Replies and new messages {#replies-and-new-messages}


Reply to any thread, or compose a new message from an inbox address. Compose supports multiple To recipients plus Cc and Bcc. Replies support Cc, Bcc and Reply all, with recipients shown before sending. Replies thread correctly with the original message, and every outbound message goes through the same sending checks as the rest of your account.

Sending to an address that already has an open conversation continues that thread instead of starting a new one.


## Agent and human, together {#agent-and-human-together}


Your agent works the queue over MCP:

- `nitro_inbox` — read the queue and mailbox: `list_queue`, `get_item`, `list_mailbox`, `get_thread`, `get_thread_page`, `get_message_body`, `validate_reply`
- `nitro_inbox_action` — act on items: `send_reply`, `send_reply_test`, `mark_handled`, `request_human`, `release_to_agent`, `mark_quarantine`

The agent answers what it can and escalates with `request_human` when it should not decide alone. Your team works the same queue in the dashboard under **Inbox**, with the same actions. Every disposition is recorded, whoever made it.


## Message source {#message-source}


Every message has a source view: the full stored header map, authentication results (SPF, DKIM, DMARC, spam, virus), and the raw text and HTML content. Open it from any message in a thread when you need to debug delivery or verify where a message really came from.
