lifecycle-messaging
Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set
Install
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/lifecycle-messaging
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cbrock84-headcount@llmmart
git clone https://github.com/cbrock84/headcount.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole cbrock84/headcount collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Lifecycle messaging
Map the lifecycle before writing any message
For each stage, name what the person is trying to do and what would move them forward. Messages written without that answer become announcements, and announcements get unsubscribed from.
The stages that matter: just signed up, activated but not habitual, habitual, at risk, lapsed. Most programs over-invest in the first and neglect at-risk entirely, which is where the money is.
The welcome sequence
The highest-engagement messages you will ever send. Do not waste them on company history.
- Immediate — deliver whatever was promised, plus the single next action.
- Within days — the fastest route to first value, one step.
- After that — the use case most people miss, or the objection most people have.
Set expectations early: what you send, how often. It reduces unsubscribes more than any subject-line technique.
Timing and cadence
Trigger on behavior, not the calendar, wherever possible. A message sent because someone did something is many times more relevant than one sent because it is Tuesday.
Cadence sustainable at your worst week. Every message should be one the recipient would miss.
SMS is a different medium
Higher consent bar, higher intrusion, higher cost. Reserve it for time-sensitive and transactional messages — delivery, appointment, security, an expiring window. Marketing SMS at any volume trains people to opt out.
Explicit opt-in, honored opt-out, sending hours respected in the recipient's timezone. These are legal requirements in most jurisdictions, not preferences.
SMS compliance is not optional
Consult qualified counsel before launching an SMS program. The exposure here is statutory damages per message, which is how these become class actions.
In the US, marketing SMS requires express written consent obtained before sending — implied consent, an existing customer relationship, or a phone number collected for another purpose does not qualify. The consent record must show what the person agreed to receive and when, and it must be retained.
The operational requirements that follow:
- Disclose program purpose, frequency, and that message rates may apply, at the point of consent.
- Honor opt-out immediately, on every standard keyword, with a single confirmation message and nothing after it.
- Respect quiet hours in the recipient's timezone, not yours.
- Keep consent and opt-out records for as long as the retention rules require — these records are the entire defense if challenged.
- Never buy or rent SMS lists. Purchased consent is not consent.
Other jurisdictions impose their own rules, and several are stricter. Determine which apply by where recipients are, not where you are.
Subject lines and preview text
They are one unit and get read together. A subject line that works with the preview repeating it wastes the second-most-read text in the message — use the preview to extend the subject, not echo it, and never leave it to default to the first line of the body.
Diagnosing
- Low open — subject line, sender reputation, or list quality. Check deliverability before rewriting subject lines; a reputation problem looks exactly like a copy problem.
- Open but no click — the message did not deliver on the subject, or has no single clear action.
- Click but no conversion — the destination, not the email.
- Rising unsubscribes — frequency or relevance. Usually frequency.
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Tooling
Lifecycle automation: Customer.io, Braze, Iterable, Klaviyo for commerce, HubSpot or Marketo for B2B, and similar.
Transactional sending is a separate job with separate reputation: Postmark, SendGrid, Resend, and similar. Keep it off the marketing domain.
In-product messaging: Intercom, Appcues, Pendo, and similar. An email that should have been an in-app prompt reaches half the audience at best.
Never
- Send to a list that did not opt in.
- Bury the unsubscribe.
- Run a re-engagement program without a plan to actually remove the people who do not re-engage. An unengaged list damages delivery for everyone else.
Files (headcount)
-
references
-
sources.md 2 KB
# Sources — `demand-generation:lifecycle-messaging` <!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. --> Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce. ## CAN-SPAM Act: A Compliance Guide for Business US Federal Trade Commission · US · public domain (US government) — quote freely <https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business> Machine-readable: <https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-316> **Authoritative for:** The mandatory elements of a US commercial email — header accuracy, subject-line honesty, physical address, opt-out mechanism and the window for honoring it — and that hiring an agency does not move the liability. ## Canada's Anti-Spam Legislation, S.C. 2010 c. 23 Department of Justice Canada · CA · free to use with attribution — credit the publisher <https://laws-lois.justice.gc.ca/eng/acts/E-1.6/index.html> **Authoritative for:** Whether you may send a commercial message to a Canadian address at all. CASL is opt-in by default, which inverts the US assumption, and this is the text governing express versus implied consent. ## Delivery restrictions and telephone solicitation rules, 47 CFR 64.1200 US Federal Communications Commission · US · public domain (US government) — quote freely <https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200> **Authoritative for:** The consent standard for marketing SMS and autodialed calls — what prior express written consent requires, how revocation must be handled, and the identification rules. Read the current text rather than a summary; this area moves in court. --- Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.
-
-
SKILL.md 4.8 KB
--- name: lifecycle-messaging description: Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and when. --- # Lifecycle messaging ## Map the lifecycle before writing any message For each stage, name what the person is trying to do and what would move them forward. Messages written without that answer become announcements, and announcements get unsubscribed from. The stages that matter: just signed up, activated but not habitual, habitual, at risk, lapsed. Most programs over-invest in the first and neglect at-risk entirely, which is where the money is. ## The welcome sequence The highest-engagement messages you will ever send. Do not waste them on company history. 1. **Immediate** — deliver whatever was promised, plus the single next action. 2. **Within days** — the fastest route to first value, one step. 3. **After that** — the use case most people miss, or the objection most people have. Set expectations early: what you send, how often. It reduces unsubscribes more than any subject-line technique. ## Timing and cadence Trigger on behavior, not the calendar, wherever possible. A message sent because someone did something is many times more relevant than one sent because it is Tuesday. Cadence sustainable at your worst week. Every message should be one the recipient would miss. ## SMS is a different medium Higher consent bar, higher intrusion, higher cost. Reserve it for time-sensitive and transactional messages — delivery, appointment, security, an expiring window. Marketing SMS at any volume trains people to opt out. Explicit opt-in, honored opt-out, sending hours respected in the recipient's timezone. These are legal requirements in most jurisdictions, not preferences. ## SMS compliance is not optional > Consult qualified counsel before launching an SMS program. The exposure here is statutory damages > per message, which is how these become class actions. In the US, marketing SMS requires **express written consent** obtained before sending — implied consent, an existing customer relationship, or a phone number collected for another purpose does not qualify. The consent record must show what the person agreed to receive and when, and it must be retained. The operational requirements that follow: - Disclose program purpose, frequency, and that message rates may apply, at the point of consent. - Honor opt-out immediately, on every standard keyword, with a single confirmation message and nothing after it. - Respect quiet hours in the **recipient's** timezone, not yours. - Keep consent and opt-out records for as long as the retention rules require — these records are the entire defense if challenged. - Never buy or rent SMS lists. Purchased consent is not consent. Other jurisdictions impose their own rules, and several are stricter. Determine which apply by where recipients are, not where you are. ## Subject lines and preview text They are one unit and get read together. A subject line that works with the preview repeating it wastes the second-most-read text in the message — use the preview to extend the subject, not echo it, and never leave it to default to the first line of the body. ## Diagnosing - **Low open** — subject line, sender reputation, or list quality. Check deliverability before rewriting subject lines; a reputation problem looks exactly like a copy problem. - **Open but no click** — the message did not deliver on the subject, or has no single clear action. - **Click but no conversion** — the destination, not the email. - **Rising unsubscribes** — frequency or relevance. Usually frequency. ## Sources `references/sources.md` in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding. ## Tooling Lifecycle automation: Customer.io, Braze, Iterable, Klaviyo for commerce, HubSpot or Marketo for B2B, and similar. Transactional sending is a separate job with separate reputation: Postmark, SendGrid, Resend, and similar. Keep it off the marketing domain. In-product messaging: Intercom, Appcues, Pendo, and similar. An email that should have been an in-app prompt reaches half the audience at best. ## Never - Send to a list that did not opt in. - Bury the unsubscribe. - Run a re-engagement program without a plan to actually remove the people who do not re-engage. An unengaged list damages delivery for everyone else.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.