CRM and Lifecycle skill 11 of 13

SMS and WhatsApp Lifecycle Messaging SKILL.md

The SMS and WhatsApp Lifecycle skill makes Claude, Codex or another AI agent use messaging channels for the moments that matter. It sets channel roles by urgency and cost, explicit per-channel consent, US 10DLC registration and UK, EU and Nigerian rules, WhatsApp template categories and per-message pricing since July 2025, utility and marketing flows, message copy, frequency caps, quiet hours, cost forecasts and incremental measurement.

sms-whatsapp-lifecycle/SKILL.md, version 1.0.0, 1,507 words.

SMS and WhatsApp reach people where they actually look: most messages are read within minutes. That power cuts both ways. Each message costs money, interrupts someone's day and needs explicit consent in most markets. Used well, these channels handle the moments that matter: delivery updates, appointment reminders, abandoned carts with real urgency, payment failures and conversations. Used badly, they become expensive spam that gets blocked.

This skill decides what belongs on SMS and WhatsApp, sets consent and compliance, designs message flows and templates, manages costs and measures incremental impact.

Channel roles

ChannelStrengthsWatch out forBest for
SMSUniversal, fast, no app neededCost per message, strict consent rules, carrier filtering, character limitsTime-critical alerts, short reminders, two-way confirmations
WhatsApp Business PlatformRich media, buttons, two-way conversations, dominant in many markets (for example Nigeria, India, Brazil)Template approval, message categories and per-message pricing, opt-in requirementsOrder and appointment updates, support conversations, considered offers
EmailCheap, long-form, permanentLower attentionEducation, newsletters, detail
Push and in-appFree, contextualRequires app and permissionProduct nudges

WhatsApp pricing and categories (2026)

Since 1 July 2025 Meta charges per delivered template message rather than per conversation. Price depends on the market and category (marketing, utility, authentication). Utility templates sent inside an open 24-hour customer service window are free; marketing templates are always charged. Meta may change rates only on the first day of a quarter. [Confirmed, Meta developer documentation] Check current rate cards before forecasting costs.

Operating principles

  1. Consent per channel, recorded. SMS and WhatsApp consent must be explicit and separate from email consent in most markets.
  2. Earn the interruption. Send only what is time-sensitive, personal or requested.
  3. Classify messages correctly. Utility (order, account, appointment) and marketing messages follow different rules and prices.
  4. Make opting out easy. STOP keywords for SMS; clear opt-out for WhatsApp.
  5. Measure incrementality. Many SMS "conversions" would have happened from email alone.

Compliance essentials (check local law)

MarketKey points
United StatesTCPA consent rules for marketing texts; carrier registration for A2P 10DLC (brand and campaign registration); quiet hours rules in some states; honour STOP
United KingdomPECR requires prior consent for marketing texts (soft opt-in for existing customers in limited cases); clear opt-out
European UnionGDPR and ePrivacy consent; record proof
NigeriaNDPA data protection rules; NCC regulations and do-not-disturb rules for SMS
WhatsApp everywhereMeta's opt-in requirements and Business Messaging Policy; template approval

This is not legal advice; confirm with counsel for each market.

When to use, and when not to

Use it when adding SMS or WhatsApp to lifecycle, when costs rise without clear return, when opt-out rates are high, or in markets where WhatsApp leads.

Don't use it for email-only programmes (lifecycle-email-copy-design) or for deliverability on email (email-deliverability).

Inputs to ask for, in one message

  1. Markets and audiences, and which channels customers use there.
  2. Provider and setup (for example Attentive, Postscript, Klaviyo SMS, Twilio, a WhatsApp Business Solution Provider).
  3. Consent capture method and records.
  4. Current flows, volumes, costs, opt-out and conversion rates.
  5. WhatsApp templates and their categories, if used.

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as sms-whatsapp-lifecycle/SKILL.md.

---
name: sms-whatsapp-lifecycle
description: "Use SMS and WhatsApp for the lifecycle moments that matter: channel roles by urgency and cost, explicit per-channel consent, US 10DLC registration, UK PECR, EU and Nigerian rules, WhatsApp template categories and per-message pricing since July 2025, utility and marketing flows, message copy, frequency caps, quiet hours, cost forecasts and incremental measurement. Use whenever someone asks about SMS marketing, WhatsApp marketing, WhatsApp Business API, text message flows, 10DLC, SMS consent, WhatsApp template pricing or adding messaging channels to lifecycle."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/crm-lifecycle/sms-whatsapp-lifecycle/
  category: marketing
  subcategory: crm-lifecycle
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# SMS and WhatsApp Lifecycle Messaging

SMS and WhatsApp reach people where they actually look: most messages are read within minutes. That power cuts both ways. Each message costs money, interrupts someone's day and needs explicit consent in most markets. Used well, these channels handle the moments that matter: delivery updates, appointment reminders, abandoned carts with real urgency, payment failures and conversations. Used badly, they become expensive spam that gets blocked.

This skill decides what belongs on SMS and WhatsApp, sets consent and compliance, designs message flows and templates, manages costs and measures incremental impact.

## Channel roles
| Channel | Strengths | Watch out for | Best for |
|---|---|---|---|
| SMS | Universal, fast, no app needed | Cost per message, strict consent rules, carrier filtering, character limits | Time-critical alerts, short reminders, two-way confirmations |
| WhatsApp Business Platform | Rich media, buttons, two-way conversations, dominant in many markets (for example Nigeria, India, Brazil) | Template approval, message categories and per-message pricing, opt-in requirements | Order and appointment updates, support conversations, considered offers |
| Email | Cheap, long-form, permanent | Lower attention | Education, newsletters, detail |
| Push and in-app | Free, contextual | Requires app and permission | Product nudges |

## WhatsApp pricing and categories (2026)
Since 1 July 2025 Meta charges per delivered template message rather than per conversation. Price depends on the market and category (marketing, utility, authentication). Utility templates sent inside an open 24-hour customer service window are free; marketing templates are always charged. Meta may change rates only on the first day of a quarter. [Confirmed, Meta developer documentation] Check current rate cards before forecasting costs.

## Operating principles
1. **Consent per channel, recorded.** SMS and WhatsApp consent must be explicit and separate from email consent in most markets.
2. **Earn the interruption.** Send only what is time-sensitive, personal or requested.
3. **Classify messages correctly.** Utility (order, account, appointment) and marketing messages follow different rules and prices.
4. **Make opting out easy.** STOP keywords for SMS; clear opt-out for WhatsApp.
5. **Measure incrementality.** Many SMS "conversions" would have happened from email alone.

## Compliance essentials (check local law)
| Market | Key points |
|---|---|
| United States | TCPA consent rules for marketing texts; carrier registration for A2P 10DLC (brand and campaign registration); quiet hours rules in some states; honour STOP |
| United Kingdom | PECR requires prior consent for marketing texts (soft opt-in for existing customers in limited cases); clear opt-out |
| European Union | GDPR and ePrivacy consent; record proof |
| Nigeria | NDPA data protection rules; NCC regulations and do-not-disturb rules for SMS |
| WhatsApp everywhere | Meta's opt-in requirements and Business Messaging Policy; template approval |
This is not legal advice; confirm with counsel for each market.

## When to use, and when not to
Use it when adding SMS or WhatsApp to lifecycle, when costs rise without clear return, when opt-out rates are high, or in markets where WhatsApp leads.

Don't use it for email-only programmes (`lifecycle-email-copy-design`) or for deliverability on email (`email-deliverability`).

## Inputs to ask for, in one message
1. Markets and audiences, and which channels customers use there.
2. Provider and setup (for example Attentive, Postscript, Klaviyo SMS, Twilio, a WhatsApp Business Solution Provider).
3. Consent capture method and records.
4. Current flows, volumes, costs, opt-out and conversion rates.
5. WhatsApp templates and their categories, if used.

## Workflow

### Step 1. Decide channel roles
For each journey moment, choose the channel by urgency, richness and cost. SMS and WhatsApp should add something email can't.

### Step 2. Set up consent
Separate checkboxes or keyword opt-ins, clear wording on what and how often, double opt-in where appropriate, records with source and timestamp.

### Step 3. Register and configure
For US SMS, complete 10DLC brand and campaign registration (or use toll-free verification or short codes). For WhatsApp, verify the business, set display name, and create templates in the right categories.

### Step 4. Design flows
Transactional and utility first (order, delivery, appointments, payment failure), then high-intent marketing (cart abandonment with stock or price urgency, back-in-stock, early access for subscribers who asked).

### Step 5. Write messages
Identify the brand first, keep SMS short, one link, clear opt-out language where required, no misleading urgency. For WhatsApp, use buttons for common replies and route replies to people or support.

### Step 6. Set frequency and quiet hours
Cap marketing texts per week, respect local quiet hours and time zones, and suppress SMS when the same message just went by email and was acted on.

### Step 7. Manage costs
Forecast by message count, market and category. Use utility templates inside the service window where appropriate; avoid sending marketing templates to low-value segments.

### Step 8. Measure
Incremental conversions against holdouts, revenue per message after cost, opt-out rate, reply rate and support deflection.

## Message examples
| Moment | SMS | WhatsApp |
|---|---|---|
| Shipped | "[Brand]: your order is on its way, arriving Thu. Track: [link]" | Utility template with tracking button |
| Payment failed | "[Brand]: your payment didn't go through. Update in 1 min: [link] Reply STOP to opt out" (where marketing rules apply) | Utility template with update button |
| Back in stock | "[Brand]: the [item] you wanted is back. [link]" | Marketing template with image and buy button |
| Appointment | "[Brand]: reminder, your appointment is tomorrow 10:00. Reply C to confirm" | Utility template with confirm and reschedule buttons |

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Same message on email and SMS | Send SMS only if email isn't acted on within a set time |
| WhatsApp template rejected or reclassified | Rewrite to fit the category; don't disguise marketing as utility |
| High opt-out after a campaign | Check frequency, relevance and timing; pause similar sends |
| International numbers | Format in E.164, respect each country's rules and costs |
| Customers reply with questions | Route to support; a conversation is the channel's main advantage |

## Handoffs to related skills
- Consent records: `crm-data-hygiene`
- Journey timing: `customer-journey-mapping`
- Dunning and retention: `retention-churn-prevention`
- Win-back with consent: `win-back-reactivation`
- Holdouts: `lifecycle-experimentation`
- Cost and revenue reporting: `lifecycle-reporting-attribution`

## Worked example
An online fashion retailer in Lagos sent marketing by email and SMS, with high SMS costs and weak results. Customer research showed most buyers preferred WhatsApp. The team moved order updates to WhatsApp utility templates (free inside the service window when customers had messaged recently), added a back-in-stock marketing template for customers who requested alerts, routed replies to customer service and kept SMS only for delivery-day alerts. A holdout showed the back-in-stock template drove incremental sales, messaging costs fell, and support calls about order status dropped.

## Output format
```
# SMS and WhatsApp plan: <business>, <markets>, <date>
## Channel roles by journey moment
## Consent and compliance by market
## Registration and template setup
## Flows and message copy
## Frequency, quiet hours and suppression rules
## Cost forecast by market and category
## Measurement with holdouts
```

## Common mistakes
- Using SMS as a copy of email.
- Consent bundled with email or buried in terms.
- Marketing disguised as utility templates.
- Ignoring quiet hours and time zones.
- Counting attributed revenue without holdouts or costs.

## Questions to ask before you design
- Which messaging apps do customers in each market prefer?
- How is SMS and WhatsApp consent captured and recorded?
- What does each message cost by market and category?

## Self-check before you answer
- Is consent explicit, per channel and recorded?
- Does every message earn the interruption?
- Are templates in the right categories and costs forecast?
- Is impact measured incrementally after cost?

## Official documentation
- WhatsApp Business Platform pricing: https://developers.facebook.com/docs/whatsapp/pricing
- WhatsApp Business Messaging Policy: https://business.whatsapp.com/policy
- CTIA messaging principles and best practices: https://www.ctia.org/
- UK ICO guidance on electronic marketing: https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/crm-lifecycle/sms-whatsapp-lifecycle/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Decide channel roles

For each journey moment, choose the channel by urgency, richness and cost. SMS and WhatsApp should add something email can't.

Separate checkboxes or keyword opt-ins, clear wording on what and how often, double opt-in where appropriate, records with source and timestamp.

Step 3. Register and configure

For US SMS, complete 10DLC brand and campaign registration (or use toll-free verification or short codes). For WhatsApp, verify the business, set display name, and create templates in the right categories.

Step 4. Design flows

Transactional and utility first (order, delivery, appointments, payment failure), then high-intent marketing (cart abandonment with stock or price urgency, back-in-stock, early access for subscribers who asked).

Step 5. Write messages

Identify the brand first, keep SMS short, one link, clear opt-out language where required, no misleading urgency. For WhatsApp, use buttons for common replies and route replies to people or support.

Step 6. Set frequency and quiet hours

Cap marketing texts per week, respect local quiet hours and time zones, and suppress SMS when the same message just went by email and was acted on.

Step 7. Manage costs

Forecast by message count, market and category. Use utility templates inside the service window where appropriate; avoid sending marketing templates to low-value segments.

Step 8. Measure

Incremental conversions against holdouts, revenue per message after cost, opt-out rate, reply rate and support deflection.

Message examples

MomentSMSWhatsApp
Shipped"[Brand]: your order is on its way, arriving Thu. Track: [link]"Utility template with tracking button
Payment failed"[Brand]: your payment didn't go through. Update in 1 min: [link] Reply STOP to opt out" (where marketing rules apply)Utility template with update button
Back in stock"[Brand]: the [item] you wanted is back. [link]"Marketing template with image and buy button
Appointment"[Brand]: reminder, your appointment is tomorrow 10:00. Reply C to confirm"Utility template with confirm and reschedule buttons

Edge cases and judgement calls

SituationWhat to do
Same message on email and SMSSend SMS only if email isn't acted on within a set time
WhatsApp template rejected or reclassifiedRewrite to fit the category; don't disguise marketing as utility
High opt-out after a campaignCheck frequency, relevance and timing; pause similar sends
International numbersFormat in E.164, respect each country's rules and costs
Customers reply with questionsRoute to support; a conversation is the channel's main advantage
  • Consent records: crm-data-hygiene
  • Journey timing: customer-journey-mapping
  • Dunning and retention: retention-churn-prevention
  • Win-back with consent: win-back-reactivation
  • Holdouts: lifecycle-experimentation
  • Cost and revenue reporting: lifecycle-reporting-attribution

Worked example

An online fashion retailer in Lagos sent marketing by email and SMS, with high SMS costs and weak results. Customer research showed most buyers preferred WhatsApp. The team moved order updates to WhatsApp utility templates (free inside the service window when customers had messaged recently), added a back-in-stock marketing template for customers who requested alerts, routed replies to customer service and kept SMS only for delivery-day alerts. A holdout showed the back-in-stock template drove incremental sales, messaging costs fell, and support calls about order status dropped.

Output format

# SMS and WhatsApp plan: <business>, <markets>, <date>
## Channel roles by journey moment
## Consent and compliance by market
## Registration and template setup
## Flows and message copy
## Frequency, quiet hours and suppression rules
## Cost forecast by market and category
## Measurement with holdouts

Common mistakes

  • Using SMS as a copy of email.
  • Consent bundled with email or buried in terms.
  • Marketing disguised as utility templates.
  • Ignoring quiet hours and time zones.
  • Counting attributed revenue without holdouts or costs.

Questions to ask before you design

  • Which messaging apps do customers in each market prefer?
  • How is SMS and WhatsApp consent captured and recorded?
  • What does each message cost by market and category?

Self-check before you answer

  • Is consent explicit, per channel and recorded?
  • Does every message earn the interruption?
  • Are templates in the right categories and costs forecast?
  • Is impact measured incrementally after cost?

Official documentation

When to use this skill, and when not to

Use it when adding SMS or WhatsApp to lifecycle, when messaging costs rise without clear return, when opt-out rates are high, or in markets where WhatsApp is how customers prefer to talk to businesses.

Messages are read within minutes, which makes these channels powerful for delivery updates, appointment reminders, payment failures and conversations, and expensive spam when used as a copy of email. Since 1 July 2025 Meta charges per WhatsApp template message, with utility templates free inside an open 24-hour service window, so planning matters.

Don’t use it for email-only programmes (use Lifecycle Email Copy and Design).

Example prompts

  • “Should our Lagos store move order updates to WhatsApp?”
  • “Set up SMS consent and 10DLC registration for our US launch.”
  • “Forecast WhatsApp costs by market and template category.”
  • “Write SMS and WhatsApp versions of our payment failure message.”
  • “Our SMS opt-outs doubled. What went wrong?”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# SMS and WhatsApp plan: example fashion retailer, Nigeria, 10 October 2026

## Channel roles
| Moment | Channel | Category |
| Order shipped | WhatsApp | Utility (free inside service window) |
| Back in stock (requested) | WhatsApp | Marketing |
| Delivery day | SMS | Transactional |
| Newsletter | Email | n/a |

## Rules
Marketing messages max 2 per week; quiet hours 21:00-08:00 local; replies routed to customer service

## Measurement: holdout on back-in-stock template

Compliance points are flagged per market with a recommendation to confirm with counsel; the skill is not legal advice.

What the agent needs from you

The skill asks for your markets and audiences and which channels customers use there, your SMS or WhatsApp provider, how consent is captured and recorded, current flows with volumes, costs, opt-out and conversion rates, and your WhatsApp templates and their categories if you use them.

How this skill hands off to related skills

Messaging channels connect to the rest of the set. Consent records come from CRM Data Hygiene, timing from Customer Journey Mapping, dunning from Retention and Churn Prevention, consented win-back from Win-Back, holdouts from Lifecycle Experimentation and cost-aware reporting from Lifecycle Reporting.

How to run SMS and WhatsApp Lifecycle step by step

  1. Install the skill as sms-whatsapp-lifecycle/SKILL.md.
  2. Name your markets and the messaging apps customers use there.
  3. Share your provider setup and how consent is captured.
  4. Export current flows with volumes, costs, opt-outs and conversions.
  5. Review channel roles, compliance notes, templates and cost forecasts.
  6. Launch with frequency caps and a holdout, then review monthly.

Situations this skill handles

Messaging channels fail when they copy email or ignore consent. The skill handles these situations:

SituationWhat the skill does
SMS repeats every emailSends SMS only for time-critical moments or unacted emails
WhatsApp-first marketMoves order updates and support to WhatsApp utility templates
Template rejected or reclassifiedRewrites the message to fit the correct category
Opt-outs spikeReviews frequency, relevance and timing
US launchPlans TCPA consent and 10DLC registration
Customers reply with questionsRoutes replies to people or support

What makes this skill different

Most SMS advice treats it as a faster email blast. This skill decides what earns the interruption, classifies messages correctly as utility or marketing, records consent per channel and forecasts cost by market and category before anything is sent.

It also measures incrementally after cost. Many SMS conversions would have happened from email alone, so a holdout is the only way to know whether the channel pays.

Practical tips from real projects

  • Brand first in every SMS so people know who is texting.
  • Respect quiet hours and time zones.
  • One link per SMS; buttons for common WhatsApp replies.
  • Reply handling is the point of WhatsApp; staff it.

A worked example: an online fashion retailer in Lagos sent marketing by email and SMS, with high SMS costs and weak results. Research showed most buyers preferred WhatsApp. Order updates moved to WhatsApp utility templates, free when sent inside the service window after recent customer messages; a back-in-stock marketing template went to customers who requested alerts; replies were routed to customer service; and SMS stayed only for delivery-day alerts. A holdout showed the back-in-stock template drove incremental sales, messaging costs fell and order-status calls dropped.

Compliance varies by market. In the US, marketing texts need TCPA-compliant consent and business numbers need 10DLC registration. In the UK, PECR requires prior consent for marketing texts, with a narrow soft opt-in for existing customers. The EU applies GDPR and ePrivacy consent. In Nigeria, the NDPA governs data and NCC rules govern SMS. On WhatsApp everywhere, Meta’s opt-in requirements and Business Messaging Policy apply.

Cost control is part of the design: forecast by message count, market and category, use utility templates inside the service window where appropriate and avoid sending marketing templates to low-value segments where the expected return doesn’t cover the price.

The skill includes message examples for shipping, payment failure, back-in-stock and appointment moments in both SMS and WhatsApp form, plus suppression rules that stop SMS when the same message was already acted on by email.

Frequency caps protect the channel: a weekly limit on marketing messages, and no SMS if the same message was opened and acted on by email.

Channel roles summarise the approach. SMS is universal and fast, but costs per message and faces strict consent and carrier filtering, so it suits short, time-critical alerts. WhatsApp offers rich media, buttons and two-way conversation and leads in markets such as Nigeria, India and Brazil, but needs approved templates and careful category choices. Email stays the home for education and detail, and push and in-app handle product nudges for free.

Frequently asked questions

Since 1 July 2025 Meta charges per delivered template message, priced by market and category (marketing, utility, authentication). Utility templates inside an open 24-hour customer service window are free.

In most markets, yes, and it must be explicit and separate from email consent. In the US, marketing texts fall under TCPA rules and business texting needs 10DLC registration.

A US system for business texting from standard ten-digit numbers, requiring brand and campaign registration with carriers.

Yes, with opt-in and approved marketing templates. Disguising marketing as utility breaks Meta’s rules and risks template rejection.

For time-critical, short messages: delivery alerts, appointment reminders, payment failures and verification. Send SMS after email only if the email wasn’t acted on.

Compare a holdout that receives email only with a group that also gets SMS, and subtract message costs.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.