LC Email System

We’re adding support for a native professional email inbox that lets users send and receive personal business emails (e.g., you@yourdomain.com ) —without needing third-party email services. Key Highlights: Users can create and assign custom email addresses from their domains. Messages will only be visible to the assigned user unless the email is inactive or deleted. Admins can manage address status, forward messages, or delete mailboxes with handling options. DNS and domain verification are handled automatically behind the scenes. This unlocks a full inbox experience natively within the platform—great for client-facing roles, internal teams, or personal business communication.

I would like you to have this feature on highlevel to allow users to select a sending domain for each worflow. Sometimes client has multiple website and funnel domain. If we create workflow and email sequence we might need a different reply email address for each domain. You can just add a limitation of the active sending domain maybe at least 3 or 5, so users will not be abuse this feature.

Currently users still have to login to their domain DNS host and manually add the DMARC TXT record after doing the domain auto config in HL. It would be great (like with the www toggle) if an option existed where users could choose to have the DMARC for an email subdomain also added at the time the other DNS records are being added

One of the things I have seen in many email builders is an automatic spam scoring. As you write out the email (or template), it gives you a score for how likely that is to trigger a spam filter and gives ideas of what you can do to reduce the likelihood of being put in the spam box. This is huge for all of us since any spam warnings that our sub-accounts get also affect the entire account. It could help increase overall deliverability and help all users across the platform.

The way the dedicated domain assignment works right now is that, if you have 2 domains and 2 workflows, the communication load will be split in a round robin fashion between the two, and we don't yet have an option to specify a domain to be used in the workflow's settings. This would be great to have in the near future, so that we can decide in which workflow, which email domain is used.

We’d like to request a feature enhancement for the LC Email System to support the creation of fully branded and professional email addresses. Currently, the system allows us to create email addresses in the format name@post.domain.com . We would love the ability to create and use email addresses in the standard professional format: name@domain.com .

I’ve already set up the dedicated domain, but the email used for sending emails is unable to receive replies, and those responses don’t appear under the conversation tab. And with the new Domain resell feature, this is a must. We don't have dedicated inbox for our main domains and official email adresses.

m posting this publicly because private tickets have gone nowhere, and this issue affects more than just me—it affects every GHL user who uses a custom SMTP provider like Bluehost, and potentially others. Despite repeated back-and-forth with support, Go High Level is refusing to take responsibility for a critical flaw in their email system: there is no built-in throttling feature. For those unfamiliar: Email throttling is a basic and essential function in any CRM platform that sends email. It controls the rate at which emails are sent to avoid overwhelming SMTP servers, triggering spam filters, or getting accounts blocked. Without throttling, emails are blasted out all at once, and servers like Bluehost reject them to protect against spam-like behavior. That’s exactly what’s happening here. I’ve personally spoken with Bluehost support several times. They’ve made it abundantly clear that this is not a problem on their end. In fact, they’ve told me they’ve had multiple calls with other Go High Level users experiencing the exact same issue. Their assessment? GHL’s software is not pacing email sends—and that's the root of the problem. Yet, GHL support keeps pointing to error codes that say “email rejected by host” and trying to pass the blame, rather than addressing the actual cause of the rejection: the system is sending too many emails too fast, with no throttle control. This isn’t a fringe request or a luxury feature. It’s foundational CRM infrastructure. Any platform offering email automation and marketing tools should already have a throttle system in place. That GHL doesn’t is not only baffling—it’s negligent. 📣 To the GHL tech team and leadership: It’s time to stop deflecting and start fixing. You’ve built a powerful platform, but you’re leaving your users exposed with a fundamental oversight that threatens our businesses. If this doesn’t get resolved, many of us will be forced to seek alternatives. This issue needs to be escalated and addressed immediately. If you're a GHL user experiencing random email bounces or rejections using custom SMTP—check your logs. You’re probably affected too. Let’s make some noise until this gets prioritized. – Shiva J Transformational Empowerment Coach www.TheHeartCenteredBeing.com

Provide delivery and spam rate based on the ESP

Have the ability to have a profile picture when we send an email to make it stand out while using ghl as our inbox.