LC Email System

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
Deliver inbound email to Conversations regardless of subdomain
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.
8
·

upcoming

Load More