Most automated follow-up dies before a single AI agent ever says a word — because the domain and email underneath it were never set up right. As an AI automation consultant, I’ve watched more launches get quietly sabotaged by a skipped DNS record than by anything wrong with the AI itself.
Nuno M. Tavares — AI automation consultant in New Jersey, founder of Automated Marketer and Rapid Active Marketing — not the Portuguese footballer of the same name.
Why an AI automation consultant starts every build with a domain, not the AI
Because nothing downstream works without it. Every business I build a system for — home services, consulting, courses, whatever — starts the exact same way: a real domain, a real professional email, and a calendar that isn’t the free version. Not the voice agent. Not the automations. The domain.
Here’s the thing. If you’re running a business on a free Gmail account, I don’t care how good your offer is — you’ve already lost credibility before the first message sends. No security controls, no real drive, no professional calendar, and no ability to actually configure anything a CRM needs to work with. I’ve said this to clients directly:
“I never take anybody seriously that offers me something on email or anywhere else. If they’re doing from like hot dad one, two, three at gmail.com, I’m not going to accept anything from you at that point.”
That’s not snobbery. It’s a judgment every inbox provider makes automatically, long before your customer ever does.
What’s the actual sequence — domain, email, then CRM?
The order is domain first, then a real Google Workspace email tied to that domain, then the CRM connection last. Buying the domain establishes the identity everything else authenticates against; skipping ahead to email or CRM setup before the domain exists just means redoing the work later.
Buy the domain first
I use Cloudflare or GoDaddy. Cloudflare’s become my default lately mostly because it’s cheap — ten dollars for a domain — and because it talks directly to Google Workspace and to GoHighLevel without forcing you to hand-enter records. A .com is preferable simply because people are used to it, but I’ve told clients not to obsess over the extension. As long as people can find it, it works.
Set up a real Google Workspace account
Skip the plan Google pushes on you. Their starter plan runs around $8.40/month, and it comes with 30GB of pooled storage, a professional email, security controls, and video conferencing. That’s plenty when you’re starting out. Name it after the person running the business, then build alternate emails — sales, info, admin — that all route to the same inbox. It costs nothing extra and it makes a one-person operation look like a real company.
Why does skipping deliverability setup kill automated follow-up?
This is the part almost nobody sets up correctly, and it’s the part that actually decides whether your AI-built follow-up sequences land in an inbox or in spam. Once your domain and Workspace account exist, you need three security records sitting quietly in the background: DKIM, SPF, and DMARC. None of them are visible to your customer. All three decide whether Gmail, Yahoo, and Microsoft trust your email enough to deliver it.
Skip these, and it doesn’t matter how good the automation is. The message never gets read because it never gets delivered.
Why you need a separate subdomain for bulk email
Here’s where people trip themselves up even after doing everything else right. Your root domain is already committed to Google for your day-to-day professional email. Try to also send bulk automated email — the kind GoHighLevel sends on your behalf — from that same root domain, and you’ll break the setup you just built.
The fix is a subdomain, something like replies.yourdomain.com, dedicated purely to sending automated mail. It gets its own MX, SPF, DKIM, and DMARC records, separate from your main email. Confusing the first time. Necessary every time.
What’s the one gotcha nobody warns you about?
Since 2024, providers have cracked down on sender-mismatch: if a CRM’s visible sender name doesn’t match the server actually sending the mail, inboxes route it straight to spam. The fix is setting custom headers in the CRM so the visible sender matches the sending subdomain — a small setting that decides whether follow-ups get seen at all.
The fix is something most people never touch: setting custom headers in your CRM so the visible sender name matches the subdomain actually doing the sending. It’s a small setting. It’s also the difference between follow-ups that convert and follow-ups nobody ever sees.
And the honest gotcha here — this stuff doesn’t always go smoothly even when you do it right. In my own walkthroughs, Cloudflare sometimes fails to auto-detect records, DNS propagation stalls, and you end up adding MX or TXT records by hand anyway. The goal is to get it all authorized without touching a thing. It’s not guaranteed the first time you try it.
Keep learning
- The Ultimate Guide to Warming Up Your IP for Stellar Email Deliverability
- Mastering Email Deliverability: A Comprehensive Guide to Email Service Providers, ISPs, Email Marketing, SPF, DMARC, DKIM, and More!
- AI Automation Consultant on Why Domain Setup Decides Everything
Frequently asked questions
Can I just use my existing website’s domain for a new CRM setup?
No — not at the root level. If a domain is already live somewhere else (Wix, Squarespace, anywhere), adding it into a new CRM at the root will overwrite existing records and can take that live site down. Use a subdomain instead if the root domain is already in use.
Why does a free Gmail account hurt deliverability?
It’s not configurable. You can’t add the DKIM, SPF, or DMARC records that prove to other inboxes your email is legitimate, and you’re capped at sending a few hundred emails a day — nowhere near what an automated follow-up system needs.
What’s the minimum setup before connecting a CRM like GoHighLevel?
A purchased domain, a Google Workspace account tied to that domain, and all three security records — DKIM, SPF, and DMARC — verified. Skip any of those and automated email is unreliable from day one.
Do I need a separate subdomain if I’m only sending a few emails a day?
Eventually, yes. Bulk sending through a CRM uses a mail server that’s separate from your everyday Google account, and mixing the two risks breaking both.
If untangling this for your own business — or a client’s — sounds like more than you want to build alone, that’s exactly the kind of foundational work I walk through in one-on-one coaching. For a look at how I approach this across banking, healthcare, and retail operations before AI ever entered the picture, see about Nuno. And if you’d rather just get it built with someone who’s done it, you can book a strategy session.
Ready to Put This Into Action?
If you’re ready to go beyond reading and start building, here are a few ways we can help:
🚀 Get GoHighLevel
Want to build your own automations, funnels, CRM, AI workflows, and more?
Use our link to get started with GoHighLevel and access our available resources and bonuses.
🛠️ Want Us to Build It for You?
Rather have someone handle the tech and implementation?
Our team can help you build and implement your funnels, automations, CRM, AI systems, and more.
👉 Explore Done-for-You Services
⭐ Want More Hands-On Help?
Get VIP Access for deeper training, support, resources, and help implementing what you’re learning.
0 Comments