Week 7 of 8

Email HTML, Campaigns, and Deliverability

Templates are the building blocks. Campaigns are how you sequence them. Plan the goal, timing, and deliverability before you design anything.

A template is a single reusable email design. A campaign is a planned sequence of emails with a defined goal and timing. Deliverability is whether those emails land in the inbox at all.

Beautiful email design is worthless if the message hits the spam folder, breaks on mobile, or has a broken link. Deliverability and clarity come first, design second.

This week is not about making emails look fancy. It is about making sure emails are readable, deliverable, compliant, connected to the right audience, and tied to a clear next step. Email only works when the message, list, sending domain, workflow, and CTA all support the same goal.

Why This Matters

A beautiful email that no one opens is worse than a plain one that gets replies. Deliverability, mobile layout, and clear CTAs matter more than visual polish.

What Usually Goes Wrong

HTML emails that break on mobile
No unsubscribe link or physical address
Vague CTAs like 'learn more' with no landing destination
Campaigns with no defined goal
Sending a nurture without checking the workflow it feeds into
Sending from a domain with no SPF, DKIM, or DMARC configured

Deliverability Foundations

Use a real sending domain, not a free inbox.
Configure SPF, DKIM, and DMARC on the sending domain.
Warm the domain by sending small volumes to engaged contacts first.
Keep the list clean; remove bounces and long-inactive contacts.
Watch spam complaints; even a small spike hurts reputation.
Send only to contacts with the right consent and relationship.
Avoid purchased or scraped lists.
Do not send large broadcasts from a new or untested domain.
Use clear subject lines that match the email content.
Avoid image-only emails.
Avoid excessive links, attachments, or spam-style formatting.
Make sure the reply-to inbox is monitored.
Remove or suppress repeated bounces.
Review unsubscribes and complaints after every campaign.

Note

Deliverability is not one setting. It is the combined result of domain setup, list quality, message quality, sending volume, engagement, complaints, and consistency.

Email Types to Understand

Not every email has the same purpose.

Transactional email

A message connected to a specific action, such as a confirmation, receipt, appointment notice, password reset, or document update.

Marketing email

A message sent to promote, educate, nurture, re-engage, or move someone toward a business goal.

Nurture email

A planned sequence that educates or follows up over time.

Broadcast email

A one-time message sent to a selected list or segment.

Internal notification

A message sent to the team, not the contact.

Note

Each type needs the right audience, timing, footer, unsubscribe handling, and expectation. Do not treat every email like a promotional campaign.

Anatomy of a Working Email

From name and reply-to

A real person or brand the recipient recognizes. Reply-to must be monitored.

Subject line

Short, specific, no clickbait. Preview text extends the subject, it does not repeat it.

Header

Minimal. A single line of context or a small logo. Avoid heavy hero images.

Body

Short paragraphs, one idea per paragraph. Written to be read on a phone.

One primary CTA

A single specific action. Book a call, download the resource, reply with an answer.

Footer

Physical address, unsubscribe link, and a plain-text way to contact you.

HTML vs Plain Text Thinking

HTML can help with layout, branding, buttons, and structure, but the email still needs to feel readable and human.

A good HTML email should still work if the images do not load. The main message, CTA, and contact information should be visible as text.

Use HTML for structure, not clutter.

Use a simple single-column layout
Keep the width mobile-friendly
Use readable font sizes
Use buttons and text links carefully
Include alt text for important images
Avoid putting the entire message inside one image
Keep branding light
Make sure the CTA is visible without scrolling too far

Note

Plain-looking emails often perform better than over-designed emails when the goal is a reply, booking, or conversation.

Campaign Planning

?What is the single goal of this campaign?
?Who is on the list and how did they opt in?
?How many emails and over what timing?
?What is the CTA on each email?
?What is the branching logic when the goal is achieved?
?Which workflow will deliver this campaign?
?What action proves the campaign worked?
?What should happen when the person clicks?
?What should happen when the person replies?
?What should happen when the person books?
?What should happen when the person unsubscribes?
?What list, smart list, tag, or segment should receive this?
?Who should be excluded?
?When should the campaign stop?
?What workflow starts or stops this sequence?
?What will be measured after sending?

Note

A campaign should not continue after its goal has been met. If the goal is to book a call, the sequence should stop or change once the contact books.

Simple 5-Email Nurture Structure

A basic nurture sequence does not need to be complicated.

Email 1: Confirmation or welcome

Confirm why the person is receiving the email and set expectations.

Email 2: Education

Teach one useful idea related to the problem they care about.

Email 3: Problem awareness

Explain the common mistake, risk, or missed opportunity.

Email 4: Option or solution explanation

Show the path forward without over-selling.

Email 5: Clear next step

Ask the reader to book, reply, download, call, or take one specific action.

Note

Each email should have one main idea and one primary CTA.

Campaign-to-Workflow Connection

Campaigns rarely live alone. They are usually delivered by a workflow, stopped by a workflow, or connected to a pipeline event.

Before sending, decide:

?What workflow sends this campaign?
?What trigger starts the sequence?
?What audience enters the sequence?
?What tags or fields are required?
?What pipeline stage should start it?
?What event should stop it?
?What happens when someone replies?
?What happens when someone books?
?What happens when someone clicks but does not book?
?What happens when someone unsubscribes?
?What internal notification or task should be created?

Note

The campaign is the message plan. The workflow is only the delivery system.

Pre-Send Checklist for Every Email

Rendered on desktop and mobile
Every link clicked and verified
From name, reply-to, subject, and preview text set
Footer, address, and unsubscribe present
Test send to a live inbox, not just the preview
Confirmed the workflow or campaign is connected to the correct audience
Subject line matches the email content
Preview text is written
Email is readable without images
Images have alt text where needed
CTA appears as a button or clear text link
Plain text or fallback version is reviewed if available
Unsubscribe link works
Physical address is correct
Reply-to inbox is monitored
Audience and exclusions are confirmed
Workflow entry and stop logic are confirmed
Test send is reviewed in at least one real inbox
Links are checked on mobile
UTM or tracking links are used only when needed and tested

Performance Review After Sending

After a campaign sends, review what happened.

Look at:

Delivery rate
Bounce rate
Open rate, if available
Click rate
Replies
Bookings or conversions
Unsubscribes
Spam complaints
Failed sends
Workflow history
Contacts who clicked but did not convert
Contacts who replied and need human follow-up

Note

Do not judge the campaign by opens alone. A lower-open email that gets replies, bookings, or qualified conversations may be more valuable than a high-open email with no action.

What to Build

A mobile-friendly base template with header, body, CTA, and footer
A plain-text-aware email structure
A short campaign plan with sequence timing
One clear CTA per email
A tested CTA destination
A campaign-to-workflow connection
A stop condition when the campaign goal is achieved
Audience and exclusion rules
Footer, physical address, and unsubscribe handling
SPF, DKIM, and DMARC verified on the sending domain
A live inbox testing routine
A basic performance review routine

Before You Build in the CRM

Plan the campaign before opening the email builder. Do not start with colors, buttons, or layout. Start with the goal, audience, offer, timing, and next step.

Start outside the CRM. Use a document, spreadsheet, whiteboard, Figma board, or your preferred AI assistant to map the campaign. Write the purpose of the sequence, the audience, the email topics, the CTA for each email, the timing, and the workflow connection.

Your campaign plan should answer:

?What is the goal of this campaign?
?Who should receive it?
?Who should be excluded?
?How did this audience opt in?
?What email type is this: transactional, marketing, nurture, broadcast, or internal?
?What is the CTA?
?Where does the CTA link?
?What happens if the contact replies?
?What happens if the contact books?
?What happens if the contact clicks but does not convert?
?What happens if the contact unsubscribes?
?What workflow starts this campaign?
?What workflow stops this campaign?
?What tags, fields, or pipeline stages control entry?
?What footer, address, and unsubscribe requirements apply?
?How will the campaign be tested before sending?
?What metrics will be reviewed after sending?

Note

Suggested AI prompt: “I am planning an email campaign for my CRM before building it. Help me define the campaign goal, audience, exclusions, email sequence, timing, CTA for each email, workflow trigger, stop conditions, reply handling, unsubscribe handling, deliverability risks, mobile-readability checks, and pre-send testing checklist. Keep the emails clear, short, and focused on one action per message.” The email builder should be where the plan is assembled, not where the strategy is invented.

Step-by-Step Training

1
Decide the single goal of the campaign.
2
Define the audience and exclusions.
3
Confirm the audience consent/source status.
4
Decide the email type: transactional, marketing, nurture, broadcast, or internal.
5
Draft the sequence outline before touching the builder.
6
Write the CTA for each email.
7
Confirm where each CTA links.
8
Verify SPF, DKIM, and DMARC on the sending domain.
9
Build the base template with a mobile-first layout.
10
Write short, direct copy with one clear CTA per email.
11
Add footer, physical address, unsubscribe, and contact information.
12
Check that the email is readable without images.
13
Test on desktop and mobile.
14
Click every link.
15
Send a live test to a real inbox.
16
Review from name, reply-to, subject line, and preview text.
17
Connect the campaign to the correct workflow or manual send plan.
18
Confirm stop conditions when the campaign goal is met.
19
Send to a small or controlled audience first when appropriate.
20
Review delivery, bounce, click, reply, unsubscribe, and complaint data after sending.

Practical Exercise

Part 1: Build the Base Template

Create one reusable template that every email in the sequence can use:

1
Minimal header or logo
2
Readable body block
3
Single-column mobile-friendly layout
4
Single primary CTA
5
Text link fallback if using a button
6
Footer with physical address and unsubscribe
7
Reply-to contact information
8
Verified render on desktop and mobile

Part 2: Plan and Build the 5-Email Nurture

Build a 5-email nurture sequence. For each email, define the main idea, the CTA, the send timing, the stop condition, and the workflow connection:

1
Email 1: Welcome or confirmation
2
Email 2: Education
3
Email 3: Problem awareness
4
Email 4: Option or service explanation
5
Email 5: Clear next step
6
Define the main idea for each email
7
Define the CTA for each email
8
Define the send timing for each email
9
Define the stop condition for each email
10
Define the workflow connection for each email

Part 3: Test and Review the Campaign

Before sending, verify:

1
SPF, DKIM, and DMARC are configured
2
Audience and exclusions are correct
3
The workflow trigger is correct
4
Stop conditions are active
5
Every email renders on mobile
6
Every link works
7
Footer and unsubscribe are present
8
Reply-to inbox is monitored
9
A live test send was received
10
Performance metrics will be reviewed after sending

Done Means Done Checklist

✓SPF, DKIM, and DMARC are configured on the sending domain
✓The campaign goal is clear
✓The audience is defined
✓Exclusions are defined
✓Consent/source status is reviewed
✓The email type is understood
✓The sequence timing is documented
✓Each email has one main idea
✓Each email has one primary CTA
✓CTA links are tested
✓The email template is mobile-friendly
✓The email is readable without images
✓Footer and physical address are present
✓Unsubscribe link is present and tested
✓Reply-to inbox is monitored
✓A live test send has been received and reviewed
✓Desktop and mobile rendering are checked
✓The campaign is connected to the correct workflow
✓Stop conditions are documented
✓Bounce and complaint monitoring is planned
✓Performance review is scheduled after sending

Common Mistakes

Watch for these

Designing before writing
Sending five emails in five days with no branching
Forgetting to update from-name and reply-to
Ignoring bounce and spam reports for the first sends
Skipping domain authentication and shipping straight to broadcast
Making the email beautiful before the message is clear
Using image-only emails
Sending from an unauthenticated domain
Sending to old or unclear lists
Using too many CTAs in one email
Forgetting exclusion rules
Forgetting to stop the campaign after the goal is met
Sending before testing links on mobile
Ignoring replies because the reply-to inbox is not monitored
Judging success only by open rate
Not reviewing bounces, complaints, and unsubscribes after sending

Related SOPs

Email Campaigns
Workflows
Conversations
Contact Importing
SMS and A2P Awareness
Cleanup and Audit

Next lesson

Week 8: Lead Capture Assets: Forms, Documents, QR Codes, and Social Media

Start Week 8