Email routing for AI agents
Route email to the work it should become.
Gent gives each agent or workflow a real inbox, then lets rules, labels, approvals, and webhooks move inbound mail into the right path without turning routing into a pile of forwarding scripts.
The problem
Forwarding moves the message. It does not own the work.
A simple routing rule can send mail from one address to another. Agent work usually needs more: a destination inbox, sender context, labels, attachments, review rules, webhook events, and a record of what happened next.
Agent addresses
Give agents and workflows addresses on verified custom domains instead of borrowing a human inbox.
Inbound rules
Use sender, recipient, labels, message context, and workflow conditions to decide what should happen.
Human paths
Hold sensitive replies or destructive actions for approval when software should not decide alone.
System handoff
Send events to the CRM, product, finance workflow, support stack, or internal tool that owns the next step.
How it works
Mail enters through the right address, then rules decide the next path.
Receive
Inbound mail lands in an inbox created for the agent, workflow, client, project, or operational function.
Classify
Rules and labels identify the sender, purpose, urgency, attachment state, or workflow condition.
Route
The inbox applies labels, creates tasks, queues approvals, stores files, or prepares the handoff.
Notify
Webhook events carry the message context into the external system that should continue the work.
Record
The message, action, approval, webhook, and audit trail stay attached to the inbox that handled the route.
Use cases
Use routing when inbound mail has more than one rightful owner.
Lead intake
Route new inquiries to a follow-up workflow while keeping the original conversation in the agent inbox.
Vendor mail
Separate invoices, missing details, documents, and approvals without relying on a shared mailbox.
Client operations
Keep each client, project, or tenant in the right inbox with its own context and record.
Human review
Send high-risk replies or changes to an approval queue before the agent acts.
Why Gent
Routing should create an operating record, not just another copy of an email.
Traditional forwarding, aliases, and distribution lists are useful when delivery is the only job. Gent is for delegated email work where the routed message needs rules, state, authority, and history around it.
Not just forwarding
The inbox can label, task, file, approve, notify, and preserve what happened next.
Works with your stack
Use Gent alongside Gmail, Outlook, help desks, forwarding tools, and internal systems.
API-first
Messages, labels, tasks, files, approvals, webhooks, and events are available through the API.
Governed
Scoped tokens and approval queues keep routed agent work inside defined boundaries.
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.