Email AI agent — inbox assistant
Triage and drafts that use the project or family thread behind the message — not a sidecar model that only sees the last email.
Triage and drafts that use the project or family thread behind the message — not a sidecar model that only sees the last email.
Email AI that only sees the message will write a polite nothing. Replies need the project, the last call, and whether this is Work or Family.
The Email agent works in the Maicos inbox (Email Client, Gmail, IMAP/SMTP) with the same staff that already sit in chat and calendar. It drafts; you send, until you explicitly automate a class of mail.
Inbox
Accounts together
Maicos, Gmail, IMAP in one place
Context
Not just the thread
Project files and chat when it is Work mail
Draft
You still send
Collaborative by default
Traditional tools
Gmail Smart Reply plus ChatGPT with a pasted thread and no project files.
With Maicos
One inbox in the workspace Work and Family AI Staff already use.
Grounded drafts and triage. Sending is still a decision.
Work and personal accounts can live together, but triage should still respect area: a school thread is not a client P1 just because it arrived at 8am.
“Reply to the contract email” uses the PDF and notes in the project, not a tone slider on an empty prompt.
The useful output is often “this is a task,” “this is a calendar event,” or “this can wait” — not a vanity priority score.
Turn a thread into a Work task or a Family reminder without forwarding it to another AI.
Connect real accounts. Keep send under your finger until a class of mail is boring.
Maicos Email Client, Gmail OAuth, or IMAP/SMTP. An agent cannot triage mail it cannot see.
Ask what needs a human this morning. Then draft the two that matter, in the right area.
Especially anything contractual, medical, or family-sensitive. Appflows can send later for narrow, trusted templates.
If it became a project, it should become a task. The inbox is not the system of record.
The email is short. The contract is a PDF in the project.
Mail arrives in the unified inbox
Client asks if clause 4 is acceptable.
You ask in context
“Draft a reply using the Project Alpha contract notes.”
The draft cites the project
Because Email AI Staff can see the taskspace, not because you pasted 20 pages into a chatbot.
You send
Or you edit. Nothing left the building on its own.
That is the product: the inbox and the project are the same world.
Name the account or the project if it is ambiguous. “Draft a follow-up” should not guess between a client and a school thread.
Inbox · 3 priority
Re: Contract review
AI draft ready · Work area
Family reunion plans
Personal · triaged
The same apps you already work in — not a second chatbot that needs uploads.
Useful agents have a job description. These limits keep this page honest — and help you pick a different agent when you need one.
How people use this every day.
What needs a human vs what can be a draft vs what is noise — split by Work vs Family if both accounts are connected.
Reply using the uploaded PDF already in the task, then file remaining work as tasks.
Keep it out of Work focus; Family AI Staff may own the follow-up task.
Once a reply pattern is boring, an appflow can send. Until then, drafts only.
The Email agent triages and drafts inside your Maicos inbox using chat, files, and calendar from the relevant area. It is not a standalone email GPT.
Maicos Email Client, Gmail (OAuth), and IMAP/SMTP for other providers.
Not unless you enable a specific autonomous path or appflow. Default is drafts you approve.
The product page explains the inbox. This page is the role: an agent whose job is triage and grounded replies.
It can connect multiple accounts. Area routing (Work vs Family) is how you keep them from becoming one panic list.
Start free — Workspace, Create, Automate, and Integrations built for AI from day one.
No credit card required · Free during beta