Your automated emails are quietly dying in spam folders and you probably don't know it. Here's exactly why — and how to fix it in under 20 minutes.
Gmail was built for personal email — one person writing to another. It was never designed to send hundreds of automated sequences. When you connect your Gmail to GHL and let it fire your welcome emails, follow-up sequences, and booking confirmations, you are fighting against every spam filter on the internet.
The worst part: you don't get an error. GHL says "sent." Gmail says "sent." But her inbox says nothing at all. The message lands in spam, in promotions, or gets silently dropped. She never saw your follow-up. She never got your booking confirmation. She thinks you ghosted her.
This is one of the most common reasons photographers tell me "my automations aren't working" — and the fix takes about 20 minutes.
Google limits personal Gmail accounts to approximately 500 outgoing emails per day across all sends combined — that includes everything you send manually AND everything GHL sends on your behalf. The moment your automation volume pushes you over that number, emails stop delivering entirely. No bounce notification. No error in GHL. They just disappear. If you are running a welcome sequence, a follow-up sequence, and a pre-session prep sequence simultaneously across multiple active clients, you can hit 500 faster than you think.
Hard limit: ~500 emails/day on personal GmailEvery major spam filter — Gmail's own, Microsoft's, Yahoo's, Apple Mail — is trained to detect bulk and automated sending behavior. Repeated identical messages sent from the same address to many recipients in a short window is a textbook spam signal. When GHL fires your inquiry welcome email to 20 new leads in a week, every single one of those sends looks suspicious to spam filters when it comes from a personal Gmail address. The filters don't know it's your studio. They see mass identical sends from a personal account and flag them.
When you send from Gmail, your messages go out through Google's shared sending infrastructure alongside billions of other Gmail users — including spammers, phishers, and scammers who use Gmail specifically because it is free and easy. Receiving mail servers track the reputation of sending IP addresses. If Google's shared IPs get flagged because other Gmail users are sending spam, your perfectly legitimate studio emails get caught in the same net. You have zero control over your sending reputation when you use Gmail. When you use your own domain, your reputation is entirely yours to build and protect.
These are three email authentication protocols that receiving mail servers check before deciding whether to deliver your message. SPF verifies that the server sending the email is authorized to send on behalf of your domain. DKIM adds a cryptographic signature that proves the message wasn't tampered with. DMARC tells receiving servers what to do if either check fails.
When GHL sends an email "from" your Gmail address, the actual sending server is GHL's infrastructure — not Gmail's. That mismatch between the "from" address domain (gmail.com) and the actual sending server is a major authentication failure. Spam filters see it immediately. When you use your own domain email with properly configured DNS records, everything aligns perfectly. GHL is authorized to send on behalf of your domain. The signature matches. DMARC passes. The email lands in the inbox.
Beyond the technical failures, consider how it looks. A client submits an inquiry to "Moonlight and Lace Boudoir" — a professional studio with a beautiful website. Then she gets an automated email from yourname@gmail.com. That mismatch between the professional brand experience and the personal Gmail address is a trust signal failure. Some clients will assume it is spam or a phishing attempt. Others will just wonder why a real business is using a Gmail address. Either way, it undermines the brand experience you worked hard to build. Your domain email is part of your brand.
You don't need to understand how these work at a technical level. You just need to know what they are and why they matter — and then follow the setup steps below to configure them correctly.
SPF (Sender Policy Framework) is a DNS record that says "these are the servers allowed to send email on behalf of my domain." Think of it as a guest list at the door. When a receiving mail server gets an email claiming to be from you@yourstudio.com, it checks your domain's SPF record to see if the sending server is on the list. If GHL is not on your list, the email fails the check and is flagged as suspicious. Setting up GHL's SPF record adds GHL to your authorized senders list.
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every email your domain sends. The receiving server checks the signature against a public key in your DNS records. If the signature matches, the server knows the email actually came from you and wasn't modified in transit. Without DKIM, receiving servers have no way to verify the email is authentic. With it, every email you send carries a verified seal of authenticity.
DMARC (Domain-based Message Authentication, Reporting, and Conformance) tells receiving mail servers what to do when SPF or DKIM checks fail. Do you want them to reject the email, quarantine it (send it to spam), or just monitor and report? DMARC also enables reporting so you can see if someone is spoofing your domain to send fraudulent emails. A basic DMARC policy set to "none" is the starting point — it lets you monitor without blocking anything. You can tighten it over time once you have confirmed everything is configured correctly.
SPF = who is allowed to send. DKIM = proof the email is real. DMARC = what to do if either check fails. All three need to be configured for your domain before GHL's emails land reliably in inboxes. GHL walks you through the specific records to add — it takes about 15 minutes in your domain registrar (GoDaddy, Namecheap, Cloudflare, or wherever your domain lives).
yourstudio.com. Not your full email address, just the domain. GHL will generate the DNS records you need to add.@ for your root domain or a specific subdomain like mg), and the Value/Content (the long string GHL provided). Save each one.hello@yourstudio.com or deanna@yourstudio.com. Go to Settings → Business Profile and update the email there. Also update it in any individual workflow email actions that have your old Gmail address hardcoded._dmarc and the value v=DMARC1; p=none; rua=mailto:you@yourstudio.com. The p=none means monitor only — nothing gets blocked. This is the safe starting point. You can tighten it to p=quarantine or p=reject later once you have confirmed all your legitimate sending is properly authenticated.GHL will give you the exact values — these are the record types and what each one does so you know what you are adding and why.
| Record Type | What It Does | Where To Add It |
|---|---|---|
TXT — SPF |
Authorizes GHL's servers to send email on behalf of your domain. Prevents spoofing and passes the SPF check on receiving servers. | Your domain registrar's DNS management. Host is usually @. |
TXT — DKIM |
Adds the public key that receiving servers use to verify GHL's cryptographic signature on every email you send. | Your domain registrar's DNS management. Host is a specific subdomain GHL provides — usually something like mailo._domainkey. |
CNAME |
Points a subdomain of your domain to GHL's sending infrastructure so tracking links and unsubscribe pages work correctly under your domain. | Your domain registrar's DNS management. Host is a subdomain GHL specifies — usually email or mg. |
TXT — DMARC |
Tells receiving servers what to do if SPF or DKIM fail. Start with p=none to monitor. Tighten to p=quarantine or p=reject later. |
Your domain registrar's DNS management. Host is always _dmarc. |
If your domain DNS is managed through Cloudflare, make sure the CNAME record is set to DNS only (gray cloud) — not proxied (orange cloud). Proxying a CNAME record for email sending breaks the authentication chain. Everything else can stay proxied — just not the email-related CNAME.
GHL has a default "from" email in Business Profile settings, but individual workflow email actions can have their own "from" address hardcoded. If you built your workflows when Gmail was connected, every single one may still say yourname@gmail.com. Go through every workflow email action and update the from address after you switch to your domain email.
DNS propagation takes time. Most registrars update within 15-30 minutes but some take longer. If you add the records and immediately hit Verify in GHL and it fails, do not panic and do not delete and re-add the records. Wait 30 minutes and check again. Deleting and re-adding records during propagation causes more problems than it solves.
If your DNS is on Cloudflare, the orange cloud on the CNAME record will break your email authentication. Every other record can be proxied — the email CNAME must be DNS only. It is an easy thing to miss and it causes the DKIM verification to fail silently.
SPF and DKIM are what GHL requires. DMARC is technically optional but skipping it leaves a gap. Without DMARC, anyone can spoof your domain and send fraudulent emails that pass SPF and DKIM. A basic p=none DMARC record takes 60 seconds to add and closes that gap permanently.
If you set DMARC to p=reject before confirming all your legitimate sending sources pass authentication, you risk having your own emails rejected. Start with p=none, monitor for two to four weeks, confirm everything passes, then move to p=quarantine, then p=reject. Rushing this step can break your email sending entirely.
When you switch from Gmail to a brand new domain email address, the sending reputation for that domain starts at zero. Receiving mail servers have never seen it before and will treat it with some skepticism at first. This is normal and temporary — but it means you should not immediately blast hundreds of emails the day you switch.
For the first two to three weeks after switching, let GHL's normal automation volume do the warming naturally. Inquiry welcome emails, follow-up sequences, booking confirmations — all of that sends at a reasonable volume that signals to receiving servers that this is a legitimate sender. Reputation builds over time through consistent, low-complaint sending.
What you should avoid in the first few weeks: large one-time broadcast emails to your entire contact list. If you have 500 contacts and you send a campaign to all of them on day one of your new domain email, you spike the volume before the domain has established trust. Save the big campaigns for after a few weeks of normal automation sending has warmed the domain up.
Send a test email from GHL to a Gmail address you control. In Gmail, open the email, click the three dots in the top right, and select "Show original." Look for the authentication section near the top. You want to see SPF: PASS, DKIM: PASS, and DMARC: PASS all in green. If you see those three, your email is fully authenticated and will land in inboxes correctly.
_dmarc with p=none to startYou can have the most perfectly written follow-up sequence in the world and it means nothing if it ends up in spam. Twenty minutes of DNS setup is the difference between automations that silently fail and automations that actually work. Do it once. Verify it. Move on. Your emails will land — and so will your bookings.