Deliver inbound email to Conversations regardless of subdomain
upcoming
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.
Log In
A
Ahmed Falih Hadi
When this will be finished ?
K
Karthik
upcoming
K
Keith Besherse
Karthik, thank you VERY much!
This is the outbound version of the same concept.
K
Keith Besherse
See also this request which would allow us to trigger Workflows off which Dedicated Sending Domain (or Default Dedicated Domain) or the addressee at that subdomain the email came in from.
K
Keith Besherse
Also, I would like to receive emails sent to any of the Dedicated Sending Domains.
At which point we would probably want to trigger/filter off domain/subdomain name too.
K
Keith Besherse
According to the help document FAQ section, cold inbound email is delivered by LC email. But no instructions or guidance are provided for how to troubleshoot. https://help.gohighlevel.com/support/solutions/articles/48001185801-cold-email-inbound-setup-mailgun
K
Keith Besherse
The point of this suggestion is to permit multiple Dedicated Sending Domains and a single Default Dedicated Domain for each subaccount/location with any addressee @ each registered DNS domain/subdomain receiving inbound email (cold or reply). All of these messages would be delivered to Conversations tab and could potentially trigger a Workflow.
K
Keith Besherse
What I am about to tell you is not a procedure approved by HighLevel. There are a couple significant risks. However, it seems to be working for me.
First: HL is not an email service provider (ESP) so deliverability and reception are not guaranteed. That is why they recommend integration with an ESP, preferably from either Google Workspace or Microsoft Outlook.
Second: I am not convinced the Customer Replied trigger with Channel is Email works consistently on inbound cold email.
Third: If your root domain is the Default Dedicated Domain (DDD) any Dedicated Sending Domain (DSD) will only receive emails which are a direct reply. No cold inbound. No new email drafted from scratch.
Fourth: If your agency has the same root domain as your SaaS your clients will not receive emails without their own DSD.
Fifth: There is no email addressed to filter for the Customer Replied trigger when Channel is Email. Thus you cannot trigger a different workflow for email addressed to sales vs email addressed to support...
With those caveats...
You can have your agency root domain (supersaasagency<dot>com) set as the DDD in the account for your agency. With a different domain (supersaasagency<dot>io) set as the agency domain for system messages. Then you can have subdomains for clients who don't give you a subdomain on their own DNS (client1<dot>supersaasagency<dot>io, client2<dot>supersaasagency<dot>io, client3<dot>supersaasagency<dot>io, ...).
There is no SMTP for emails addressed to your root domain. The address in front of the @ does not matter. All inbound email with your agency root domain should arrive in the Conversations tab.
If you want to test it you can send an email to: ideasboardtest@thebaldguymarketing.com.