Email that already knows who is writing to you.
Gmail and Microsoft 365 mailboxes, connected by OAuth and synced with their folders intact. Every thread carries the sender’s record in Cyril — deals, invoices, tickets, docs — and the AI drafts and proposes without ever sending or filing on its own.
What Mail does for you
One inbox, real folders
Gmail and Microsoft 365 mailboxes in a single list. Your labels and folders mirror into a navigable tree, and creating, renaming or filing writes back to the actual mailbox rather than into a Cyril-only copy.
The sender, in context
A rail beside each thread shows the linked contact and company, open deals, outstanding invoices, open tickets and related docs. Each section is withheld server-side if you lack that module’s permission.
AI that proposes, not acts
Open a thread and get a summary, a reply grounded in the sender’s records, and a suggested action. Confirming it raises a proposal; the owning module creates the ticket, bill or deal only after a second, explicit confirm.
Received mail held at arm’s length
Sender HTML renders in an isolated sandbox and remote images stay blocked until you approve them, then load only through Cyril’s authenticated proxy. Trust signals, safe link inspection and phishing reporting sit on the thread itself.
A supplier emails an invoice. Cyril already knows they are a supplier.
Because Mail is part of the platform rather than a connector into it, a thread is read against the Sales record, the open tickets, the outstanding bills and the docs that explain them — one query, one permission model. A deterministic classifier reads inbound mail and puts recognised work on its own queue with what it thinks the item is and how sure it is.
- Confidence floor of 0.7, with anything marginal badged low confidence
- Reclassify before anything is created — nothing routes on its own
- Per-organisation category → team routing, recorded and overridable
Mail is not a second place your email lives.
Every folder in Cyril exists in the real mailbox, read and unread state writes back to Gmail and Outlook, and organisation signatures are inserted server-side immediately before delivery — so no compose, reply, forward or scheduled send can bypass the active rule. What Cyril will not do here is as deliberate as what it will.
- Compose, reply, forward, attachments, send later and thread snooze
- No Cyril-only folders, and no folder deletion — you delete in Gmail or Outlook, where the consequence is visible
- No mail-rules engine and no out-of-office responder: your provider’s rules are respected as they stand
Common Mail questions
No. Gmail and Microsoft 365 via OAuth are the only supported paths. Generic IMAP is parked until after GA, so if your mail is not on Google or Microsoft, Mail will not work for you today.
No. A connected mailbox is private to the person who connected it, and ownership is checked in code on every read, sync, send, schedule and disconnect. You can assign an individual thread to a colleague — that mints a revocable, audited grant on that one thread, with internal notes and a warning when someone else is already replying.
Not yet. Reply and forward ship; a distinct reply-all control is still follow-up work. Worth knowing before you move a busy thread into Cyril.
The last 30 days by default, and only from the folders you choose to sync — Spam and Trash are never included unless you ask for them. Cyril is not trying to become the archive of your mailbox; older mail stays where it is.
Be one of the first to use Cyril.
Join the waitlist for early access. We'll only email you when there's something real to share.