Prompt13 · AI resources for GoHighLevel agencies
ESEN

Guide

Email in GoHighLevel: Sending Domain, Header and Reply Forwarding Without Touching DNS

GoHighLevel has three fields that look the same and are not: the branded domain, the dedicated domain and the header. Mixing them up breaks delivery or reply tracking. Here is what each one does and the native shortcut almost everyone misses.

Three fields, three jobs

  • Branded domain (Business Profile): serves funnels, sites and links. You point it with a CNAME to the GHL host. A subdomain like go.yourdomain.com is the safe option. Use the root only if that domain is exclusive to GHL.
  • Dedicated domain (Email Services): the subdomain the email is sent from. The convention is lc., for example lc.yourdomain.com. GHL creates its SPF, DKIM, DMARC and MX (Mailgun) records there and improves delivery to the primary inbox.
  • Dedicated header (Sender name and email): what the recipient sees. Keep the sender email on the same domain as the organization (for example hello@yourdomain.com) so DMARC sees it as aligned with lc.yourdomain.com.

The shortcut almost everyone skips

Before you set up email forwarding with an outside service or touch your domain's MX records, look at the Reply & Forward tab in Email Services. GHL copies every reply to the client's personal inbox and also keeps it in Conversations. Zero DNS, zero new mailbox.

Rules for it to work:

  1. The Forwarding Address must be on a different domain than the sending one (loop protection). The client's current email works.
  2. Leave the Reply Address empty. Filling it in breaks thread tracking in Conversations; GHL's own note warns about it.
  3. Ignore the "forward to assigned user" toggle if the client is a single person: entering the address directly is more reliable.

What it covers and what it does not

This covers email sent through GHL: workflows, campaigns and conversations. Replies land in Conversations on their own because of the dedicated domain, and the forwarding mirrors them to the real inbox.

If someone writes to that sender address from outside GHL, there is no mailbox behind it unless a real one or an external forward exists. That external forward is only needed if you want to receive the domain's email outside GHL.

Recommended order

  1. Branded domain on a subdomain (CNAME).
  2. Dedicated domain with the lc. prefix and its records.
  3. Header with the sender email on the organization's domain.
  4. Reply & Forward with the client's inbox, no Reply Address.
  5. Test: send an email to an account of your own, reply, and confirm it reaches Conversations and the inbox.

Related

Post-lead nurture sequenceCold email generator (GHL)GoHighLevel API

FAQ

Frequently asked questions

Do I need to set up external email forwarding to receive GHL replies?+

Not for email sent from GHL. The Reply & Forward tab copies replies to the client's inbox and keeps them in Conversations, with no extra DNS.

Why shouldn't I fill in the Reply Address?+

Because it breaks thread tracking in Conversations. GHL warns about it in the field's own note.

Which domain do I use on the sender email?+

The same as your organization, not the sending subdomain. That way DMARC sees it as aligned with the dedicated domain and delivery improves.