Your sales agent just sent a follow-up to a prospect who requested a quote 72 hours ago. The timing is perfect. The message is personalized with deal context, pricing references, and a clear next step. But the email arrives from [email protected] — and your prospect does not recognize the sender. They do not open it. Or worse, their spam filter catches it before they ever get the chance.
This is the invisible cost of running AI agents on a platform subdomain. The work gets done, but the delivery fails at the last mile — not because the content was wrong, but because the sender did not look like you.
Custom email domains fix this. When your AI agents send from [email protected] instead of [email protected], every outbound message carries your brand, builds your sender reputation, and lands in inboxes the way a message from a real team member would.
Here is how it works, why it matters more than most operators realize, and what happens under the hood when you connect your domain.
Why the Sender Address Matters More Than the Subject Line
There is a hierarchy to email attention. According to research from Litmus and Campaign Monitor, the sender name is the number one reason recipients decide whether to open an email — above the subject line, above the preview text, above everything else.
When your AI agent sends from a branded domain, the recipient sees your company name in the “from” field. That recognition triggers the same trust response as an email from a known colleague. When the agent sends from a platform subdomain, the recipient sees an unfamiliar address from an unfamiliar domain, and the mental calculus shifts from “this is from my vendor” to “this might be automated spam.”
The difference in open rates between recognized and unrecognized senders is not marginal. It is the difference between a 40% open rate and a 12% one. Across hundreds of agent-sent emails per month, that gap compounds into missed deals, unanswered follow-ups, and wasted agent work.
The Deliverability Problem No One Warned You About
Sender recognition is a human problem. Deliverability is a technical one, and it has gotten stricter.
Starting in February 2024, Google and Yahoo began enforcing new authentication requirements for bulk email senders. By November 2025, Google escalated enforcement further — messages that fail to meet authentication standards now face temporary and permanent rejections. Not soft bounces. Rejections.
The requirements are straightforward: every domain that sends email must have properly configured SPF, DKIM, and DMARC records. SPF tells receiving servers which systems are authorized to send on your behalf. DKIM cryptographically signs each message to prove it was not altered in transit. DMARC ties the two together and tells inbox providers what to do when authentication fails.
Here is the part that matters for AI-operated businesses: when your agents send from a platform subdomain, you are sharing that domain's reputation with every other customer on the platform. If another customer's agents trigger spam complaints, your deliverability suffers too. You have no control over it, no visibility into it, and no way to fix it.
When your agents send from your own domain, you own the reputation. Your sending patterns, your engagement rates, your complaint ratios — they are all yours. You can monitor them, protect them, and improve them over time. A custom domain is not a vanity feature. It is a deliverability asset.
What Custom Domains Look Like in Practice
In Palatai, connecting your domain takes about fifteen minutes of active work and up to 48 hours of DNS propagation (though most domains verify within an hour).
The setup lives in Settings, Org, Email, Domains. You add your domain, and the system returns the exact DNS records you need to add. Four records, specifically:
- SPF — a TXT record authorizing the email infrastructure to send on your domain's behalf
- DKIM — a TXT record containing your domain's signing key, so every outbound message can be cryptographically verified
- DMARC — a TXT record that defines your authentication policy and tells receivers where to send compliance reports
- MX — a mail exchange record that routes inbound replies back to your agents
The setup wizard detects your DNS provider automatically — whether that is Cloudflare, GoDaddy, Namecheap, Route 53, or any of nine supported providers — and links directly to the relevant documentation. Each record has individual copy buttons for the name and value fields, because most DNS dashboards use separate input fields and a single “copy all” button would force you to split the string manually.
If your domain already has an SPF record (and it probably does if you use Google Workspace, Microsoft 365, or any email marketing tool), the wizard detects the conflict and shows you the correct merged version. It never auto-modifies your existing record. You make the change yourself, with full visibility into what changed and why.
Once the records are in place, the wizard verifies each one individually against public DNS resolvers. It distinguishes between “found,” “propagating,” and “mismatch” — so you know whether to wait ten more minutes or go back and fix a typo. When all records pass, you send a test email from your domain to confirm the full pipeline works end to end.
After that, every inbox your agents use can be created on your custom domain. Your sales agent sends from [email protected]. Your support agent responds from [email protected]. Your marketing agent sends campaign emails from [email protected]. Every message looks like it came from your team, because it did — your AI team.
The Brand Consistency Argument
Email is not the only channel your AI agents operate on, but it is the one where sender identity is most visible and most scrutinized.
When a prospect receives a follow-up from your branded domain, then visits your website, then gets a calendar invite from your scheduling system — the domain matches everywhere. That consistency signals legitimacy in a way that no amount of personalized copy can replicate from a mismatched sender address.
Consider the alternative: your prospect gets an email from [email protected], clicks through to www.acme.com, and wonders why the domains are different. They Google the subdomain. They find a platform they have never heard of. The trust you built during the sales conversation erodes before the follow-up even gets read.
According to Edelman's research, 81% of buyers say brand trust influences their purchasing decisions. Every email from an unrecognized domain is a small withdrawal from that trust account. Custom domains keep the balance positive.
What Happens to Your Old Subdomain
When you switch to a custom domain, your platform subdomain does not disappear. Existing conversations that reference the old address continue to work — replies are routed correctly, and threading is preserved. But all new outbound messages come from your branded domain.
There is no migration burden. You do not need to update templates or rewrite saved sequences. The change applies at the infrastructure level. Your agents keep doing exactly what they were doing. They just do it under your name now.
The Compliance Dimension
As of March 2026, only 10.7% of domains have full DMARC protection with a strict reject policy at 100% enforcement. The remaining 89.3% are either partially protected or entirely exposed.
Google's Postmaster Tools v2, launched in October 2025, introduced a binary compliance status: Pass or Fail. Partial compliance — having SPF but not DKIM, or DMARC at p=none without a plan to escalate — delivers the same result as no compliance. Your messages get deprioritized or rejected.
When you set up a custom domain in Palatai, the DNS records we provide are configured for full compliance from day one. SPF authorizes the sending infrastructure. DKIM signs every message with a 2048-bit key. DMARC is set with reporting enabled so you can monitor authentication results over time and escalate your policy to quarantine or reject when you are confident everything is aligned.
This is not something your agents figure out on their own. It is built into the domain setup process. By the time your first branded email goes out, the authentication is already in place.
When to Connect Your Domain
The short answer: as early as possible.
Sender reputation is cumulative. Every email your agents send contributes to the reputation of whatever domain they are sending from. If your agents spend their first three months building reputation on a platform subdomain and you switch to a custom domain later, you start from zero on the new domain. The reputation does not transfer.
Connecting your domain during onboarding — ideally in the first week — means every email from day one builds reputation on the domain you actually own. Three months later, your custom domain has a sending history, established engagement patterns, and a clean compliance record that belongs to you.
If you are evaluating Palatai during a pilot, the custom domain setup is part of the first-week onboarding. Your agents will be sending from your domain before the pilot is over.
The Bottom Line
Your AI agents are doing real work — writing follow-ups, responding to inquiries, sending reports, nurturing leads. That work deserves to arrive under your brand, authenticated by your domain, and counted toward your sender reputation.
A platform subdomain is a fine starting point. But the moment you are serious about the emails your agents send reaching the people they are meant for, a custom domain is not optional. It is infrastructure.
Fifteen minutes of DNS configuration. One verified domain. Every email from that point forward carries your name.