LC Email System

Currently you can only send emails from one sending domain per sub-account. It would be great if we could set up a way to have different sending domains for different workflows. For example, internal email notifications in one workflow sent from Domain A and customer facing follow-ups in another workflow sent from Domain B. Currently, this isn't possible, even if Domain B is added to the account as a sending domain. Emails will only be sent from the default domain (Domain A, in this case).

Right now, workflows can only send emails from addresses added to Email Services (SMTP). We need the ability to send emails from any user’s connected 2-way synced inbox (e.g., Outlook or Gmail) directly from the workflow builder. Use case: I’m building a multi-persona system (AI bots as users), each with their own inbox Conversations work fine using 2-way sync But I can’t send workflow emails from these users unless I manually set up SMTP for each, which breaks global config Other CRMs (like HubSpot) allow user-linked emails in workflows—GHL should too Please support user-linked 2WS identities as valid workflow senders.

Currently, in LC emails, every email is a new email. Need to include the email trail when sending outbound emails. The recipient receives separate emails and has to go back to find the conversation in their email inbox. It populates in the conversations thread for us but for the receiver's end it does not.

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.

Right now every time I send out a campaign there are 2 contacts that within seconds show that they clicked a link. However they didn't. It's more than likely a antivirus tool or something that has clicked the link. I haven't had this issue in other email marketing tools. So there must be a way you can filter out or detect only real clicks from real people. Otherwise the click reporting is just wrong.

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

Could we get the ability to place a monthly email-sending limit in the subaccounts? This would be a great way to add revenue for everyone as well - Sort of like the options that we add per sub-account - do like 500, 2500, 5k, 10k - something like this would allow us to offer tiers based on sending volume and slow down sub-accounts so they don't jam up their own sending domains too fast

We want the ability to set an SMTP provider that is only for system emails. A great example is "resend" which is specifically for sending account emails, resets, etc with extremely high deliverability rates. This means that the "default" that we set for the agency for clients to use would not be what sends out password emails in case that gets burned. We would instead set a distinct/additional SMTP provider that we assign to those critical emails and customers would never see in their subaccount.

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.

Product Area: Email (LC Email / Custom SMTP) Priority: High (Deliverability & Compliance) Use Case: High-volume transactional and broadcast email using Amazon SES Summary When using LC Email with Mailgun, GoHighLevel correctly includes RFC-compliant List-Unsubscribe headers. However, when using Amazon SES as a custom SMTP provider, these headers are not included, which creates deliverability and compliance issues for bulk senders. This makes Amazon SES impractical for production email sending despite being a supported SMTP option. Current Behavior LC Email (Mailgun integration) Sends: || List-Unsubscribe: <mailto:...>, <https://...> || List-Unsubscribe-Post: List-Unsubscribe=One-Click -> Gmail/Yahoo display native “Unsubscribe” UI -> Complies with Google/Yahoo 2024 bulk sender requirements Custom SMTP (Amazon SES): -> No List-Unsubscribe headers are sent -> Gmail does NOT show native unsubscribe -> Unsubscribes rely solely on footer links -> Increases spam complaints and suppresses inbox placement -> Fails Google/Yahoo bulk sender expectations Why This Matters (Deliverability Impact) As of 2024, Gmail and Yahoo require bulk senders to: • Support one-click unsubscribe • Include List-Unsubscribe and List-Unsubscribe-Post headers • Provide frictionless opt-out without login or extra steps Without these headers: • Inbox placement is negatively impacted • Complaint rates increase • Sender reputation degrades over time • High-volume senders cannot safely use SES via GHL This affects: • Agencies • Newsletter businesses • Daily senders • High-volume broadcast workflows Requested Enhancement When using custom SMTP providers (Amazon SES), please: Inject RFC-compliant headers into all outbound emails: || List-Unsubscribe: < mailto:unsubscribe@domain.com >, || < https://yourdomain.com/unsubscribe?token= ...> || List-Unsubscribe-Post: List-Unsubscribe=One-Click Allow the unsubscribe URL to: • Respect existing GHL unsubscribe logic • Mark contacts as unsubscribed immediately • Work without authentication Apply this consistently across: • Broadcasts • Automations • Campaign emails This should mirror existing behavior in the Mailgun (LC Email) integration. Additional Context -> Amazon SES fully supports List-Unsubscribe headers -> This feature works correctly today in many ESPs (FluentCRM, Email Octopus, Mail Mint, Sure Contacts etc...) It's already possible to handle bounces via Make.com + SES event notifications. This change would make SES viable as a long-term sending option inside GHL Business Impact for GoHighLevel Adding this feature would: -> Reduce LC Email cost objections for high-volume senders -> Improve deliverability outcomes platform-wide -> Reduce spam complaints and support tickets -> Enable agencies to use SES at scale without compromising compliance -> Align GHL with modern bulk sender standards Closing This is not a workaround request — it’s a core deliverability requirement for custom SMTP usage in 2024+. Parity with the Mailgun integration would unlock SES as a first-class sending option inside GoHighLevel. Thank you for considering this.