AgentMail Campaign Inbox
Connect AgentMail, manage campaign inboxes, sync replies, and keep campaign conversations separate from transactional email.
DeepSyte uses AgentMail for two-way campaign email. Each user brings their own AgentMail API key. One AgentMail API key is treated as controlling that user's AgentMail organization, including its domains and inboxes.
Provider responsibilities
| Provider | Use |
|---|---|
| AgentMail | Campaign sending, replies, drafts, thread sync, sender pools, safe daily caps |
| Resend | DeepSyte transactional messages, product notifications, report-completion notices |
Gmail, Outlook, Composio, and inbox mining are not part of this phase.
Setup
- Add the AgentMail API key in
/dashboard/settings. - Open
/dashboard/inbox. - Verify the API key state.
- Add sender domains or let DeepSyte discover them from existing AgentMail inboxes.
- Create or connect inboxes for each domain.
- Keep each sender in warmup mode unless the inbox is already prewarmed.
The first rollout target is up to 3 domains with 3 inboxes per domain.
Inbox page
The Inbox page shows:
- AgentMail API key state.
- Sender domain cards.
- Inboxes grouped by domain.
- Current daily capacity.
- Warmup or manual limit mode.
- Next warmup increase.
- Paused or failed sender states.
- Campaign-linked threads and replies.
Replies are synced from AgentMail into DeepSyte threads. When a recipient replies, the campaign row is marked replied and can be suppressed or handled from the conversation view.
Safe sending rules
Campaign emails are plain-text-first, have no tracking pixels, no tracking redirects, no attachments, and at most one report link in the first outbound message.