ForgeMail runs customer-facing email on your domain through one AI-prepared, human-approved workflow. Keep Google Workspace or Microsoft 365 for team mail; route hello@, support@, or a dedicated customer subdomain through ForgeMail.
For founder-led teams that need hello@ and support@ to behave like an operating queue, not a shared inbox.
AI prepares the brief and draft. You approve every reply, dismiss the item, or move it into follow-up.
Coexistence
hello@, support@, or mail.company.com.Companies that send customer email from hello@, support@, or a product domain. ForgeMail is free during beta with setup help included — claim your domain, publish DNS, and go live with a human-approved workflow.
Connect a customer identity on your domain, start the conversation, turn replies into decisions, and keep a human in control — one operating sequence on your brand. Keep Google Workspace or Microsoft 365 for team mail.
Publish the DNS records ForgeMail gives you for customer send and receive. Day-to-day Workspace or Microsoft mailboxes stay where they are.
Send transactional or campaign email from your verified brand address, with templates and compliance handled in the workflow.
Inbound messages are grouped by category, priority, and next action instead of arriving as a flat inbox.
Review the AI brief and draft, edit when needed, then send, dismiss, or follow up.
The product is not just an AI reply box. It covers the upstream setup and downstream review work needed to send and receive responsibly.
The operating surface for customer email on your domain: a focused queue for messages that need judgment, with AI brief and draft ready before you approve a send. Covers mail received into ForgeMail — not an overlay of Workspace or Microsoft 365 inboxes.
Transactional and campaign send from the same verified domain.
Find threads and ground drafts from confirmed company knowledge.
Domain email is high-trust infrastructure. ForgeMail keeps humans in the send path and scopes DNS to customer-facing identities — not a takeover of employee mail.
No customer reply leaves without an explicit human send.
Records are for customer-facing send and receive identities you choose.
Workspace and Microsoft 365 employee mailboxes stay where they are.
Unsubscribe and physical-address footers injected server-side on outbound.
Domain verification with DKIM and recommended DMARC for brand send.
Full controls on Security.
We review applications manually, then walk founding workspaces through a short path from claim to first customer-facing send.
Start with the customer identity you want on ForgeMail.
Copy the records ForgeMail gives you for send (and receive if you want the loop).
Confirm authentication so branded mail can leave as you.
Send-only, or inbound with Decision Desk triage — your call.
Prove the loop with one customer-facing address before you scale.
Run the queue: AI-prepared, human-approved replies on your domain.
The setup flow walks through domain, DNS, verification, sender, test, and done. Sending can be Ready while Receiving stays Not configured — that is send-only. Decision Desk and inbound triage apply only once receive is on ForgeMail rails. Receiving MX is for your customer identity — not a migration of Google Workspace or Microsoft 365 mailboxes.
Beta is free for accepted workspaces. Enforced caps keep the rails healthy; when paid plans arrive, expect volume-based pricing — not a maze of seat add-ons — and advance notice before any paid conversion.
Per-account defaults during beta. Need more headroom? Tell us in your application or after you are onboarded.
| Limit | Beta default |
|---|---|
| Domains | 2 claimed domains |
| Monthly sends | 10,000 / UTC month (2,000 / day burst) |
Organized, AI-prepared, and human-approved — apply for a Founding Workspace, then claim your domain with setup help.