Agency client inboxes
Run client email work without mixing client inboxes.
Gent gives agencies, consultants, and operators a way to give each client workflow its own address, rules, context, approvals, and record, so delegated email work stays separate while the operation stays manageable.
The problem
Client work gets messy when every thread lands in the same place.
An agency might handle leads, support, vendor requests, follow-ups, approvals, and reporting for several clients. If that work shares one mailbox or one improvised routing layer, context leaks, ownership blurs, and review becomes harder than the work itself.
Separate addresses
Give each client, project, or workflow an inbox that owns the conversation from the start.
Separate context
Keep contacts, labels, files, tasks, and history attached to the inbox that handled the work.
Separate rules
Apply routing, follow-up, approval, and webhook behavior for the client workflow it belongs to.
Separate records
Keep audit history and activity visible without forcing everything into a shared human mailbox.
How it works
Each client workflow gets its own operating surface.
Add domain
Register and verify the customer-owned domain or subdomain that should carry the client-facing address.
Create inbox
Create the inbox for the client, project, agent, or workflow that should own incoming mail.
Configure access
Issue scoped tokens so automation can read, label, send, update contacts, or create tasks only where allowed.
Apply controls
Use approval requirements for sensitive sends, destructive actions, or work that affects a client's reputation.
Watch activity
Use tenant and inbox-level stats, webhooks, and audit events to understand what happened across the operation.
Use cases
The agency keeps the system. The client keeps a clean boundary.
Lead desk
Receive, classify, reply, and follow up from the client-specific address instead of a consultant's inbox.
Vendor intake
Route invoices, documents, and requests into a client-owned workflow with its own history.
Client support assist
Handle routine inbound work before handing sensitive cases to a human or help desk.
Operations reporting
Review inbox activity, send volume, approvals, storage, and audit events without mixing client records.
Why Gent
Agency email operations need boundaries before automation.
Generic shared inboxes are built around people reading mail together. Gent is built around delegated email work: the inbox receives the message, rules and agents act inside defined authority, and the record stays attached to the workflow.
Client-safe
Client work can be separated by inbox, domain, token, labels, files, and audit history.
Agent-ready
Each workflow can have its own address and API access without borrowing a human mailbox.
Governed
Approvals, scoped tokens, MFA requirements, and audit settings help keep delegated work under control.
Scale-minded
Volume pricing, higher limits, and team oversight fit agencies and operators managing many inboxes.
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.