What does white-label email mean for GHL agencies?

Each client sends from their own domain (marketing@clientbrand.com) with their own authentication. Recipients see the client's brand, not your agency's. The infrastructure (SMTP provider, monitoring) is managed by you, but the sending identity is the client's.

Do I need a separate SMTP account per client?

Not a separate account — separate domains within one account. Use one Mailgun or SendGrid account with multiple verified domains. Each client domain gets its own SMTP credentials and authentication records. This provides reputation isolation within one billing relationship.

What about custom tracking domains per client?

Ideally, yes. Configure links.clientdomain.com as the tracking domain for each client. This removes your SMTP provider's shared tracking domain from the equation and keeps everything branded to the client.

Can clients see the SMTP configuration?

In standard GHL sub-accounts: no. SMTP settings are managed at the agency or sub-account admin level. Clients using the front-end portal see their campaigns and reports but not the SMTP backend. You maintain infrastructure access.

What if a client leaves? Can they take their email infrastructure?

They own their domain and DNS records. They'd need to set up their own SMTP provider and GHL account. The authentication records (SPF, DKIM) transfer with their domain. Your SMTP credentials would be deactivated. Plan for this in your service agreement.

GoHighLevel White-Label Email Setup: Complete Guide

See our agency email infrastructure guide and managing multiple client domains for the complete agency framework.

The White-Label Architecture

Your Agency (Infrastructure Manager)
├── One SMTP Provider Account (Mailgun/SendGrid)
│   ├── Client A Domain: marketing.clienta.com
│   │   ├── SPF, DKIM, DMARC configured
│   │   ├── Dedicated SMTP credentials
│   │   └── [Custom tracking domain](/email-infrastructure/custom-tracking-domain): links.clienta.com
│   ├── Client B Domain: marketing.clientb.com
│   │   ├── SPF, DKIM, DMARC configured
│   │   ├── Dedicated SMTP credentials
│   │   └── Custom tracking domain: links.clientb.com
│   └── Client C Domain: ...
├── GoHighLevel Agency Account
│   ├── Sub-Account A → uses Client A SMTP credentials
│   ├── Sub-Account B → uses Client B SMTP credentials
│   └── Sub-Account C → ...
└── Monitoring (n8n / Postmaster Tools per domain)

Each client's email looks like it comes from their brand. You manage everything behind the scenes.

Per-Client Setup

Step 1: Domain Configuration

Work with the client to choose their sending domain:

marketing.clientbrand.com (subdomain, recommended)
clientbrand.com (root domain, acceptable for simple setups)

Step 2: SMTP Provider Verification

In your Mailgun/SendGrid account:

Add the client's domain
Get DNS records (SPF, DKIM, tracking CNAME)
Provide records to client (or their IT) for DNS setup
Verify domain in SMTP provider

Step 3: DNS Records (Client's Domain)

Add to client's DNS:

SPF: v=spf1 include:mailgun.org -all (or your provider's include)
DKIM: CNAME/TXT records from your SMTP provider
DMARC: v=DMARC1; p=none; rua=mailto:[email protected]
Tracking: links.clientdomain.com CNAME [provider tracking endpoint]

Step 4: SMTP Credentials

Create dedicated SMTP credentials for this client domain in your provider:

Mailgun: Domain Settings → SMTP Credentials → Add New
SendGrid: API Key with restricted permissions

Step 5: GHL Sub-Account

In the client's GHL sub-account:

Settings → Email Services → Add SMTP
Enter: host, port 587, client-specific credentials
Set as default sending method
Test: send test email, verify client's domain in From: and authentication headers

Step 6: Monitoring

Set up Google Postmaster Tools for client's domain
Add client's sending domain to blacklist monitoring
Schedule monthly reputation checks

Agency Pricing Model

White-label email infrastructure is a service you provide. Pricing approaches:

Model	Example	Pros	Cons
Included in retainer	$500/month includes email management	Simple for client	You absorb SMTP costs
Cost + markup	SMTP cost + 50-100% markup	Fair, transparent	Requires tracking per-client costs
Per-email pricing	$2-5/1,000 emails	Scales with usage	Complex billing
Flat fee	$50-150/month for email infrastructure	Predictable	May lose money on high-volume clients

For self-hosted SMTP (Mailcow/Postal at $5-15/month total), even $50/month per client provides significant margin.

What White-Label Email Is NOT

Not hiding your agency. White-labeling means the email comes from the client's brand. It doesn't mean hiding that an agency manages their marketing. Be transparent about your role.

Not shared infrastructure. Each client must have their own domain and authentication. Sharing one domain across clients is not white-label — it's a liability.

Not set-and-forget. Email infrastructure requires ongoing monitoring, authentication maintenance, and reputation management. White-label is a service, not a one-time setup.

Practitioner note: White-label email is the highest-margin service most GHL agencies don't offer. The infrastructure cost is minimal ($5-35/month depending on SMTP choice), but the value to clients is significant — properly authenticated email from their domain with managed deliverability. Charge $50-150/month per client and you're delivering real value at excellent margins.

Practitioner note: The key to scalable white-label: standardize your process. Template the DNS records (fill in client domain), script the SMTP credential creation, and checklist the verification steps. With a standard process, onboarding a new client's email takes 30 minutes, not 3 hours.

If you want white-label email infrastructure designed for your GHL agency, schedule a consultation.

Sources

GoHighLevel: Sub-Account Management
Mailgun: Domain Management

v1.0 · March 2026