GoHighLevel Email Builder: Templates & Design (2026)
GoHighLevel Email Builder: Templates & Design (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 26 July 2026 · 10 min read
On this page: Builder modes compared · Reusable templates and saved blocks · Branding and Spam Act compliance · Mobile and dark-mode gotchas · Custom values and merge fields · A/B testing subject lines · When plain text wins · Connecting templates to Workflows · Deliverability basics · Common mistakes · FAQ
The GoHighLevel email builder is one of those features people either barely touch or completely over-engineer. I have audited plenty of Australian sub-accounts where every email was a heavy, image-stacked design sent from a shared domain — and open rates showed it. I have also seen the opposite: walls of text with no unsubscribe link, which is a compliance problem, not a style choice.
This guide covers how I actually build emails in HighLevel for clients: choosing between the three builder modes, reusable templates and saved blocks, branding and footer compliance under the Spam Act, mobile and dark-mode rendering traps, personalisation with custom values, A/B testing in Campaigns, and the deliverability plumbing underneath it all.
GoHighLevel email builder modes: drag-and-drop vs code vs plain text
When you create a template under Marketing → Emails → Templates, HighLevel asks how you want to build it: the drag-and-drop editor (blocks for text, images, buttons, dividers, columns and RSS), raw HTML pasted into the code editor, or a stripped-back plain-text email that looks like it was typed in a normal mail client.
Each mode has a job. Drag-and-drop is where most client work happens — newsletters, promotions, anything needing the logo and brand colours. The code editor suits teams migrating designed templates from another platform or needing pixel control the block editor cannot give. Plain text is the quiet achiever: I use it for most nurture and reactivation sequences because it reads like a personal note, not a broadcast.
| Builder mode | Best for | Flexibility | Deliverability notes |
|---|---|---|---|
| Drag-and-drop | Newsletters, promos, branded announcements | High for layout; limited to available blocks | Heavy images and link-dense layouts can raise spam scores; keep a healthy text-to-image ratio |
| Code editor (HTML) | Migrated templates, custom designs, developer teams | Total control over markup and inline CSS | Sloppy imported HTML (broken tags, tracking bloat) hurts inbox placement; test before sending |
| Plain text | Reply-based nurture, reactivation, sales follow-up | Low — text and links only | Usually the best inbox placement; looks like one-to-one mail, which filters and humans both prefer |
A rule of thumb I give every client: if the goal of the email is a click, design it. If the goal is a reply, don't.
Building reusable templates and saved blocks
The biggest time-saver in the HighLevel email builder is not the builder itself — it is templates and saved blocks. Build your master layout once, save it as a template, then clone it for every campaign rather than starting blank. Any styled section can also be saved as a block and reused across templates. I recommend a standard kit per sub-account:
- Header block — logo at a fixed width (around 150–200px), linked to the website.
- CTA button block — brand colour, generous padding, one job per email.
- Footer block — business name, physical address, unsubscribe link, socials. Never edited per-send.
- Offer block — a styled promo section staff can drop in without touching design settings.
If you run multiple client sub-accounts, bake these templates into your snapshot so every new location starts with a branded, compliant email kit on day one. The same discipline applies to lead-capture assets — consistent styling across GoHighLevel forms and surveys and your emails makes the whole journey feel like one business.
Branding: fonts, colours, logo and the compliant footer
Branding inside the builder is straightforward: set fonts and colours at the template level so every block inherits them. Stick to web-safe fonts (Arial, Georgia, Helvetica, Verdana) — custom fonts fall back unpredictably in Outlook and older mail clients, so half your list may never see your chosen typeface anyway.
The footer is where branding meets law. In Australia, the Spam Act 2003 requires every commercial email to identify the sender and carry a functional unsubscribe mechanism honoured within five business days. Your footer needs:
- Your registered business name (and ABN is good practice).
- A physical address — an office, registered address or PO box, not just a website.
- The unsubscribe link, using HighLevel's built-in unsubscribe merge link so opt-outs are recorded against the contact automatically.
The ACMA actively enforces this and has issued multi-million-dollar penalties for missing or broken unsubscribe links — their guidance at acma.gov.au is worth ten minutes before your next big send. Build the compliant footer into your saved block once and it protects every email your team ever sends.
Mobile rendering and dark-mode gotchas
More than half of most Australian lists open on a phone, and the desktop preview is not the truth. Before saving any template, check the mobile preview for the usual traps:
- Multi-column sections stack on mobile. A three-column feature row becomes a long vertical list — make sure the stacking order still tells a sensible story.
- Tiny fonts. Keep body copy at 16px or larger; 12px looks fine on a monitor and unreadable on a phone.
- Full-width images with text baked in. Text inside images shrinks with the image. Keep headlines as live text.
- Buttons too small to tap. Aim for at least 44px of tappable height.
Dark mode is the sneakier problem. iOS Mail, Gmail and Outlook each invert colours differently: dark text on a transparent background can end up dark-on-near-black, and dark logos on transparent PNGs vanish entirely. Two fixes — give your logo a light background or white padding, and avoid pure black and pure white, which invert harshly. Then send a test to Gmail and Outlook and actually flick both to dark mode before the campaign goes out.
Personalisation with custom values and merge fields
Merge fields (custom values) are where a template stops being a broadcast and starts being a message. The basics — {{contact.first_name}}, {{contact.company_name}} — are table stakes; the real leverage comes from custom fields you have collected, like the service they enquired about or the date of their last appointment. Three habits keep personalisation from backfiring:
- Always test with a contact that has empty fields. "Hi ," is worse than no personalisation. Use fallback values where the field might be blank.
- Use account-level custom values for things that change — offer prices, booking links, seasonal messaging — so updating one value updates every template that references it.
- Personalise the content, not just the greeting. Referencing the actual service someone enquired about lifts response far more than a first name in the subject line.
This matters most in win-back sequences, where a generic blast gets ignored but "it's been eight months since your last service" gets replies — the backbone of any decent GoHighLevel database reactivation campaign.
A/B testing subject lines in Campaigns
Under Email Marketing → Campaigns, HighLevel lets you split-test subject lines on a scheduled send: write two variants, choose the test sample size and winning metric (opens or clicks), and the platform sends the winner to the rest of the list after the test window closes.
Keep the test honest: change one variable at a time, and with Apple Mail privacy features inflating open rates, I increasingly pick clicks as the winning metric for iPhone-heavy lists. Run tests on bigger sends (500+ contacts) where the sample is meaningful, and keep a log of winners — after ten campaigns you will know whether your audience responds to curiosity, specificity or urgency, and that insight is worth more than any single test.
When plain text outperforms designed emails
Here is the counterintuitive bit: for reply-based campaigns, an unstyled email from a real person's name will usually beat your best-designed template. Designed emails signal "marketing"; plain text signals "someone wrote this to me". And a reply is the strongest positive engagement signal Gmail and Outlook can record — it trains inbox providers to keep putting you in the primary tab.
I default to plain text for appointment follow-ups, database reactivation, quote chasers, review requests, and any sequence where the CTA is "just hit reply". I default to the designed HighLevel email builder templates for newsletters, offer announcements, event promotion and content roundups. Most accounts need both; the mistake is using one mode for everything. Email is also just one channel — echoing the same offer through the GoHighLevel Social Planner means the contact who skims the email still sees the message twice that week.
Connecting templates to Workflows for automated sends
Templates earn their keep when they are wired into automation. In any workflow, add a Send Email action and select a saved template rather than writing the email inline — when the offer changes or the footer needs updating, you edit the template once instead of hunting through fifteen workflow steps.
Automated sends worth templating: the instant new-lead response, appointment confirmations and reminders, nurture sequences, abandoned-checkout emails if you sell through a GoHighLevel ecommerce store, and review requests. Pair each template with wait steps and if/else branches so contacts who reply or book drop out automatically — the full trigger-and-action logic is covered in my guide to GoHighLevel Workflows.
One operational tip: name templates with a system, like NURTURE-01-Welcome. Six months from now, "Copy of Copy of Untitled" helps nobody.
Deliverability basics: the plumbing under every template
None of the design work matters if the email lands in spam. Three fundamentals.
Use a dedicated sending domain through Mailgun. HighLevel sends email via Mailgun, and the default shared arrangement ties your reputation to strangers. Set up a dedicated subdomain — something like mail.yourbusiness.com.au — so your sending reputation is yours alone.
Authenticate with SPF, DKIM and DMARC. When you add your sending domain, HighLevel provides the DNS records to publish: SPF authorises the sending servers, DKIM signs each message, and DMARC tells receivers what to do when either check fails. Since Google and Yahoo tightened bulk-sender requirements, unauthenticated mail is increasingly rejected outright. The step-by-step DNS instructions live at help.gohighlevel.com.
Warm up and keep the list clean. A new domain sending 10,000 emails on day one looks exactly like a spammer. Ramp volume over a few weeks, remove hard bounces, and move long-unengaged contacts into a reactivation sequence instead of flogging the newsletter at them forever.
Common mistakes to avoid
- Sending from the shared domain forever. Fine for week-one testing, but every serious sender needs a dedicated Mailgun domain with SPF, DKIM and DMARC in place.
- No physical address or unsubscribe link in the footer. That is a Spam Act breach in Australia, and the ACMA has fined household names for exactly this.
- Building every email from scratch. Without saved templates and blocks, branding drifts and your team burns hours recreating headers and footers.
- Designing for desktop only. Skipping the mobile preview and dark-mode test means part of your list gets unreadable text and invisible logos.
- Merge fields with no fallbacks. "Hi ," destroys trust instantly; always test templates against contacts with empty fields.
- Using designed templates for reply-based sequences. If you want a reply, a heavily branded email works against you — go plain text with a personal sender name.
If you want branded, high-deliverability email templates built for your business inside GoHighLevel, book a strategy call with the HL Growth Partner team.
Frequently asked questions
Is the GoHighLevel email builder drag-and-drop?
Yes. The default editor under Marketing → Emails → Templates is a drag-and-drop block builder with text, image, button, divider, column, video and RSS elements. You can also switch to a raw HTML code editor for imported designs, or keep emails as simple plain text for one-to-one style sends.
Can I import my own HTML email templates into HighLevel?
Yes. Choose the code editor when creating a template and paste your HTML in. Just test thoroughly afterwards — templates exported from other platforms often carry leftover tracking code or broken markup that hurts rendering and spam scores.
What does an email footer legally need in Australia?
Under the Spam Act 2003, commercial emails must clearly identify the sender, include accurate contact details (a physical address is best practice), and provide a functional unsubscribe facility that is actioned within five business days. Use HighLevel's built-in unsubscribe link so opt-outs are recorded automatically.
Why do my emails look wrong in dark mode?
Mail clients invert colours inconsistently in dark mode. Dark logos on transparent backgrounds can disappear, and forced colour inversion can make text unreadable. Avoid pure black and pure white, give logos a light background or padding, and send test emails to Gmail and Outlook in dark mode before every major campaign.
Do plain-text emails really deliver better than designed ones?
Generally, yes. Plain-text emails have no images or heavy markup for filters to flag, and they attract more replies — the strongest positive engagement signal an inbox provider can see. For sequences aimed at getting a response, plain text usually wins; save designed builds for newsletters and promotions.
