Email System

Formal Complaint: Unsubscribe Requirements, Customer Autonomy, and Inadequate Technical Support I find this response deeply disappointing and frankly unacceptable. I am a paying HighLevel client, not a volunteer product tester submitting ideas for features that may or may not be considered someday. I am raising a legitimate concern about how your platform treats businesses and their subscribers. I have invested considerable time and resources into building a professional email infrastructure, including dedicated sending domains, branded email templates, and a fully functioning custom unsubscribe system integrated with HighLevel's own DND functionality. My unsubscribe system works. My subscribers can unsubscribe. HighLevel correctly records their decision. Yet your platform continues to display a warning that my emails are missing an unsubscribe link. Your proposed solution is to add HighLevel's native unsubscribe link, which may expose my subscribers to an intrusive questionnaire that I find completely inappropriate for my brand. Why should HighLevel dictate the questions my subscribers encounter when they simply wish to unsubscribe? Subscribers should be able to withdraw their consent without being subjected to an experience designed by a third-party software provider that I have explicitly chosen not to use. I understand and support legitimate email compliance requirements. I expect HighLevel to meet those requirements and provide the technical infrastructure necessary to protect deliverability. But I strongly object to presenting HighLevel's own interface and questionnaire as though they were inseparable from industry compliance. Even more concerning, your support representative was unable to provide a definitive answer about whether the persistent warning affects my domain reputation, email warmup, or deliverability. These are fundamental technical questions about your own platform. They should not be redirected to an Ideas Board. I am asking HighLevel to take responsibility for a contradiction in its product: You officially support custom unsubscribe workflows. Your system successfully processes those workflows. Your email editor nevertheless fails to recognize them. Your suggested workaround undermines the very customization your platform claims to support. This is a product and customer-experience issue that deserves technical investigation and a clear resolution. I expect this concern to be escalated to the appropriate product and email deliverability teams, with a substantive explanation of how paying clients can maintain their own branded unsubscribe experience while satisfying HighLevel's validation and deliverability requirements. I am not requesting permission to customize my brand experience. I am asking HighLevel to support the functionality it already advertises and to stop treating a legitimate customer concern as an optional feature request. Please escalate this complaint and provide a meaningful response. Lana Elco

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.

After a month of troubleshooting I finally learned that the 2way sync with Outlook only supports the native version of Outlook, not the desktop version. This is a great disappointment and was a huge waste of hours of troubleshooting with the support team. (At least this limitation should be noted clearly where the sync settings are located.) This ability to sync was one of the key items I looked at before joining GHL and now is not able to function.

Most of the system generated emails (eg for new contact created or appointment scheduled) are ugly, not translated and I cannot find a way to turn them off. Please let us customise all the system generated emails.

One click “Export statistics” that would export an XLSX with multiple sheets. Campaign Performance (table of stats) Opens Performance (list of open email addresses, contact names, company names, event timestamp) Clicks Performance (list of click email addresses, contact names, company names, link clicked, event timestamp) Or if Excel workbook is too fiddly, separate csv export button as you have now, but with the option to select the fields you want in your export.

Problem HighLevel currently treats Email DND as a global suppression state. If a contact unsubscribes from marketing email, Email DND also prevents transactional and operational workflow emails from being delivered. HighLevel Support confirmed this behavior under Ticket GHL-6446254 and confirmed there is currently no supported method to exempt transactional/operational workflow emails from Email DND. This makes it difficult to maintain separate consent states for marketing communications and transactional/operational communications. Example A customer submits an application or service request and separately opts out of marketing. The business should stop sending newsletters, promotions, nurture campaigns and other marketing email. However, the customer may still need to receive: Application/form submission confirmations Document requests Application or account status updates Appointment confirmations/reminders Transaction receipts Service-related notices Customer-requested communications Other non-promotional operational communications Under the current architecture, marketing unsubscribe can prevent these operational messages as well. Requested Enhancement Please add separate email consent/suppression states for: Marketing Email Transactional / Operational Email Workflow email actions should be configurable as Marketing or Transactional/Operational. If a contact unsubscribes from marketing, HighLevel should suppress marketing email while continuing to permit legitimate transactional/operational communications. Ideally, HighLevel should also maintain auditable consent information including consent/withdrawal status, date/time, source and communication classification. Transactional/operational email should also support appropriate footer behavior rather than automatically using the same marketing-unsubscribe mechanism. Business Impact Businesses need to respect marketing opt-outs without inadvertently terminating communications necessary to service an application, appointment, transaction, account or other existing customer relationship. The current global Email DND architecture can force businesses to move operational communications outside HighLevel in order to maintain separate marketing and operational communication controls. Purpose-based DND would improve compliance architecture, customer experience and workflow reliability across financial services, healthcare, professional services, SaaS, home services, appointment-based businesses, e-commerce and other industries. Reference: HighLevel Support Ticket GHL-6446254

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

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.

Hello there! I am requesting for the following endpoint ' https://backend.leadconnectorhq.com/reporting/emails/aggregate/status ' to be available on the V2 Public API. This API endpoint gives LC Email stats for a particular location, is there a possibility of making it available to users of the V2 Public API?