Human-in-the-loop email agent
Let the agent prepare the work. Keep the final authority.
Gent gives an email agent its own address, scoped token, approval gates, and audit trail, so sensitive replies and changes can be held for human review instead of borrowing a human inbox.
The problem
Approval prompts are not oversight.
A human-in-the-loop email workflow needs more than a popup before send. The reviewer needs the message, thread, token scope, intended action, and record of what happened. Gent keeps that context attached to the agent inbox.
Own address
The agent works from its own inbox, not a person's mailbox or reputation.
Scoped authority
Tokens decide what the agent may read, send, delete, or change.
Approval queue
High-stakes sends and destructive actions can be queued instead of executed.
Audit record
Approvals, rejections, webhook events, and message history remain attached to the workspace.
How it works
The agent acts inside boundaries you set.
Create inbox
Give the agent a verified custom-domain address for the workflow it owns.
Issue token
Grant only the scopes needed, such as email:read, email:send, contacts:read, or task:write.
Require approval
Set requires_approval for sensitive scopes like email:send or destructive actions.
Review action
The agent receives a queued response with an approval_id; a human approves or rejects before execution.
Keep the record
The thread, held action, outcome, and audit trail stay with the delegated inbox.
Use cases
Where human review matters.
Client follow-up
Let the agent draft and organize replies while a person approves what goes to the client.
Vendor intake
Extract the work from invoices and requests without letting the agent send risky commitments unattended.
Support escalation
Classify and prepare responses, then hold sensitive cases for human decision.
Regulated work
Keep evidence of who approved what, when, and from which inbox.
Why Gent
Control belongs where the email work happens.
If an email agent uses a human mailbox, review happens after identity, history, and reputation are already mixed together. Gent separates the delegated workspace first, then applies scopes, approvals, webhooks, and audit to that workspace.
Not your inbox
The agent does not need your sent folder or personal mailbox to do its job.
Not blind automation
Rules and approvals define where autonomy stops.
Not a help desk
Use Gent when software needs email primitives, not a ticketing workspace for human support teams.
API-first
Messages, approvals, tokens, events, and audit are available through the API.
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.