Mail AutomationPrivate AI operations
Professional email operations team at work

Customer-hosted Gmail automation

Every customer email handled.In their language. On your terms.

Mail Automation understands incoming Gmail conversations, drafts evidence-backed replies, and sends only when the operating mode and safety policy allow it.

  • Off, Semi-autonomous, or Autonomous
  • One customer-owned OAuth app
  • Data isolated by inbox

Email in progressReservations · French

NEW
INCOMING MESSAGE

“Bonjour, est-il possible de modifier ma réservation pour arriver un jour plus tôt ?”

Knowledge foundVerified source
Approval requiredPolicy safeguard
MESSAGE OUTCOMEDraft ready for review
Customer-owned Google OAuth
Multiple isolated Gmail inboxes
Multilingual replies
Human approval safeguards

A real operating decision

Don’t trust a black box.See why every reply moves.

Each message is classified, grounded, checked against policy, and either drafted, sent, or held for your team.

Reply decisionReservations inbox · just now

SEMI-AUTONOMOUS
DRAFT RESPONSEGrounded in 2 sources

Bonjour Camille,

Merci pour votre message. Nous pouvons vérifier la disponibilité pour une arrivée un jour plus tôt. Avant de modifier la réservation, notre équipe confirmera le nouveau tarif et la disponibilité.

Nous revenons vers vous très rapidement avec la confirmation.

Guest Services
Customer Support
INBOX OPERATING MODE

Reservations

reservations@example.com

Human approval activeBooking changes, refunds, and uncertain replies

Control, not a blank workflow

More email handled.Accountability stays human.

The agent prepares evidence-backed drafts while your team reviews every reply before it leaves the inbox.

A different architecture

Email automation should work for the customer.

Professional automation without surrendering credentials, mixing inbox data, or hiding the operating decision.

01
Per-inbox control

Off means off

Keep an inbox connected for context while drafting and sending remain fully disabled.

02
Semi-autonomous

Draft first. Review every reply.

The agent prepares a grounded response in the sender’s language. Your team decides what leaves the inbox.

03
Autonomous

Routine work moves. Risk waits.

Confident routine replies can send automatically while sensitive or uncertain email enters approval.

04
Customer-owned access

One OAuth app. Your installation.

Connect multiple Gmail inboxes through one Google OAuth application owned and controlled by the customer.

05
Strict isolation

Every inbox is its own operation.

Authorization, Gmail identity, signature, knowledge, settings, and history stay isolated by inbox.

06
Multilingual by design

Reply in the sender’s language.

The agent understands multilingual threads and responds from approved business knowledge and conversation context.

Built around email reality

Useful on the first thread. Adaptable after the thousandth.

Start with safe multilingual drafting, then connect knowledge and approved business tools as the operation grows.

01

Grounded answers

Responses use approved knowledge and relevant email history—not unsupported guesses.

02

Human when it matters

Sensitive, uncertain, or policy-triggering messages remain visible in the approval queue.

03

Business actions

Connect approved tools and workflows without mixing credentials or state between inboxes.

04

Nothing disappears

Actions, decisions, approvals, and sends remain observable through the audit history.

One observable path

The agent replies.Your team stays accountable.

01Gmail receives the messageIdentity and history stay inside that inbox
02The agent retrieves evidenceApproved knowledge and relevant thread context
03Policy chooses the routeOff, draft for approval, or eligible auto-send
04The outcome is recordedDecision, sources, approval, and send remain auditable
CUSTOMER INSTALLATION

Authorization stays encrypted and isolated.

One customer-owned OAuth application connects multiple Gmail inboxes without merging their credentials, identity, signature, settings, or data.

Customer-hosted architecture

Before connecting Gmail

What teams need to know before getting started.

01Can one installation connect multiple Gmail inboxes?+

Yes. One customer-owned Google OAuth application supports multiple connected Gmail inboxes, while every inbox keeps separate encrypted authorization, identity, signature, automation settings, and data.

02Does autonomous mode send every email automatically?+

No. Autonomous mode can send eligible routine replies, but sensitive, uncertain, or policy-matched conversations are held for human approval.

03Can automation be disabled for only one inbox?+

Yes. Off, Semi-autonomous, and Autonomous are selected independently for each connected inbox.

04Where does the email data live?+

The platform is designed for customer-hosted deployment, so operational data and encrypted credentials remain within the customer installation.

Your workspace. Your rules.

Put routine email on autopilot without losing control.

Connect Gmail, choose the mode for each inbox, and keep sensitive decisions with your team.

Open your workspace