LC Email System

As it involved data privacy, so the screenshot will blur the personal information, today one of our client feedback they received an email in CRM system, which is not their client. I checked, it is another subaccount's customer replied a form email, but it goes to their conversation. I believe this may cause serious senstive information leak, so I contacted the zoom call directly. The explained reason is because both subaccounts using the same agency level default email domain, and the email is both no-reply@agencydomain.com , so the system won't know which account to go to, then it will go to a random one. Immediately I give a suggestion, actually you do not need to use no-reply@agencydomain.com , you can use a part of location ID + the business name@agencydomain.com , or you can use no-reply-[hashcode-of-location-ID]@ agencydomain.com to send out the email, then when customer reply, it is easy to know it is for which subaccount. The support suggest us to create delicated domain for each client, I told him if our clients quantity is small, we may do that, when the quantity is huge, how to do that? It is also not possible to expect all the client to do this, as long as not all client applied their own delicated email domain, this risks persist. I hope you can consider my suggestion seriously as potential data leak for any CRM system is big issue. Add: since the delicated domain is so important, it shall be added to the top of launchpad so at least customer know it is first priority. Although many may still not do it.

LC emails ending up in junk and GHL support has no recommendations or solution

Something is wrong with 2-way sync and/or dedicated domains. When you send emails via workflows and automations, and then the contact you emailed replies, their reply email does not come back to your email inbox. It only comes back into the CRM. This is a major issue. There should NEVER be a scenario when a contact replies to one of my emails, and I don't actually receive the email in my email client inbox. I've had this happen myself, and I've had this happen with my customers in their sub-accounts. I've submitted a support ticket for this and reached out to support multiple times, but no one seems to be able to help. This needs resolution immediately.

Using automation, my emails are showing chris= shocialyfe.fun on behalf of my actual email domain. See attached screenshot. On gmail the from shows correctly, but in Outlook it shows a very long from with "on behalf of _____". It's my belief that this is affecting my open rate. I tested with 2 customers and they never received my emails, yet Highlevel stated the emails were delivered.

NOTE: THIS BUG IS MARKET PREVIOUSLY AS RESOLVED! THIS IS FALSE. THIS IS ON GHL AND GHL NEEDS TO FIX THIS! This is what it says when adding a subdomain and connecting with LC. However, currently, everyone who does this if failing MS Office users. I spent hours reading and "on behalf of" topic and could not find a solution. 99% of our clients use outlook, hence we need to fix how this looks on Outlook. 1- Fix "on behalf of" for the root domain email 2- Show header text (Contact < contact@go.domain.com > instead of contact@go.domain.com ) at the top of the email - should be fixed for both subdomain emails and the root one

Currently attachments are not forwarded when using the "forward" feature in the "settings" of the "email services" on location level. That doesn't make sense, the full email including all attachments should be forwarded instead.

Bounce stats in Agency dashboard for subaccounts do not match the bounce rates within the subaccount when looking at bounce stats in workflows.

It's really frustrating when a client had previously unsubscribed from our newsletter and then when they try to reset their password it is not delivered. Or if they place another order, the delivery and receipt are not sent. This is a major issue. Emails with important information like this should be sent regardlesss of their previous unsubscribe.

Email replies are not staying within the email thread that they were replying to but instead are starting a brand new email thread in the lead’s inbox. This is unorganized and appears unprofessional, we need a fix ASAP!

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