Intern
What you actually do
Paper jobs, then one spine. Reply and exclusion tests. You are not 'doing email marketing'. You are installing manners.
Library / System / GoHighLevel email is operator mail inside the CRM you already pay for
GHL email fails when it is used as a cheap Mailchimp: whole-account blasts, no sunset, replies in someone’s Gmail, and a 30-email 'value ladder' nobody will still send in six months. The operating layer is a short spine on relationship segments, Conversations as the inbox, domain auth, and campaigns as pulses on top — not as the system. This hub is how to install that layer without a second ESP 'for now'.
GHL email fails when it is used as a cheap Mailchimp: whole-account blasts, no sunset, replies in someone’s Gmail, and a 30-email 'value ladder' nobody will still send in six months. The operating layer is a short spine on relationship segments, Conversations as the inbox, domain auth, and campaigns as pulses on top — not as the system. This hub is how to install that layer without a second ESP 'for now'.
Write five jobs on paper before the builder: orient, prove, objection, ask, last look. Two jobs in one letter is a broadcast wearing a sequence hat.
If you need a discount in email two, the offer is unclear. Price panic is not nurture.
Replies that land in personal Gmail train people to shout into a void and lose the thread when a hire starts.
Sunset is respect for the inbox — including your domain. Forever-nurture is how you become noise and then blame deliverability.
A second ESP 'because GHL email is limited' is allowed only if GHL still owns state. Two newsletters is a tax on customers.
Intern
Paper jobs, then one spine. Reply and exclusion tests. You are not 'doing email marketing'. You are installing manners.
Operator
Spine first. Pulses on segments. Conversations. Sunset. Second ESP only with state still in GHL.
CEO
Broadcast volume is not a system. A spine with stops and an inbox with an owner is. Until that exists, more copy is more noise.
GHL campaign/workflow email, from-domain, Conversations replies, smart list/segment, spine (5–7), sunset tag, campaign pulse, suppression of booked/paid.
Write-in → spine enroll; email 1 orients, does not discount
Reply → Conversations on the contact; spine pauses
Unengaged N days → sunset; off blast lists
Campaign pulse → segments, not the whole sub-account; spine members excluded when jobs collide
Subject lines and jobs on paper. Distinct. No builder until the jobs exist.
Why: Builder-first is how you get one long letter split by waits.
Done when: Each email named in three words.
Enrollment on form/book, not Friday import. Email one within an hour on a test.
Why: Intent dies in the weekend gap.
Done when: Throwaway submit receives email one.
From-address and reply path on the contact. Owner. Sequence stops or pauses.
Why: The spine is a conversation starter. A black hole is a broadcast.
Done when: Reply test creates a visible thread and pauses the job.
Lead vs booked-not-held vs customer vs sunset. Never 'the whole account' as a habit.
Why: Whole-account is how customers get acquire copy.
Done when: A customer is not in the lead spine or the acquire blast.
Silence rule in days. Goodbye, then suppress. Campaigns are dated pulses on lists that exclude spine collisions.
Why: Campaigns doing the spine’s job is how you skip building the spine.
Done when: Unengaged off the next blast. Pulse has a date and a segment.
Five jobs on paper. Build that only. Test enroll, reply pause, customer exclusion, sunset window on a test contact. Do not load a 30-email snapshot. Do not send a whole-account 'we’re back'.
A second ESP, a copywriter for weekly essays, or an AI sender until the spine, Conversations, and sunset exist. More volume on an unowned list is a domain tax.
Snapshot 20-email machine. Replies to a personal inbox. Blast to all. Customers in acquire. Unengaged forever. Domain new or unauthenticated. That is Mailchimp-cosplay inside a CRM.
Enroll, reply pause, booked/paid excluded, sunset defined, campaign not whole-account. Auth records exist (see deliverability). A stranger can name the five jobs.
Fix auth, hygiene, and sunset first. Moving a dirty list to Klaviyo or Mailchimp moves the bill. If you still need an ESP, GHL must keep state.
Because you will still send them in six months. Email eight waits until 1–5 have jobs and stops.
A weekly pulse can exist. It is not nurture. Without a spine and sunset, the weekly is how you train mute.
This week
This week: five jobs, same-day enroll, Conversations replies, relationship segments, sunset rule. No whole-account send.
Until stages, fields, and write-in have owners, the sub-account is a filing cabinet.
Read ↗If every automation can fire, none of them is an operating system.
Read ↗If the thank-you does not change the contact, you paid for a brochure.
Read ↗If campaigns do the work of flows, the list is large and the list is not alive.
Read ↗Working notes
The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.