Header Override for Emails Actions in Workflows or Dedicated Domain Choice for Workflows
S
Steven Schmidt
We have a dedicated domain for workflows. Anytime an email is sent via a workflow, it is sent through this domain and applies the default headers (name/email) assigned to that domain. I just created a new workflow with an email action. We would like that email to be sent from a different header than what is currently on the workflow domain. Unfortunately, the "From Name" and "From Email" fields in an email action do not override the workflow domain header.
Currently, you can assign more than one domain as a workflow domain. This splits the frequency up of which domain a workflow chooses as its sending domain.
For example: You're sending 100 emails through a workflow and you have a 50% frequency for both domains, each one will send 50 emails.
It would be nice to override the default headers with the headers in email actions OR if you have multiple dedicated domains configured to be workflow domains, you have the choice of picking only a single one of those domains to use for a specific workflow.
Log In
E
Emma Sansom
When will this be done, it's so critical for best deliverability how is it still not a feature? thanks... Matthias Loeffel AND Dallas Clounch have you managed to find a work around since asking abiout this 6-12 months ago?
M
Matthias Loeffel
This actually is also the case with email campaigns. The dedicated headers will never be overwritten by what I put in as "Sender Name".
👉 We want to send multiple campaigns. A solution would be to let us choose which dedicated domain we would like to use for a specific email campaign, or for the matter, the specific email in a workflow.
E
Emma Sansom
Matthias Loeffel don't suppose you've managed to find a work around? We are even considering a differnet platform
D
Dallas Clounch
This is also causing me major issues, need to be able to select which dedicated domain to use at the individual workflow level
E
Emma Sansom
Dallas Clounch don't suppose you've managed to find a work around? We are even considering a differnet platform
D
Dave King
This is exactly what I need.
I have a client sending 50,000 emails per day on AWS and they get blacklisted. Moving to GHL, so I created 20 dedicated domains (sub domains) for GHL. But when I specify that dedicated domain in the workflow it is overridden by the default dedicated domain. I do not understand the point in "default dedicated domain", it is certainly not a feature, and breaks being able to specify a from address on the workflow completely. Literally everything routes out of the default dedicated domain, I do not see the point and how that is ever a benefit. If I could remove a dedicated domain from being default, I think it would work. And the workaround is to remove the header, but then you have a "on behalf of" and the emails go to spam.
What we need is if we specific the from name and from email in a workflow step or on the settings tab that matches a dedicated domain, it routes through that dedicated domain.
Come on guys, we need this!
E
Emma Sansom
Dave King don't suppose you've managed to find a work around? We are even considering a differnet platform
D
Dave King
Emma Sansom we logged it with the dev team, who were meant to remove it before Christmas, but they didn't, I gave up in the end and moved emails elsewhere, as it wasn't workable. Please drop me a message if you want to chat about it.
E
Emma Sansom
Dave King hi Dave, yes we are looking at doing cold stuff elsehwere. Happy to chat, how do we go about that? Want to connect on Li? https://www.linkedin.com/in/emmasansom/