GoHighLevel Now Picks a Sender Domain Per Workflow

August 31, 2026. If you run client email inside GoHighLevel, a change shipped on August 28 fixes a problem that has quietly cost agencies deliverability for years. Workflow Settings now has a Sender domain dropdown, so a promotional nurture and a booking confirmation no longer have to leave the sub account on the same domain. Until now they always did, and a single bad campaign could push appointment reminders into spam alongside it.

What actually changed

1. A Sender domain dropdown now appears under Sender details in Workflow Settings, listing every verified dedicated domain on the sub account plus an All domains option.
2. Choosing All domains keeps the existing behaviour, sending across configured domains using the weighted distribution set at the sub account level.
3. Choosing a specific domain plus a prefix sends every email action in that workflow from that address, the same way domain selection already worked in Email Campaigns.
4. If the sub account has no dedicated domains configured, the dropdown does not appear at all. This is a feature for agencies already running their own sending domains.

Why one domain per workflow is worth the setup

Sending reputation is assessed per domain, which is why Google's own sender guidelines tell bulk senders to keep different classes of mail on different subdomains. Inside a GoHighLevel sub account that was previously impossible at the workflow level. Changing the From address on a workflow changed the name recipients saw, not the domain the mail actually left on, so promotional volume and transactional volume rose and fell together on one reputation.

Splitting them does two things. It caps the blast radius, so a nurture campaign that gets complaint rates wrong costs you that domain and not your receipts and reminders. And it lets you canary a brand new domain on one low volume workflow and watch how it lands before you move anything important across. HighLevel's own worked example is a clinic keeping reminders and receipts on one subdomain and monthly promotions on another.

The override chain that will catch someone out

There are three levels of precedence and they are not obvious. Sender details set inside an individual email action beat the workflow level setting. Email headers configured in the dedicated email settings beat the workflow settings. And if someone types a full sender email address on a different domain than the one selected, that address wins and HighLevel raises a Sender domain mismatch warning rather than blocking the send.

The practical consequence is that setting the workflow domain does not guarantee the workflow uses it. Before you trust the new setting on a live client, open each email action in the workflow and check whether anyone has hardcoded a full From address inside it.

What it means for operators

Do this in one pass per sub account. Verify at least two dedicated domains under Email Services, put transactional workflows such as booking confirmations, receipts and missed call follow ups on one, and put promotional or reactivation workflows on the other. Audit the email actions for hardcoded From addresses. Then leave a fortnight between the change and any judgement about results, because domain reputation moves slowly in both directions.

This is standard practice in cold outreach and it is now available where the CRM lives. If you want it configured across a client portfolio rather than one sub account at a time, that is part of what we do in GoHighLevel services, and the same segmentation logic underpins how we set up sending infrastructure for cold email campaigns. If a domain is already in trouble, start with our guide to checking and fixing a blacklisted domain before you point new workflows at it.