AI email triage
Let the inbox sort the work before anyone opens it.
Gent gives an agent inbox the rules, labels, AI checks, events, and approval gates to turn inbound email into routed work instead of another pile of unread messages.
The problem
Routing alone does not decide what matters.
A forwarding rule can move a message. It cannot reliably decide whether the message is a lead, a vendor request, a support issue, a low-priority update, or a risky reply that needs a human. Gent keeps those decisions inside the inbox record.
Classify
Identify what kind of work arrived before a person starts scanning their inbox.
Label
Apply labels and context so later automation and search can work from the same record.
Route
Assign or forward the thread to the inbox, owner, workflow, or webhook that should handle it.
Escalate
Hold sensitive drafts or destructive actions for review instead of letting automation run unchecked.
How it works
Email arrives. The inbox decides the next step.
Receive
A message lands with sender, recipients, subject, body, attachments, and thread context.
Evaluate
Workflow rules and AI workflow conditions inspect sender, content, labels, and configured instructions.
Organize
The inbox applies labels, moves messages, updates contacts, creates tasks, or assigns the thread.
Notify
Webhooks and event notifications carry important changes into the product or workflow that owns the next step.
Review
Sensitive replies can be drafted, queued, and approved by a human before sending.
Use cases
The first pass happens before the bottleneck.
Lead intake
Separate real opportunities from newsletters, cold pitches, and low-intent replies.
Support triage
Label and route routine issues while surfacing cases that need a person.
Vendor mail
Identify invoices, requests, missing details, and follow-ups without hand-sorting admin mail.
Internal handoff
Create tasks or assignments when a thread belongs with another inbox or owner.
Why Gent
Triage needs memory, rules, and a record.
Generic AI assistants can summarize a thread after someone opens it. Routing tools can forward mail. Gent sits where the work begins: the inbox that receives the message, applies rules, calls AI when configured, fires events, and preserves what happened.
Inbox-native
Labels, messages, tasks, contacts, files, approvals, and events live around the same inbox.
API-first
Products can consume routed work through webhooks, events, and the API instead of screen-scraping an inbox.
Controlled
Scopes and approval queues define what the agent may do automatically.
Not a help desk
Use Gent when software needs email primitives, not a ticket queue for a human support team.
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.