Email basics
Connect Gmail or Outlook and work your inbox with Maya — read, open, reply, compose and batch-draft. Maya is the only agent with your inbox, and she never sends anything without your click.
Diese Seite ist in deiner Sprache noch nicht verfügbar — wir zeigen die englische Version.
Maya is your email agent. Connect Gmail or Outlook and she reads your inbox, opens the thread you point at, and writes the reply — as an editable card you send yourself.
She is the only one of the ten agents who can do any of that.
Maya is the only agent with your inbox
The mail tools are mounted for Maya alone. This isn't a rule in a prompt she could be talked out of — the email toolset simply does not exist for Ashley, Blake, Lucy or anyone else at runtime. If you ask another agent to write an email, they hand the job to Maya, who opens her own conversation to do it.
And if no mailbox is connected, the email tools don't exist for Maya either.
Connect a mailbox
Maya works with Gmail or Outlook / Microsoft 365 — or both at once.
- Open Integrations from the sidebar.
- Click Connect next to Gmail or Outlook.
- Sign in and approve the permissions.
- Open a conversation with Maya and ask for your inbox.
That's it. Full walkthroughs: Gmail · Outlook.
One Gmail per account — but Gmail *and* Outlook is fine
Unyo stores one Gmail connection and one Outlook connection per user. You can have both mailboxes connected side by side. You cannot connect two Gmail accounts.
One conversation, one mailbox
If you have both connected, every conversation locks to whichever mailbox it first acted on. The pill above the composer shows which one, with a lock icon.
This is deliberate. A thread that silently switched mailboxes halfway through is how the wrong reply goes to the wrong person from the wrong address. Ask Maya to switch mid-conversation and she'll decline and point you at a new chat — the new one is unlocked and will bind to whichever mailbox you use first.
Read your inbox
You get a rendered inbox card — sender, subject, snippet, date, unread state, attachment flag — not a wall of numbered text. Maya is explicitly instructed never to list your emails as prose; the card is the interface.
From the card you can:
- Filter to unread only — ask for it.
- Open any email to read the full body in place.
- Fire a quick action — Draft top 2, Summarize, Find invoices are one tap.
What Maya actually sees
Maya works from a cache of your most recent inbox messages — around the latest 10 per mailbox. Anything older than five minutes triggers a re-sync in the background, so the inbox she reads is at most one refresh behind. Snippets are stored at 150 characters and bodies at 2 000.
She is not indexing your archive and she cannot search five years of mail. She works the top of your inbox, which is the part that needs working. Cached mail is deleted after 30 days by a nightly job.
Open an email
Maya pulls the full body. For Gmail, if the message isn't in the recent cache she can still fetch it from the API. For Outlook, messages outside the cached window aren't reachable — you'll get a clear "not found" rather than an invented summary.
Reply
You get an editable reply card with the real recipient, the real subject (Re: …) and the real thread attached.
Not "real" as in Maya tried hard. Real as in she never touches those fields: she passes the email's id, not an address, and the server resolves the actual sender, subject, thread id and message id from your inbox. If the id doesn't resolve to a genuine email, the tool refuses and tells her to re-read the inbox — and either way, every field is on the card in front of you before anything sends.
Compose
Write an email to jean@acme.com about the Q2 report — we're two weeks behind and I want to propose a new date
Same card, blank thread. Edit to, cc, bcc, subject and body directly — your edits autosave about 1.5 seconds after you stop typing and survive a reload, a tab switch or a browser close.
If your ask is genuinely too thin, Maya asks one short question instead of drafting filler.
Iterate by talking, not retyping
Say "make it shorter" or "add Isadora in CC" and Maya sees your current edited draft, not her original. Every field you changed by hand is preserved; the old card is marked superseded so you can't send a stale version by accident.
Batch: reply to several at once
You get all three drafts in one collapsible card. Review them, edit them, send them individually. Same for composing:
Both drafts, one card. Maya is instructed never to fire off separate compose calls for a multi-email ask.
Sending — the part Maya doesn't do
Every compose and every reply renders a card. The card has a Send button. You press it.
There is no auto-send. Not as a default — as an absence.
The send is gated in the database, not in a prompt. The send action is flagged as confirmation-required in config, so it can never execute directly — it routes to an editable card and stops there until you click. Maya can draft, batch, attach and stage; the transmission itself only fires from a human click.
This is also true of Maya's overnight work: automations draft, never send. There is no setting that turns this off, because there is nothing to turn off.
Once you click:
- Double-tap-proof. Every confirmed draft carries a stable idempotency key. A retry, a refresh or a resumed run cannot send the same email twice.
- Your signature is injected server-side in both HTML and plain text, then frozen into the sent record — editing your signature later doesn't rewrite history. See Email signature.
- Tagged in your real mailbox. Gmail gets a Sent by Unyo label; replies get Answered by Unyo on the original (and archive it). Outlook gets the matching categories. Your mailbox stays legible from your phone.
- Gmail recipients become contacts in your Neural Core, automatically.
Caps: 10 recipients per email, 10 attachments.
Attachments, in one line
Maya can attach from Google Drive, your Neural Core and your image library — and files you drop on the card yourself. That has its own article: Email drafts and attachments.
Send later
Compose and reply draft cards have a Schedule button. Pick a date and time and it's stored as a real instant in your timezone, DST included. Details and limits: Email scheduling.
What this costs
Nothing, at the tool level. Reading your inbox, opening an email, composing, replying, batch-drafting and sending are all 0 credits.
You pay for the model's thinking on the run — billed on real cost, not per message. See Credits and billing.
Tips
- Ask for the inbox before asking for drafts. Maya drafts far better replies when the thread is in front of her.
- Point, don't spell. "Reply to the Uniqlo one" is more reliable than pasting an address — the server resolves the real one.
- Edit on the card. For small changes, typing into the field beats asking for a rewrite.
- Give her your tone once. Anything you tell Maya about how you write lands in your Neural Core, and she uses it next time.
- Two mailboxes? Start a fresh chat per mailbox. The lock is per conversation.
Troubleshooting
"Reconnect from Integrations" instead of my emails Your mailbox token expired or was revoked. Unyo detects this and marks the connection disconnected rather than quietly showing you an empty inbox. Go to Integrations, reconnect, ask again.
The mailbox pill is locked and I want the other one Working as designed — one conversation is bound to one mailbox. Open a new conversation with Maya; it locks to whichever mailbox you use first there.
Maya says she has no mailbox Nothing is connected yet, or the connection dropped. The email tools only exist when a mailbox does.
"Email not found in cache" on Outlook The message is outside the recent window Maya works from. Open it in Outlook directly, or wait for it to come back to the top of the inbox.
She's not showing an email I can see in Gmail Two likely causes: it's below the recent window she reads, or you have a newsletter filter on that's dropping it from summaries. Ask her directly — "is anything being filtered?"
Can Maya send an email without my approval?
No — and not because of a setting. Sending is confirmation-gated in Unyo's database config, not in Maya's instructions: any send resolves to an editable card and waits. Every compose and reply becomes an editable card, and transmission only fires when you click Send. This holds for her overnight automations too: they draft, they never send.
Can my other agents read my inbox?
No. The email toolset is mounted for Maya only — at runtime, not just in her instructions. Ashley, Blake, Lucy and the rest have no inbox tools to call. If you ask one of them to write an email, they delegate to Maya, who opens her own conversation and does it there.
Can I connect two Gmail accounts?
No. Unyo stores one Gmail connection per user. You can connect Gmail and Outlook together and work both, but not two accounts on the same provider. Each conversation then locks to one of them.
Does Maya see my entire inbox?
No, and it's worth being precise about this: she works from a cache of roughly the 10 most recent messages per mailbox, re-synced in the background once it passes five minutes old. Snippets are stored at 150 characters, bodies at 2 000, and the whole cache is purged after 30 days. She works the top of your inbox — she is not an archive search engine.
How can I be sure the reply goes to the right person?
Because Maya doesn't choose. She passes the email's id and the server resolves the real sender, subject, thread and message id from your cached inbox. If the id isn't genuine, the tool errors out instead of guessing. Then you see every field on the card before you send.
What does reading and drafting cost?
Zero credits for the tools themselves — inbox, read, compose, reply, batch and send are all free. You're billed for the model's actual token cost on the run, which is metered on real spend rather than a flat per-message fee.