Multiple Sender Mailboxes per Sub-Account
D
Daniel Kress
Allow several verified email identities on a single sub-account and let users choose the desired “From” in workflows, bulk sends, and conversations. Add simple role-based permissions (e.g. sales@ for Sales, support@ for Support).
Keeps departments and brands clearly separated
Improves deliverability with proper SPF/DKIM alignment
Reduces account sprawl and simplifies reporting
Log In
S
Sales & Marketing
Merged in a post:
Email Sender Identity for 1-on-1 Conversations (be able to change the from email)
M
Maximilian Lannoye
Description / Problem Statement:
Currently, when sending manual 1:1 emails via the Conversations tab, the “From” name and “From” email address default to the logged-in user’s email/profile.
Requested Solution / Feature:
Introduce a setting within each Location / Sub-account in GoHighLevel allowing administrators to define a default From Name and From Email Address for all manual 1-on-1 sends in Conversations. This could include:
A configuration field under Settings → Email Services or Settings → Conversations Defaults labelled “Default From Name (Manual Emails)” and “Default From Email (Manual Emails)”.
Optionally a toggle “Override user login email for manual send From address” (Yes/No).
When enabled, regardless of which user is logged in, the manual send will default to the configured “From Email” and “From Name” for that Location. The user can still manually change it if desired, but the default loads accordingly.
Ensure the “From Email” must belong to a verified sending domain (dedicated domain) configured for that sub-account, to maintain deliverability.
Possibly provide a dropdown list of verified sending email addresses for each sub-account/user to choose from for manual sends (so users can pick their specific domain-aligned address if multiple are configured).
Benefits / Impact:
Reduces user error and eliminates the need for individual users to manually set or switch “From” addresses each time they send a manual email.
Ensures brand consistency — manual sends across the team appear from the business domain, not from personal login emails.
Improves deliverability and sender reputation by ensuring the “From” address aligns with the properly configured sending domain for the sub-account.
Scales much better for agencies like ours that manage many users across many sub-accounts with different domains.
Enhances professionalism in communication: leads and clients always see the business branded email, not a personal email which may confuse them.
Additional Notes / Considerations:
This feature would complement existing workflow/campaign “From” address settings (which already allow explicit “From Name” and “From Email” fields).
It should be clearly documented in the “Sending Priority – From Name & Address” doc to reflect that manual sends via Conversations can now respect the Location-default “From” address rather than just the logged-in user.
Agencies should be able to configure this per-location (sub-account) so that each client or brand can maintain its own domain and sender identity.
Ideally, a permissions layer: allow Admins only to set the default “From” address; users see it pre-populated but can change it if the toggle allows.
A migration or fallback logic: if no default “From Email” is set, continue with the current logic (user’s email) to avoid breaking existing workflows.
Summary:
Please add the capability for Location/Account administrators to set a default “From Name” and “From Email” for manual sends in the Conversations tab — so the “From” address is automatically aligned with the correct business-domain email, rather than defaulting to each user’s login. This change would dramatically improve usability, brand consistency, deliverability, and scalability for teams and agencies.
Thank you for considering this enhancement.
D
Denise Cruz
YES! I came here ask for this as it's one of the most annoying things in using the GHL as a true CRM for 1:1 client communications. I'd would be great to have the ability to switch between the pre-configured emails for "sales@mydomain.com", "support@mydomain.com", etc or as "email@one-domain.com" or "email@another-domain.com" as a drop drown in the 1:1 email composer vs. having to switch the account I'm logged.
J
Jacob Drinen
For REALLLLLL
C
Caleb Christopher
Solid, especially from the email deliverability and authentication: SPF/DKIM (which can significantly affect DMARC, which can outright reject or quarantine messages that don't align with SPF/DKIM configuration)... the PROBLEM would be that DMARC has to be relaxed just to accommodate weak sender authentication, which opens the domain to abuse by others because of the relaxed DMARC security setting.
~I'm speaking from my experience as a cybersecurity speaker and consultant.