Existing email stack
Do not replace the inbox. Stop lending it to agents.
Gmail, Outlook, forwarding tools, and help desks can stay where they are. Gent gives delegated work its own address, record, controls, and API surface.
The boundary
Keep human email human.
Your personal or team inbox is still the place for people to read, decide, and communicate. Gent is for work that software or an agent needs to handle: intake, follow-up, routing, approvals, and records.
Human inbox
Personal judgment, meetings, calendar context, direct relationships, and ordinary day-to-day mail.
Gent inbox
Delegated work with scoped tokens, workflow rules, webhooks, approvals, and audit history.
Forwarders
Useful alias and routing layers. Gent can be the destination when the message needs to become managed work.
Help desks
Best for human support teams. Gent fits before, beside, or beneath them when email has to become programmable workflow.
Common routes
How mail moves.
Direct to Gent
Use a verified custom domain when an agent, workflow, or client mailbox should own the address from the start.
Forward a copy
Send copies from Gmail, Outlook, or another system into Gent while the original human inbox remains intact.
Route selectively
Use rules to send only certain senders, subjects, recipients, or labels into Gent-managed work.
Escalate back
When risk is high, Gent can hold a reply for approval or forward context to the human/team system that should decide.
When to use it
The signal is not email volume. It is delegated responsibility.
Use Gent when the reply, record, or follow-up should not depend on a person remembering to move a thread. If the work needs authority, state, an audit trail, and a clean boundary from your human inbox, it belongs in its own inbox.
Client work
One inbox per client, project, workflow, or agent so context stays separated and reviewable.
Vendor intake
Requests, invoices, documents, and follow-ups become structured work instead of loose messages.
Approvals
Risky sends can be drafted by an agent and held until a person approves them.
Operational records
Messages, contacts, files, labels, webhooks, and audit events stay with the delegated workspace.
Next step
Give the delegated work its own address.
Start with one workflow that should no longer borrow a human inbox: vendor intake, client follow-up, support escalation, or agent-managed approvals.