One Inbox for People and AI Agents: Unifying Mail Without Handing Over Your Gmail
Bring mail from Gmail, Outlook and other providers into one place where agents draft and people decide, using selective forwarding instead of full account access.
By Toan Nhu
Most small teams do not have one inbox. They have a support address in Google Workspace, a founder's Gmail, a sales alias on Outlook and a shared hello@ that three people check when they remember. Adding an AI agent to that mix usually makes it worse: the agent needs access to something, and the easiest option is often full OAuth access to someone's entire mailbox.
There is a cleaner design. Give agents their own mailboxes, route only the mail you want them to see into those mailboxes, and let people and agents work the same queue with clear rules about who owns each thread.
What a shared queue needs to get right
- A data boundary. The agent should see support requests, not payroll, legal threads or password resets.
- Clear ownership. At any moment, everyone should know whether a person or an agent is handling a thread. Two replies to the same customer look careless.
- Sorting and priority. A unified inbox is only useful if the important messages rise to the top.
- Review before sending. Especially at the start, agent replies should be drafts a human approves.
Step 1: Forward selectively instead of connecting whole accounts
Mermail works alongside your existing provider. You keep using Gmail, Outlook, iCloud Mail, Proton Mail, Yahoo Mail or Lark Mail, and create a forwarding rule that sends selected messages to a Mermail mailbox. Mermail does not sign in to your provider account or read your whole inbox; its AI can only process messages delivered to the Mermail mailbox and the thread context that comes with them. Your forwarding rule becomes the data boundary.
Start narrow. Good first rules forward mail sent to your support or sales address, mail from known customer domains, or mail with a specific label or subject prefix. Exclude invoices, payroll, legal and medical correspondence, security alerts, password resets and personal conversations. Once a rule behaves as expected, widen it carefully. Note that forwarding usually applies only to new mail, not your existing archive.
Step 2: Organize mailboxes by job inside one workspace
In Mermail, a workspace is the ownership boundary: it groups mailboxes, members and their roles, custom domains, billing and storage. A practical layout for a small team is one workspace with a mailbox per job, such as support, sales and a verification inbox for agent signups, rather than one mailbox per human. Members with access can open the same threads, and workspace admins control domains, members and billing.
If you serve several clients or deployments, keep one workspace per client. It makes access, storage and billing much easier to reason about than a single workspace full of unrelated mailboxes.
Step 3: Let AI sort, and let people see what matters
Every Mermail mailbox sorts inbound mail into Support, Partnership, Technical and Other tabs. On top of that you can define custom labels with plain-language rules (for example, Refund request or Enterprise lead) and tell urgent email detection what counts as urgent for that mailbox. Urgent messages get a badge and a louder alert, including push and Telegram notifications if connected, so the person on duty sees them without watching the inbox all day.
Step 4: Agents draft, people approve
Each mailbox has a built-in email-response triager that prepares a reply to qualifying new Inbox messages and saves it as a draft for human review. It skips mail that looks automated. The draft is linked to the triager run that produced it, so reviewers can see where it came from. You can also connect Claude, ChatGPT, Cursor, Codex or another MCP client to Mermail and ask it to work through the queue in the same way: read, summarize, draft, and wait for approval before sending.
Step 5: Make handoffs explicit
The trickiest part of a shared inbox is the moment a person steps in. Mermail handles this for forwarded mail with a simple rule: if someone replies directly from Gmail, Outlook or the original provider, Mermail treats it as a human takeover. The whole thread becomes human-managed and Mermail's AI permanently stops processing later messages in it. Continue that conversation in the original provider. If you want the thread to stay in the AI workflow, send the reply from the Mermail draft instead.
That behavior is deliberately conservative. It is always safe for a human to take a conversation back, and it avoids the worst outcome for a customer: a person and a bot replying to them at the same time.
Check the setup
- Send a new message that matches your forwarding rule and confirm it appears in Mermail.
- Send one that should be excluded and confirm it stays only in the original provider.
- Review a triager draft end to end before approving anything automatically.
- Reply from the original provider on a test thread and confirm the AI stops working on it.
Read the Mermail auto-forwarding guide
Keep your existing email and give your agents only the mail they need. Set up a Mermail mailbox and point one forwarding rule at it.
