Product

How it works

Run customer email from one verified company domain — organized, AI-prepared, and human-approved. One brand identity for outbound and inbound, AI that prepares every conversation, and a human who sends. Here is the closed loop.

01 Verify your domain

Claim the brand identity you want customers to write to — often hello@ or support@ on your company domain, or a dedicated subdomain — and complete a guided DNS checklist: TXT and DKIM for send reputation, recommended DMARC, and receive readiness when you want the closed loop.

Keep Google Workspace or Microsoft 365 for team and day-to-day mail. ForgeMail runs customer send and receive on that brand identity — you do not need to move everyone’s mailbox.

02 Send as the brand

Use templates with merge tags for transactional mail and campaigns. Delivery status lands in a message ledger; bounces, complaints, and unsubscribes suppress future sends. Compliance footers are injected server-side. Sending can be Ready without pointing MX at ForgeMail — that is send-only.

03 Receive what customers write back

Inbound mail to the customer identity lands in the ForgeMail workspace — not a personal Gmail dump, and not a replacement for your Workspace or Microsoft inbox. Outbound history and inbound threads share one brand identity. Decision Desk and inbound triage require receive on ForgeMail rails; they do not apply to mail that still lands in Google or Microsoft.

04 AI prepares the queue

On the way in, ForgeMail assists with:

Categorization and priority so the queue is a decision list
A short summary before you open the full thread
A brand-voice draft grounded in the conversation

AI artifacts are assistive. Nothing goes to a customer until a human acts.

05 You reply

Edit the draft, send from the same brand identity, and keep thread continuity in-product. Bad addresses stay out of the next send so outbound does not poison the inbox you just organized.

Apply for Beta Access

Also see For founders · Press · Security · Privacy · Terms · Log in