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’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.

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.

We are introducing a new AUP Spam enforcement system to improve sender reputation and protect HighLevel’s email infrastructure. Currently, we only take AUP action for high hard-bounce rates (invalid emails, etc.). With this enhancement, we will also enforce AUP when emails are repeatedly blocked for spam-related reasons, even if Email Validation is enabled. Enforcement Logic: 3 spam strikes within a rolling 7-day window → Email sending will be permanently blocked for the sub-account. This block is independent of bounce/AUP hard bounce logic. The block persists even when Email Validation is enabled. Notifications: For every spam strike, we will send: In-app & email notifications to Agency Owner Notifications to sub-account users (same flow as current AUP bounce notifications) When permanently blocked (after 3 strikes), users receive a clear message explaining: Why they were blocked The spam violations detected Recommended next steps (improving content, domain setup, warmup, etc.) Why This Matters: This enhancement: Prevents continued sending of spammy content Protects domain & IP reputation for all HighLevel senders Reduces Microsoft/Gmail spam filtering Ensures higher inbox placement for compliant users Strengthens overall infrastructure integrity Rollout Notes: This will run alongside the existing AUP bounce enforcement. Spam detection will use full provider response messages. UI + notification updates will mirror AUP bounce experience.

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

On a regular basis I have to contact support to ask them to fix or change the sending IP associated with my dedicated sending domains, because Microsoft is blocking the emails. This issue is that Microsoft black lists the Mailgun server IP for the shared server(s). It then takes days, sometimes longer for the issue to be temporarily resolved. Then a few weeks later or sometimes longer it happens again. And it doesn't just happen on one sub-account. Every time this happens my clients get very frustrated that their emails aren't sending and ultimately it is impacting their business. We need a permanent fix for this issue. And purchasing a dedicated IP for the sub account is another expense when they don't send 100,000+ emails per month.

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

SIMILAR TO MAILCHIMP, WE SHOULD BE ABLE TO CHOOSE WHAT FROM NAME WE WANT TO SEND EMAILS FROM, NOT JUST LIMITED TO DEFAULT HEADER

Currently when you can only have a single email service set up per account. This makes it hard for splitting transactional email addresses from marketing email addresses. For example, in my case, I have sub-domains for different email purposes using MailGun. What complicates this even further is that if my client decides that they don't want to receive newsletter or marketing material and unsubscribe, they won't receive any Transaction Emails from me anymore. I do believe that is it best practice to separate your emails between the main domain (for transactional) and the sub-domains (for marketing or newsletters) Although there are some complicated ways around this, it makes it harder for my clients to achieve this outcome. I do understand that there are a lot of rules and regulations when it comes to emails regarding the structure and laws to protect people from spam, that I still don't fully understand. But I would like to suggest the following if it complies: Multiple email services are added with their own DND settings, or at least 2 Email Services with their own DND settings, from which one can be transactional emails for instance, and another for marketing emails. If I client does not want to receive marketing emails I should still be able to send them, for example, an invoice, because the email service being used for transactional emails does not have DND active. And then if they were subscribed to a mailing list but do not want the marketing emails anymore and unsubscribe, the DND settings are active on the email services being used for marketing, so I can then still send them, for example, an invoice because my main transactional email services DND settings are not active.