Sending domain setup
Connect a dedicated sending subdomain and review how it fits alongside your existing business email.
Services / Email deliverabilityGOHIGHLEVEL EMAIL SERVICESGive your emails
Give your emails
a better foundation.
Sending-domain setup, authentication, and practical workflow improvements for your GoHighLevel account. Understand what needs attention and what to do next.
25% off your first order · Scope agreed before work beginsSTART WITH THE RIGHT CHECKS01 02 03 04 05 06
More than a DNS change.
Authentication is one part of the picture. Your sending setup, audience, message content, and follow-up process all need to work together.
SPF, DKIM & DMARC
Review authentication records and coordinate the required DNS changes with your domain administrator.
Provider configuration
Check your LeadConnector, Mailgun, SendGrid, or other agreed sending setup and its connection to GoHighLevel.
Campaign & workflow review
Check sender details, templates, segmentation, follow-up timing, and how replies and opt-outs are handled.
Testing & reporting
Review sample messages, authentication results, and available account signals. Document findings and next steps.
Ongoing improvements
Agree on a review plan for sending practices, list quality, and changes to your account over time.
A CLEAR PROJECT PROCESSKnow what changes.
Know what changes.
Know why.
We agree on the scope and access needed for your account. Your existing business email and connected tools are part of that review.
Read the email setup guide ↗Review your current setup
Share your sending provider, domain, current concerns, and the workflows you want reviewed.
Agree on the changes
Confirm the records, account settings, and workflow updates included in your project.
Configure and test
Make approved changes and check sample messages, authentication results, and workflow behavior.
Get a practical handover
Receive a summary of the setup, remaining recommendations, and any agreed support steps.
Diagnose the symptom before changing the setup.
An email problem can begin in a workflow, at the sending provider, or after a receiving server accepts the message. A useful review identifies where the journey stops. Bring an example of the affected email, when it was sent, and what the recipient or sending log shows.
Emails are accepted but appear in spam
Collect a recent message header and compare authentication results, sender identity, audience source, and sending history.
Changing a subject line alone will not resolve every underlying setup problem.
Messages bounce or are rejected
Read the exact provider error and distinguish an invalid address from authentication failure, rate limiting, or a policy rejection.
Keep the error text and timestamp so the review starts with evidence.
A new domain has inconsistent results
Review the first audiences, sending frequency, and account limits before expanding campaigns.
Start with people who expect your messages and adjust based on observed results.
Contacts receive duplicate follow-ups
Trace workflow enrollment, re-entry settings, campaign overlap, and stop conditions.
Test what happens when a contact replies, books, or unsubscribes.
Replies do not reach the right person
Check the reply-to address, connected mailbox, conversation routing, and team assignments.
Send a test reply and confirm that a team member can see and respond to it.
A “delivered” event generally means the receiving server accepted the message; it does not confirm that a person read it or that it appeared in their primary inbox. Keep delivery, placement, and customer response separate when reviewing campaign performance.
SPF, DKIM & DMARC EXPLAINEDSPF DKIM DMARC
Understand what your domain records do.
These controls help receiving systems evaluate who sent a message. They are a foundation for a responsible sending setup, alongside audience quality and sending practices.
Authorize sending sources
SPF identifies servers authorized to send for a domain. Review the existing record and legitimate sending services before making changes.
Sign outgoing messages
DKIM adds a signature that receivers can verify using a key published in DNS. Check an actual sent message as well as the configuration screen.
Check identity alignment
DMARC checks whether the visible From domain aligns with a passing SPF or DKIM identity. Its policy tells receivers how to handle failures.
Google recommends SPF, DKIM, and DMARC. Its additional bulk-sender requirements apply to senders reaching roughly 5,000 messages per day to personal Gmail accounts, including authentication and unsubscribe requirements. Review the full requirements for your sending pattern in Google’s email sender guidelines.
DEDICATED SENDING DOMAINS
Separate the roles of your domains.
Your website address, business mailbox, and marketing sending domain serve different purposes. For example, a business might use example.com for its website and mail.example.com for a sending subdomain.
HighLevel supports dedicated sending domains in LC Email. Use the records supplied for your account and verify them in the platform. A dedicated sending domain is different from a dedicated IP address, and setting one up does not guarantee inbox placement.
HighLevel’s dedicated-domain setup guide ↗What we confirm before DNS changes
- Which provider hosts your everyday business mailbox
- Which services already send using your domain
- Which subdomain the GHL setup will use
- Who approves and applies changes to DNS
- How we will verify the result and document the change
Keep a record of the existing configuration. Do not replace unrelated website or mailbox records just to connect a sending service.
Explore the GHL domain setup guide ↗A DELIVERABILITY REVIEW YOU CAN USE
What your audit should tell you.
A useful report connects a finding to evidence, an action, and a way to check the result. The exact review depth depends on your chosen package and the access available.
Current configuration
A summary of the sending provider, domain, relevant authentication records, sender addresses, and workflows included in the review.
Observed findings
Examples of the errors, authentication results, or workflow behavior we could reproduce. Unknowns are recorded as items to investigate.
Prioritized actions
A checklist separating configuration work, campaign changes, and decisions that need your approval or your provider’s support.
Changes made
A record of agreed updates, including the account or domain affected and any steps your team needs to complete.
Verification results
What was tested after the work, which checks passed, and which results require more observation or additional access.
Next review steps
A handover covering the signals to watch, ownership of follow-up tasks, and the scope of any separately agreed ongoing support.
Example finding: follow-up continues after a booking
Evidence: a sample contact books an appointment but remains enrolled in a promotional sequence. Action: review the workflow’s booking conditions and exit rules. Verification: repeat the test with a new sample contact and check that the next promotional step is skipped. This is an illustrative review scenario, not a client result.
A practical sending checklist.
Confirm audience expectations
Know where contacts came from, what they requested, and whether this message matches that expectation. Keep opted-out and invalid addresses out of active campaigns.
Review the message journey
Check the From name, reply destination, links, mobile presentation, and unsubscribe experience. Confirm that the landing page matches the email’s offer.
Check the workflow
Use sample contacts to test enrollment, delays, timezone settings, replies, bookings, and exit conditions. Look for overlapping sequences.
For a new sending setup, HighLevel recommends starting with opted-in contacts who are likely to engage and increasing sending gradually. Follow your account’s current limits and review bounces and complaints before expanding. See HighLevel’s sending and warm-up guide.
What to monitor after launch
Review provider errors, bounces, complaints, unsubscribe activity, and actual replies or bookings. Treat open rates as one signal rather than proof that a message reached the intended inbox. Compare similar campaigns over time instead of drawing conclusions from one test email.
When an issue appears, preserve the message example and error details before making several changes at once. A documented change followed by a repeatable test is easier to evaluate.
EMAIL SETUP PACKAGESDOMAIN SERVICES SETUP + REVIEW DOMAIN SERVICES
Choose your starting point.
Packages cover one domain. We confirm the exact scope before starting; provider subscriptions and sending charges are separate.
Foundation
$100 / domain · USD
For a new sending domain or a focused authentication setup.
- One domain
- DNS record review and setup
- SPF, DKIM & DMARC configuration
- Agreed email-provider connection
- Setup handover
Standard
$250 / domain · USD
For an existing account that needs a broader email review.
- Everything in Foundation
- Email deliverability report
- Google Workspace DNS review, if used
- Automation setup review
- Prioritized recommendation checklist
Premium
$499 / domain · USD
For teams planning a more involved sending workflow.
- Everything in Standard
- Sending-volume and workflow planning
- Campaign configuration review
- Provider setup review
- Testing and handover checklist
First order? Ask us to apply the 25% offer to your project quote. Inbox placement cannot be guaranteed.
Can you guarantee every email reaches the inbox?
No. Inbox placement depends on the receiving provider and factors beyond authentication alone. We can review your setup, make agreed improvements, and document the results of testing.
Can you work with an existing GHL account?
Yes. We review your current provider, domain records, and workflows before planning changes. Tell us which parts of the account are already in use.
Will you need access to my domain?
DNS work requires access through an agreed process. We can coordinate changes with your administrator. Do not send passwords through your initial email or WhatsApp message.
Is ongoing support included?
Each package has an agreed implementation scope. Ongoing monitoring, campaign work, and account support can be scoped separately.
Can you help with email automation too?
Yes. We can review inquiry responses, campaign segmentation, and follow-up workflows. Explore our automation services.
LET’S REVIEW YOUR SETUP
Make your next step clear.
Tell us what you’re sending, which provider you use, and what needs fixing.