Multiple Email Services with DND
W
Willie Meyer
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.
Log In
M
Martin Mora
it will also allow staff mebers have their own email addresses and send out from their own staff account on the sub account.
J
Jay Leonen
My agency uses a sales email to communicate with leads and prospects who inquire with us directly through email, or are on the discovery/demo call process. Some marketing emails will be coming from HighLevel, but most are from domains sending through Instantly. We also use a separate support email to communicate with clients (onboarding/support), affiliates, and collaborative and white-label agencies.
This would be a great help, having the ability to use multiple email services within a sub-account so as to separate sales and support correspondence.
J
Jacob Hicks
Yes, we basically need the ability for users to choose what TYPE of emails they want to unsubscribe to. Right now, we just have one unsubscribe option and it unsubscribes them from EVERYTHING.
I created a short loom video showing an example: https://www.loom.com/share/0b31f4b984d34435b855fa49a29e7c80
O
Oie Dobier
Jacob Hicks Completely agree the system should be able to separate the type of email and then send/not send based on user preferences. For example, if I have a workflow that is an operational workflow I should be able to denote that at the workflow level and then any action in the workflow would respond accordingly to the user's preferences around operational emails and texts. I know we can build a custom landing page for people to unsubscribe so we don't use the standard DND behavior but then implementing that into workflows is super painful. It's easy at the top of a workflow to check for a specific unsubscribe tag and exit the workflow but in the middle of it, if they unsubscribe (add a tag) the only way to exit would be to use the goal event of which currently I think you can only set one goal per workflow so that doesn't work in instances where there's already another goal event. Having to put if/then branches before every email in a workflow just isn't sustainable.