Give your support agent an inbox.
A real, monitored address your AI support agent owns — so it can receive tickets, reply in-thread, and escalate without a human relaying every message.
Support happens in email. Customers reply to order confirmations, forward receipts, and send screenshots — all to an address a person is expected to be reading. An AI support agent without its own inbox is stuck behind a human who has to copy messages in and paste answers back out.
Mailgent gives the agent a real address it owns: support-name@mailgent.dev. It reads incoming threads, replies in the same thread with full quoting, handles attachments, and hands off to a human when it should — all through tools built for software instead of a mail client.
Reply in the thread, not a new email
Customers expect a reply to land under the message they sent, with the history intact. The agent lists unread threads, reads the full conversation, and replies in place so the customer sees one continuous exchange.
Labels and rules keep the queue organized: auto-tag by topic, route billing questions to one label and bugs to another, and mark threads resolved when the agent closes them.
const threads = await mail_list_threads({ label: "inbox", unread: true });
for (const t of threads) {
const thread = await mail_get_thread({ id: t.id });
const answer = await draftReply(thread);
await mail_reply({ threadId: t.id, text: answer });
await mail_update_thread_labels({ id: t.id, add: ["resolved"] });
}Escalate with the whole context
When a ticket needs a human, the agent doesn't drop it. It forwards the thread to your team's address or applies an escalation label your staff watches, so the handoff carries the full history and the customer never repeats themselves.
Because the agent has its own identity, every action it took is attributable and logged — you can see exactly which replies were automated and which were human.
Deliverable, verified mail
Replies are sent from a verified sender with proper DKIM and SPF, so they land in the inbox instead of spam. Customers see a real address, not a no-reply, and can keep the conversation going.
FAQ
Can the agent handle attachments?
Yes. It can read inbound attachments (screenshots, receipts, logs) and attach files to its replies.
How does a human take over a thread?
The agent forwards the thread or applies an escalation label your team monitors. State and history travel with it.
Is the inbox shared with other agents?
No. Each agent identity gets its own address and its own scoped key, so actions are isolated and attributable.
Give your agent an inbox.
A real email address, a vault, 2FA, and an identity in one API call.