LC Email System

Dedicated Domain = Spam. SMTP = One User for 100 People?!
❌ 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.
1
Multiple Email Services with DND
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.
4
Load More