lifecycle-messaging

# Lifecycle messaging — deliverable, consented, compliant Messages that don't arrive (poor deliverability) or that arrive without consent (TCPA/ CAN-SPAM violations) are both fatal for an SMB product. This skill makes both correct by construction. **Design the consent + deliverability posture before the first send.** ## 1. Transactional vs marketing — split them Decide per message which bucket it is; they have different rules and should use different sending identities (often different subdomains / providers): | | Transactional | Marketing / lifecycle | |---|---|---| | Examples | receipt, booking confirm/reminder, password reset | win-back, promo, newsletter, nurture step | | Consent | implied by the transaction | **explicit opt-in required** | | Unsubscribe | not required (but honor STOP) | **required**, one-click, honored fast | | Sending domain | `txn.` subdomain | `mail.`/`news.` subdomain | Never send marketing content on the transactional channel "because it delivers better" — that's how the transactional domain gets burned. ## 2. Provider selection (pick one, justify it) - **Email** — Postmark (best transactional deliverability, strict on marketing), Resend (DX-first, good default), SendGrid (scale). Default: **Resend for transactional**, add a marketing-grade ESP only when lifecycle volume justifies it. - **SMS** — Twilio (messaging service + sender pool), or Telnyx. Use a Messaging Service, not a single number, for scale + failover. A2P 10DLC registratio...