LC Email System

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

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

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

Can you please add a 'warm up email' service. Or have an integration to a service like Warmup Inbox. Thanks

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

I would like you to have this feature on highlevel to allow users to select a sending domain for each worflow. Sometimes client has multiple website and funnel domain. If we create workflow and email sequence we might need a different reply email address for each domain. You can just add a limitation of the active sending domain maybe at least 3 or 5, so users will not be abuse this feature.

For those who are using Sendgrid for emails, it would be nice to have a "From Name" field. At the moment, GHL only uses the email username as the from name even when the from name is already set up in Sendgrid. For instance, when a Sendgrid email sender johndoe@mydomain.com was set up with a From Name "John D." in Sendgrid, GHL seems to bypass that from name and just go ahead and use "johndoe". Users should be able to use the From Name set up in Sendgrid or be able to put a From Name in GHL as well.

The LC email are a great feature but pretty useless as they never land in inbox, especially when you wanting to do email newsletters it’s needed

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.