Intern
What you actually do
DNS screenshots and the exclusion count. You do not send to all to 'test'. You test small and authenticated.
Library / System / Inbox access is part of the system, not a post-mortem after a blast
Deliverability as an operating layer is authentication (SPF, DKIM, DMARC), a list that can sunset, complaint and bounce watched weekly, one sending identity per job, and no panic blasts to museums. The leak is blaming Gmail after a whole-account send, a domain that was 'set up once', and unengaged addresses kept for vanity. This hub is the hygiene layer under GHL email and any ESP you added.
Deliverability as an operating layer is authentication (SPF, DKIM, DMARC), a list that can sunset, complaint and bounce watched weekly, one sending identity per job, and no panic blasts to museums. The leak is blaming Gmail after a whole-account send, a domain that was 'set up once', and unengaged addresses kept for vanity. This hub is the hygiene layer under GHL email and any ESP you added.
Auth is table stakes. If records are missing or a lookalike domain is unverified, you do not have an email system. You have a hope.
List size is not an asset if it cannot reach the inbox. Sunset is how you keep the living list alive.
Whole-account blasts are the usual incident. Segments and permissions exist so this is hard to do by accident.
Moving ESPs with a dirty list moves the reputation problem. Clean, then move, or do not move.
GHL vs Klaviyo vs 'the agency’s Mailchimp' as three senders is how you split reputation and confuse unsubscribes.
Intern
DNS screenshots and the exclusion count. You do not send to all to 'test'. You test small and authenticated.
Operator
Inbox is part of the system. Auth, sunset, complaints, one sender. Move lists only after hygiene.
CEO
A large list that cannot inbox is a liability. Sunset and auth are the layer. Until they exist, more copy is more risk.
Sending domain, SPF/DKIM/DMARC, return-path, list segments, sunset, complaint rate, bounce, warmup if new, one from-name, whole-account ban.
New domain or new ESP → warmup and auth before volume
Unengaged → sunset; not on the next blast
Complaint spike → stop and inspect, not 'send more to get the number down'
One job, one from-identity; customers not on acquire from-names if that would confuse
SPF, DKIM, DMARC aligned enough to pass. Screenshot. Who owns DNS changes.
Why: Unowned DNS is how a 'quick domain change' tanks a quarter.
Done when: A test send authenticates. Records documented.
Where the ESP shows them. Weekly. Threshold that pauses big sends.
Why: Unwatched complaints are how you discover a block late.
Done when: Monday includes the two rates or 'ESP cannot show them' as a ticket.
Definition of unengaged. Suppress. Do not keep them 'for a win-back someday' on the blast list. Win-back is a finite journey on a segment, not the museum.
Why: Vanity size is the tax.
Done when: Next scheduled send excludes sunset. Count of excluded is known.
Permissions, saved segments, a second approver if needed. Incident if someone still does it.
Why: One click can undo months of hygiene.
Done when: A test: intern cannot easily send to all. Process written.
Which domain/ESP for sales nurture vs DTC vs transactional. Kill the third newsletter.
Why: Three senders, one brand, is how people mark spam on the one they remember least.
Done when: A table of senders and jobs. Extras off.
Auth screenshots. Complaint/bounce place in the UI. Sunset definition and a send list that excludes them. Sender table. You are not buying warmup SaaS until records and sunset exist.
A big reactivation blast, a new ESP, or a deliverability tool until auth is true and the museum is off the next send. Volume on a dirty identity is how you buy a block.
Domain set up once. Whole-account 'we’re back'. Unengaged kept. Three ESPs. Blame Gmail. That is a post-mortem culture, not a layer.
Auth passes. Sunset excluded on a real send. Complaints on Monday. One-sender table. Whole-account hard to do. New domain would have a warmup plan.
Open rates are noisy. Complaints, placement, and whether customers still get mail are the system. Fine until a blast.
After auth, sunset, and one-sender are true. Consultants on a museum list and three ESPs will sell you more tools.
Same layer. Different UI. Auth, sunset, complaints, one job per sender. Do not run two sunsets that disagree.
This week
This week: auth, complaint/bounce home, sunset on the next send, sender table, whole-account ban. No reactivation blast.
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 ↗Broadcasts feel like work. A spine with manners is the product.
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.