Email System

New regulations forced us (in EU) to allow leads to disable tracking cookies on email. This feature is available only for LCemail users. It'd very important to have it available also for users that send emails with third-party providers like Mailgun or alternative services.

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.

The email campaigns associate revenue that's great. We make workflows so campaigns are not always necessary day to day, yet we have no idea how much revenue is generated by a workflow email etc. This is a massive gap, if we are helping businesses this needs to be addressed as it is one clear indictor if the system is making more money for a client or not! I would appreciate & I think it would also be great for GHL to be able to advertise that the system generated a clients business X amount. It's a massive gap that in theory would be easy to close you do it on emails for campaigns already why not workflows? There are a few already like this address it its a really high value additive that would also make your SaaS be more attractive

The current unsubscribe page in GoHighLevel has a major limitation that prevents previously unsubscribed contacts from resubscribing through the method GHL recommends. According to GHL's documentation, contacts can resubscribe by clicking the unsubscribe link in an email and selecting "Unsubscribed by mistake. Subscribe again." However, this does not work once a contact has already submitted an unsubscribe reason. Here's the problem: A contact clicks the unsubscribe link in an email. They're presented with several options, including "I no longer want to receive these emails" and "Unsubscribed by mistake. Subscribe again." Let's say they select "I no longer want to receive these emails" and click Submit. They're then taken to a confirmation message saying "Thanks for your feedback!" Later, they realize they unsubscribed by mistake or simply change their mind and want to receive emails again. They click the same unsubscribe link in the original email, hoping to select "Unsubscribed by mistake. Subscribe again." Unfortunately, the page only displays the previous "Thanks for your feedback!" confirmation message. The options are no longer available. So how exactly are they supposed to resubscribe if GHL no longer allows them to select the option? This is the actual issue. The unsubscribe page behaves like a one-time submission form, making the existing resubscription option practically useless after someone has already unsubscribed. What needs to be improved: Allow contacts to access the unsubscribe/resubscribe options again, even after they've already submitted an unsubscribe reason. Remove the limitation where returning to the unsubscribe link only displays the previous confirmation message. If a contact is already unsubscribed, the page should still provide a working "Unsubscribed by mistake. Subscribe again" option so they can voluntarily opt back in. Once they select the resubscribe option, GHL should properly update their email subscription status and record their renewed consent. The unsubscribe link should remain functional for managing email preferences, rather than becoming permanently stuck on a confirmation message after the first submission. Why this matters: People change their minds. Someone might unsubscribe accidentally, or they might intentionally unsubscribe today and decide to receive emails again weeks or months later. GHL already provides a "Subscribe again" option, but what's the point of having it if contacts can no longer access it after they've unsubscribed? The current behavior also makes GHL's recommended resubscription method confusing and unreliable. We're not asking for an entirely new system. We're asking GHL to improve the existing unsubscribe page so that the resubscription option remains accessible and functional even after the contact has previously unsubscribed. Please fix this one-time submission limitation. Contacts should always have a straightforward way to voluntarily resubscribe, especially when GHL already advertises this functionality.

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.

Be able to mark an email as spam and block it from coming into the system. Because I’m charged for every email that comes through the system, there should be a way to block unwanted emails. Not all emails come with unsubscribe options.

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

From Instantly: "The warmup functionality mimics human conversations between email accounts. But in this case, your ‘friends’ are other Instantly.ai users that have also enabled the warmup feature. You can be sure that all of them will open your email and a high percentage will write you back with a ‘thoughtful’ and positive sentiment. ​ The emails written by the Instantly AI algorithm signal to Google, Outlook, and others ESPs that your email account and sending domain is relevant and legitimate. This increases the likelihood that the messages that are sent to the cold leads in your outreach campaigns will also actually land in their inbox and subsequently be opened and replied to. ​ The bottom line is that the warmup will improve the deliverability of your cold email accounts by mimicking human conversations in the Instantly.ai user pool. When you connect a sending account to Instantly, warming up the accounts also warms up your SMTP sending server and IMAP servers as well. On top of the deliverability benefits, your outreach email accounts will also stay alive for longer and the likelihood of you ‘burning’ through an account is significantly lower. Think of it as you emailing back and forth with your friends - on autopilot." https://help.instantly.ai/en/articles/5975329-how-warm-up-works-and-why-it-s-important

When you add an email subdomain and select AUTOCONFIGURE, what is set up in (in my case) Cloudflare, is different to what's recommended in GHL. Further, when reading the support article ( https://help.leadconnectorhq.com/support/solutions/articles/155000002223-how-to-add-a-domain-and-verify-dns-record ), it says TTL records should be set to 5 minutes, though Cloudflare uses both 10 mins and 1 hour depending on the setting. This is confusing as there's nothing listed as to the impact of this auto-configuration in Cloudflare that differs from what's recommended by GHL.