An agent inbox is a dedicated email workspace for delegated work.
It gives an AI agent its own address, credentials, activity record, and control surface. The agent can receive email, send replies, apply labels, save files, trigger workflows, and wait for human approval when needed.
It is not just another alias.
Here at gent.mx, we think the useful shift is giving agents a real place to work without pretending they are people. The inbox should make the agent more capable, but also easier to limit, inspect, and take over.
An alias forwards mail
An alias or forwarding address is mostly a delivery tool. It receives mail at one address and sends it somewhere else. That can be enough when the goal is simple delivery.
But delegated work usually needs more than delivery.
An agent inbox owns work
An agent inbox can be the place where work happens:
- Messages arrive.
- Rules classify and route them.
- Files and attachments are handled.
- Tasks or follow-ups are created.
- Replies are drafted or sent.
- Sensitive actions wait for approval.
- Activity and audit records remain attached.
That is the difference between "send this email somewhere" and "let the agent operate this inbox under rules."
Why it matters
The inbox boundary makes the agent easier to control. Instead of granting broad access to a person's mailbox, you issue scoped access to a dedicated workspace. Instead of mixing agent activity into a personal sent folder, you keep it in the agent's own record.
That record becomes important as the agent takes on more operational work.
Where to start
Create an inbox for a specific job: lead intake, vendor invoices, customer triage, client follow-up, or approvals. Then connect the agent with the smallest set of scopes needed.
The features page, docs guide, and workflow library show the product, operator, and developer views of the same model.