When emailing a contact, the FROM address defaults to the address of the currently logged-in HL user, when it SHOULD default to the email address specified in Settings > Email Services for the account
V
Victor Elkins
When emailing a contact via the HL UI, the FROM email address should always default to the email address specified in that account's Setting > Email Services configuration. Failing to do so is irrational, as defaulting to sending FROM the email address assigned to the currently logged-in user means SMTP authentication will fail, except in rare instances where it just so happens the currently logged-in user has the exact same email address as the one specified in Settings > Email Services. This is particularly egregious when one has an Agency with many subaccounts, all of whom are for different users. Example: Say my name is Bob Smith, email bob@smith.com, and I log into my account as an Agency admin. I have subaccounts for different staff members: Jim Johnson, jim@johnson.com, and Kevin Nations, kevin@nations.com. Each one of these users wants to communicate with their contacts using their own email address, so SMTP auth for each account is of course set up to use their respective email address (and, of course, their address will be used 95% of the time, since they will be the ones using the account). Because HL is configured illogically in-regards contact email FROM settings, every time I go to a specific subaccount, and attempt to send a contact an email, HL defaults to sending from bob@smith.com, my email, instead of jim@johnson.com, the email configured in Settings > Email Services.. So every single email I send to a contact on Jim Johnson's account, I have to edit the FROM field every single time. And every other user has to do the exact same thing any time they access any other subaccount that isn't their own.
S
Spencer Grimes
This impacts 90% of our users.
We really need this because almost all of our users user their personal/business domains for their user, but we're creating email subdomains for them and sending through our mailgun account so they don't have to set up DNS records.
G
GBizRank Admin
SOLUTION?! **see the comment on this loom video!
S
Spencer Grimes
GBizRank Admin great work around for LC Email! However, this only works for LC Email, but not folks using the mailgun integration or other email services, which is what we need.
W
Wes Noyes
Yes! This is very much needed.
S
Stockton Walbeck
THIS IS HUGE! This is one of the biggest complaints we get. Here is a loom video outlining the issue GHL team: https://www.loom.com/share/cdc1e12be6da4ebe940dadf42d55dc5c?sid=851a4db8-2c1c-440a-9b41-97584ecf3a78
E
Eric Mann
Oh man please fix this! Ok…further research shows some nuance and potential workarounds on some of the cases listed here. Worth the read. https://help.gohighlevel.com/support/solutions/articles/48000979925-masking-sender-emails-from-name-address
D
Dylan O'Rourke
This should be standard... causing unnecessary workarounds
K
Keith1 Besherse
Yes, agency admin email address and individual user email address should not overwrite group emails like: "info@..." "support@..." "help@..." "hello@..."
H
Henry Gilliam [Agency]
Agreed. This is a royal PITA for our users. And makes it necessary at times for us to use a VPS to go into HL.