FAQ
Onboarding and migration, answered
These are the practical questions people ask before connecting their first production inbox.
Getting started
Do I need my own domain before creating an inbox?
No. You can start by accepting mail through a provided domain. For production traffic, your own domain is recommended so mail reputation and routing are managed per business use.
Can I use Gent without coding?
Yes. The dashboard is a full no-code client for setup, routing, approvals, and day-to-day inbox operations. Start there first, then layer in Claude / ChatGPT (Codex), Hermes, OpenClaw, and other agent runtimes when you want custom behavior.
What is the first thing to configure?
Start by configuring your domain (or use a shared domain), then create an inbox. Connect it by copying the new Gent address into To/CC on existing conversations or by creating a token for direct API clients.
Can I start only with receive and not outbound?
Yes. Inbound handling is immediate and always active. Replies are prepared as drafts for review so a person keeps control before anything is released.
Onboarding friction
I cannot receive mail after adding DNS. What should I check?
Check propagation and sender identity records first. If the domain is new or recently edited, wait for propagation and confirm inbound host/provider verification in dashboard settings.
Should I start with full access or scoped permissions?
Start scoped. Most setups begin with receive and triage plus task-level workflows. Outbound actions are draft-only right now, so start with minimal scopes and expand as needed.
Can one inbox send on behalf of multiple brands?
Not at the same quality level. Most teams use one inbox per delegated function so behavior, reputation, and audit visibility stay clear, especially while release controls are in review.
Migration and coexistence
Will this replace Gmail or Outlook?
No. Gent is designed to sit beside existing stacks and forward to team tools. You can run it as your agent workspace while keeping human inboxes for internal workflows.
Can I keep forwarding rules in place?
Yes, if you already have established human workflows. Gent gives you a place to build explicit rules for what should be handled by an inbox, human, or downstream system.
Can I use one mailbox for support, invoices, and follow-up?
You can, but it usually lowers control. Most teams benefit from context-specific inboxes for clearer routing, permissions, and audit clarity.
Governance and safety
How do I avoid over-automation?
Use approvals for outbound action drafts, apply caps for external actions, and configure sender controls before enabling any autonomous execution.
Does Gent log what happened?
Yes. Gent records action history for inbox activity, tokens, workflow events, and approvals. Use that for incident review and governance checkpoints.
Who can rotate secrets and tokens?
Only authorized workspace users with the right privileges in your dashboard. For multi-user teams, rotate under workspace admin context to limit token exposure.
Billing and limits
What is billed first: inbox or workspace?
The workspace and add-on options define capability. In many cases one workspace includes base operations while specific inbox usage can scale with your plan.
Can I test with one inbox and grow later?
Yes. You can move from early setups to larger capacity and governance controls as automation volume grows.