Playbook · Mail

Send email from your own domain — and actually land it.

By default your emails come from mail.loopi.social. That works, but it isn't your brand. This play moves your profile to mail.yourbusiness.com so every email comes from you — better recognized, better delivered, and replies that reach your real inbox. A few DNS records, one setting, done.

What it does for you

Right now your subscribers see mail.loopi.social in the From line. This makes every email come from your own brand instead. By the end you'll have:

• Your domain in every From line. Email arrives from hello@mail.yourbusiness.com, not a shared Loopi address — recognizable, trusted, yours.
• Better deliverability. Proper SPF, DKIM, and DMARC for your own domain is what inbox providers look for to trust your mail.
• Replies that reach you. A confirmed reply-to address means when a subscriber hits reply, it lands in your real inbox.
• A clear "Ready to send as yourself" state. No guessing whether setup is complete — the profile tells you.

The play

Add a sending domain, add the DNS records Loopi gives you, let it verify, set a reply-to. Your readiness state flips from "sending as Loopi" to "Ready to send as yourself."

You pick the domain. Loopi generates the SPF, DKIM, and DMARC records; the agent reports the exact name, type, and value for each so you can paste them into your DNS provider (GoDaddy, Cloudflare, Namecheap, wherever your domain lives). Verification is automated — Loopi polls the DNS and flips the status the moment the records resolve.

What Loopi handles for you

• Generates SPF, DKIM, and DMARC records for your sending domain — the exact values needed for your Loopi-managed SES infrastructure.
• Verifies before enabling sends — the domain stays in a "pending" state until all three records resolve correctly. Loopi will not send from an unverified domain, so you can't accidentally ship from a half-configured setup.
• Separates reply-to verification via mail.requestReplyToChange — a one-time confirm email so that subscriber replies reach your real inbox, not a sending-only address. This is its own step because the address you send from and the address replies go to are often different.

Compliance and sending infrastructure are profile-level settings only — they are not overridable per email, which keeps them as safety rails rather than something that can be misconfigured on an individual send.

How to do it with Loopi

Hand your agent three things. It produces three confirmations.

The prompt

Replace mail.yourbusiness.com and yourbusiness.com with your actual domains, then hand this to any agent with Loopi MCP connected:

I want to send email from my own domain instead of mail.loopi.social.
My desired sending domain is mail.yourbusiness.com.

1. Call account.getOrCreateSendingDomain({ domain: "mail.yourbusiness.com" })
   and report the exact DNS records I need to add (SPF, DKIM, DMARC) — name,
   type, and value for each.

2. Check account.getSendingDomain({ domain: "mail.yourbusiness.com" })
   until the status is "verified". Report when it is, or tell me which
   record is still failing so I can fix it.

3. Once the domain is verified, call mail.getSettings to confirm the
   current fromAddress. Then call mail.updateSettings to set the
   fromAddress to hello@mail.yourbusiness.com (or whichever address
   I prefer on that domain).

4. Call mail.requestReplyToChange({ replyTo: "hello@yourbusiness.com" })
   so replies from subscribers reach my real inbox. Tell me what
   confirmation step I need to complete.

5. Report the final readiness state: is the profile showing
   "Ready to send as yourself"?

Connect Loopi to your AI agent and run this play →

Next play

A verified sending domain handles the infrastructure side of deliverability. The copy side is equally important. Land in Gmail Primary covers the body and subject rules that keep your emails out of the Promotions tab once your domain is live.