OVIOO AIMost of it still arrives as email.
So OVIOO connects the mailboxes your company already runs instead of asking anyone to leave them. What changes is not where mail lives — it is what happens in the seconds after somebody reads it.
- Adrián Soler09:41Halden rollout — delivery confirmationPlease confirm the delivery window and resend the requirements…742615
- Castellane SA08:52Proforma — Halden & Co rolloutAttached the proforma for the October works, 12–16 October…742615
- Ingrid HalvorsenYesterdayRe: Halden rollout — updated requirementsFinal requirements attached, two changes since the last…742615
- Riverside GroupYesterdaySpring programme — availability?We’re planning the spring programme again and wanted to ask…742580
- Castellane SAMonSchedule received — thank youConfirming receipt of DeliverySchedule_v3.xlsx…742615
Hola Daniel,
Two things before we lock the schedule: please confirm the delivery window for the 12th, and could you resend the requirements list? I can’t find the latest version.
Gracias, Adrián
The basics are boring on purpose.
Everything else OVIOO does would be worthless if the mail underneath were unreliable.
A serious mail client first
Unified inbox across every connected mailbox, real threads, drafts, archive, junk and the provider’s own folders. Sends wait a few seconds so they can be taken back. Anyone who has used Outlook is at home in minutes.
Folders are roles, not server names
Sent, Drafts, Archive, Junk and Trash combine across accounts, so an old “Enviados” sits beside a new “Sent” without a second column. Folders can be created, renamed and deleted on the server itself.
Shared addresses, per-person access
The addresses a company actually runs on — projects@, finance@, info@ — alongside personal ones. The owner connects a mailbox and grants each colleague read or send access; nobody sees an inbox they were not given.
Health you can see
Each mailbox shows what it is doing: still indexing with the percentage, needs reconnecting, sync error with the reason. A stuck mailbox says so instead of quietly going stale.
Three ways in, one workspace.
Nothing migrates, nothing is rerouted, and stopping leaves your mail exactly as it was.
Microsoft 365 & Outlook
Over Microsoft’s own API, including calendar invitations you can answer from the message.
Google Workspace & Gmail
Over the Gmail API, with labels and threads read the way Google models them.
Any IMAP & SMTP host
Server, port and TLS, with the connection tested before it is saved. The awkward hosts are supported too.
Credentials are encrypted, and OVIOO opens a mailbox with a short-lived lease rather than holding a password in the open. A mailbox belongs to one workspace, and moving it carries its index rather than re-reading the server.
What happens once it is read.
This is the whole point. A message stops being an item in a list and becomes part of the work.
Joins its job
A message carrying a reference number links to it deterministically. No rule to write, no folder to choose.
Becomes a task
A request in the text is proposed as a task with an owner and a date — yours to accept or dismiss.
Becomes money
An invoice or proforma attached to it is read into a payable on the right job, with amount, currency and due date.
Files itself
Attachments land on the job they belong to and on the right shelf in Documents, keeping the version that was actually sent.
None of it happens silently. Anything interpreted rather than matched waits in one review screen with the sentence it came from, and OVIOO cannot send, delete or forward anything on your behalf.
Reply with what you already sent.
When a supplier asks for the requirements list again, the reply box already knows which file went to that contact and when. Attach it in one click and the job records the resend.
The same box knows the reference, so the answer stays on the job without anyone copying a number into a subject line. Signatures are per mailbox, per person, and set centrally when a company wants them uniform.
Hola Adrián,
The delivery window is confirmed for 16:30 on the 12th — Castellane SA is on site from 15:00.
The latest requirements list is attached; it’s the version we sent on 18 August with the two specification changes included.
- Adrián’s questions — this morning
- Castellane confirmation — on site 15:00
- Requirements_FINAL.xlsx — sent 18 Aug
- Confirm delivery window — done
- · Drafts only — you press Send.
- · Uses reference context only when authorised.
- · Facts in the draft link to their source.
History is searchable from day one.
Indexing and analysis are different things, and confusing them is how other tools produce a surprise bill.
Indexed: everything
Every message in a connected mailbox is indexed and searchable immediately — headers, threads, attachments and codes. That costs nothing and is never rationed.
Analysed: what you choose
Each mailbox has a date OVIOO reads from. Older mail is read on demand — when somebody opens the thread, or when the context would help a live job and you say yes.
What connecting a mailbox actually means
The question behind every email product: what changes on our side, and what happens if we stop.
Nothing is migrated and nothing is rerouted
Your MX records do not change, your addresses do not change, and mail is not forwarded anywhere. OVIOO connects to Microsoft 365, Google Workspace or any IMAP host and reads alongside you. People who prefer Outlook can keep using Outlook.
Leaving takes your mail with you
Because nothing was moved, disconnecting leaves every mailbox exactly as it was, with the same folders and the same history. That is a deliberate property, not an accident: a product that holds your email hostage does not deserve the connection.
Shared mailboxes without a shared password
orders@, projects@ and finance@ open beside personal addresses in one window, with access granted per person. Somebody who may read operations mail does not thereby read finance, and every grant is visible in one place and revocable.
Sending is a person, every time
Drafts can be prepared for you — with the context they were built from listed beside them — but nothing leaves without somebody pressing send. There is no auto-reply, no scheduled sequence and no rule that answers a customer.
Credentials are encrypted, and expire
Stored mailbox credentials are encrypted at rest. Connector sessions are scoped to one workspace, expire, and are never written to disk — a key that lived inside the app would be a key every customer shared.
The honest limit
Generic IMAP and SMTP need a connector running to sync and send. It ships inside the desktop app, so mail moves while somebody has OVIOO open, and a queued send waits for the next time anyone does. Microsoft and Google are HTTPS APIs and are unaffected.
Fair questions
It can, and it does not have to. OVIOO is a full mail client — read, reply, attach, search, undo send — but it connects rather than migrates, so a team can move over one person at a time, or never. What matters is that the mail reaches the work either way.
For Microsoft 365 and Google Workspace it is an OAuth connection. For a generic IMAP host it is a server, a port and a credential. There is no MX change, no domain verification and no mail routing to approve.
Attachments are kept and filed against the job they arrived on. Message text is retained inside a retention window you can see, and older bodies are swept while the message itself stays indexed and searchable — so storage does not grow without bound and the record does not disappear.
No. It does not delete, archive or move messages on your mailbox on its own, and destructive actions in the product go through a thirty-day recovery window rather than vanishing.
Keep your addresses. Change what happens next.
Connect one mailbox and see a week of real mail turn into work you can hand to somebody.