LC Email System

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

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.

Currently you can only have 1 active dedicated domain at a time. This can be frustrating as you may have different dedicated domains for different functions such as xyz@support.xyz.com , xyz@bookings.xyz.com , xyz@marketing.xyz.com . If we have the ability to have multiple dedicated domains at once it can smoothen the process and increase professional communications for clients

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

❌ The Glaring Problem: HighLevel allows multiple SMTP servers at the sub-account level, but only one can be set as the default for outbound emails. This creates major limitations for companies where users each have their own email - which is 99.99% of companies - and is near enough completely redundant. If a company has 100 employees (e.g. charlie@, rebekah@, joanne@) and several shared addresses (e.g. info@, billing@, sales@), all emails must be sent through one default SMTP or dedicated domain. If the default SMTP is charlie@, why would Rebekah send through it? If it’s info@, why would Charlie email the lead he's just spoken to on the phone through it? Yes, we have dedicated domains. Dedicated domains are great for mass campaigns to protect the root domain’s sender rep - but terrible for personal outreach, and they almost always end up in spam. If it’s a dedicated domain for bulk - why would Joanne send a 1:1 sales email that NEEDS to land, FROM HER, through it? For SDRs or anyone doing 1:1, emails need to come from the actual user’s address to ensure deliverability, and appear professional and trustworthy. SMTP is the only reliable option for this - but we can only use one SMTP across 100 employees... Why?! ✅ Suggested Solution: Allow each user to connect their own SMTP/email service. Emails sent from that user should automatically route through their configured SMTP provider, offering full control and accountability - with the option to override if needed. If no match is found, the system should fall back to the company’s default SMTP, or default sub-account email address through their dedicated sending domain. Additionally, allow admins to assign access to specific shared addresses (e.g. sales@, support@) to certain users or teams. For example, sales team members could be granted access to send and receive from sales@ - without exposing it to the rest of the company. This would solve so many issues with the current, deeply flawed email service. Having one SMTP per sub-account makes zero sense when every user has their own inbox, and using a dedicated domain for 1:1 SDR emails is deliverability and conversion suicide.

At this time, cold inbound email is delivered to the "universal inbox" only if addressed to the Default Dedicated Domain. If someone replies to an email sent from a Dedicated Sending Domain it is delivered to the Conversations tab. But if they save that email address to their contact list and write a new email using the address in their list the resulting email will be lost, it will not be delivered. This has a predictable lost revenue potential where people who reach out later (rather than replying to email marketing immediately) are lost to the CRM/automations/nurturing. Certainly if the email is forwarded from our Contact to another email address or a friend and a cold email is sent to us from that other address we will not receive the message. Our nurturing campaign worked, but we failed to capitalize on the opportunity. In my set up (see graphic) any email sent to {{addressee}} @ email.thebaldguymarketing.com will not be delivered while emails addressed to {{addressee}} @ thebaldguymarketing.com will arrive in the Conversations view. I would like to take advantage of the options provided by having separate Workflow, One-One, Campaign, and Bulk domains. We could have four different Dedicated Sending Domains if we could be sure that emails addressed to any of them would be delivered to Conversations. What is the point of having multiple Dedicated Sending Domain options if any cold inbound emails will be lost in cyperspace? The way it is now we should have only one (the burner for cold outbound bulk email) and keep all other email on the Default Dedicated Domain. The behavior I would like to see: any email addressed to anyone at any dedicated sending domain established with correct MX and TXT records (DMARC & SPF) for that subaccount/location should be delivered to the inbox.

GoHighLevel Feature Request – Critical for Multi-Brand Agencies Many of us are running multiple brands or clients under one sub-account with separate dedicated sending domains. But currently, GoHighLevel doesn’t allow us to lock a specific sending domain per workflow or campaign. Even when settings are correct, emails often go out from the wrong domain unless every step is manually overridden. This creates confusion for clients, damages brand trust, and wastes time. This is not just a nice-to-have – it's essential. We urgently need the ability to set a default sending domain at the workflow or campaign level. Please prioritize this. Agencies are asking for it, clients are asking for it, and it’s becoming a blocker for scaling with GHL. If this affects you too, speak up in the comments. Let’s push this forward.

Whenever ANY malicious actor sends an email to your LC Email sending domain, that email will appear in the Conversations Tab. Whether that email contains malware or phishing links, it will still show in the Conversations Tab. If you have a Contact in your CRM which these malicious emails may come from, it will trigger a reply, seemingly making the email seem legit. If you have Email Forwarding enabled inside HL, these malicious emails get forwarded via your LC Email sending domain, and in the case of it going to your Gmail account, gets properly flagged as Spam or Malicious, but now your LC Email Domain is receiving these bad signals, giving it a bad Reputation and it hurts your Deliverability. In Gmail these emails properly get flagged as spam...they go straight to the junk folder. But not inside the CRM platform. Add proper Spam protection like Gmail has to ensure malicious actors do not piggyback off of our LC Email sending domains to get their email delivered. I'm told this should be a feature request, but LC Email which is Mailgun, should have this by default seeing as Mailgun has inbound spam filtering available as a setting.

I have clients that ONLY use LC Email for email service, I'd like to be able to create a trigger or feature in the user profile that IF an incoming email is sent "To:" them (if not assigned) gets assigned to them.

We need a way for contacts to resubscribe to our email list if they unsubscribe via the new LC email unsubscribe link. This will be useful for agencies so we can test the unsubscribe link and resubscribe after testing. It will also be useful to give contacts who unsubscribe the option to resubscribe in case it was an accident or if they change their mind. There could be an option to resubscribe given immediately after someone unsubscribes. This is a very common way to do it. There should also be another way to do it if the contact wants to be resubscribed and no longer has access to the email.