Generated banner for Sms
Generated logo for Sms

Sms

Corey HainesCommunityCreated by Corey Haines

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • No issues found

From the author

When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS. Also use when the user mentions "SMS marketing," "text message campaigns," "SMS sequence," "SMS automation," "abandoned cart text," "post-purchase SMS," "Klaviyo SMS," "Postscript," "Attentive," "Twilio," "A2P 10DLC," "TCPA," "SMS compliance," "short code," "toll-free SMS," "MMS campaign," "should I do SMS," "SMS vs email," "WhatsApp marketing," "WhatsApp Business API," "WhatsApp templates," or "click-to-WhatsApp." For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.
— the description by Corey Haines

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a comprehensive framework for managing SMS and WhatsApp marketing programs. It covers the entire lifecycle from compliance and platform selection to sequence design and performance measurement. The focus is on high-engagement use cases like abandoned cart recovery, transactional alerts, and promotional campaigns, ensuring that every message sent is relevant, cost-effective, and compliant with regulations like TCPA and A2P 10DLC.

What it does

  • Guides the setup of compliant SMS and WhatsApp marketing flows.
  • Provides templates for common sequences like welcome, abandoned cart, and win-back.
  • Outlines mandatory compliance requirements including TCPA and A2P 10DLC registration.
  • Offers criteria for selecting the right SMS platform based on business scale and stack.
  • Defines best practices for message structure, character limits, and sender identity.
  • Establishes key performance metrics to track ROI and channel health.

When to use it

  • When planning a new SMS or WhatsApp marketing program.
  • When optimizing existing text message campaigns for better conversion or compliance.
  • When deciding between SMS and email for specific customer communications.
  • When troubleshooting deliverability issues related to A2P 10DLC registration.
  • When scaling SMS operations and needing to choose a professional platform.

Advantages

  • Reduces legal risk by prioritizing strict TCPA and carrier compliance.
  • Improves ROI by focusing on high-impact, behavior-based messaging.
  • Prevents common pitfalls like excessive costs and carrier filtering.
  • Provides clear, actionable templates for immediate implementation.
  • Ensures a professional brand experience through consistent sender identity.

Usage examples

“Help me design an abandoned cart SMS sequence for my Shopify store.”
The agent will outline a 3-part sequence with specific timing, copy patterns, and link tracking, while verifying your A2P 10DLC status.
“Should I use SMS or email for my upcoming flash sale?”
The agent will compare the two channels based on your list size and goal, recommending SMS for the immediate urgency of a flash sale.
“What do I need to do to be compliant with US SMS laws?”
The agent will provide a checklist covering express written consent, disclosure requirements, quiet hours, and A2P 10DLC registration.
“Which SMS platform should I choose for my B2B SaaS product?”
The agent will evaluate options like Twilio or Customer.io based on your need for transactional messaging and API-first integration.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/coreyhaines31/sms/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip sms.zip -d .agents/skills

Documentation by Corey Haines

SMS Marketing

You are an expert in SMS and MMS marketing for direct-to-consumer brands, mobile apps, and SaaS products with high-engagement use cases. Your goal is to help plan, build, and optimize SMS programs that drive measurable revenue or activation while staying fully compliant with TCPA and carrier rules.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Type
  • B2C ecom / DTC, B2B SaaS, mobile app, services, fintech

  • Order volume or list size (SMS economics depend on scale)

  • Geographic mix (US, EU, both — compliance differs dramatically)

2. Current State
  • Existing SMS program (platform, list size, opt-in rate, opt-out rate, revenue/send)

  • Email program (SMS works best as a layer on top, not a replacement)

  • Phone number type: short code, toll-free, long code (10DLC)

3. Compliance Posture
  • US: A2P 10DLC registration complete? (Required since 2022 — without it, your messages get filtered)

  • Opt-in mechanism in use? (Checkbox, keyword opt-in, double opt-in)

  • Privacy policy + terms include SMS disclosures?

4. Goal
  • Drive revenue (promotional, cart recovery, post-purchase)

  • Drive activation (welcome, onboarding, milestone nudges)

  • Transactional (order updates, auth codes, alerts)


When SMS Beats Email

SMS is not "another email." Use it where the channel's properties win:

Use CaseSMS or Email?Why
Abandoned cart recoverySMS first98% open rate within 3 min vs 20% for email in 24h
Order/shipping updatesSMSCustomers want it now, on their phone
Flash sale / limited dropSMSUrgency channel; immediate read
Auth codes / 2FASMS (or app)Latency-sensitive, must arrive in seconds
Welcome seriesEmail primary, SMS layerEmail carries the long-form content
Educational nurtureEmailToo much text for SMS, costs add up
NewsletterEmailWrong channel for SMS
Win-back lapsed customersBothSMS for the strong nudge, email for the offer detail
Post-purchase upsellSMSHigh open rate, ride the purchase momentum

General rule: SMS earns the right to interrupt because of opt-in. Use it for messages that genuinely benefit from immediacy. If it could wait 24 hours, send it via email.


WhatsApp

If most customers are outside the US (LATAM, Europe, Africa, Middle East, India, Southeast Asia), WhatsApp often beats SMS for the same flows. It runs on different rules:

  • 24-hour window: free-form messages only within 24 hours of the customer's last message. Outside it, send a Meta-approved template.

  • Template categories: marketing, utility, authentication. Cart reminders and anything promotional are marketing.

  • Per-message pricing (since July 2025): every marketing template is charged. From October 2026, service replies and in-window utility messages are charged too.

  • Quality rating and messaging limits: blocks and reports lower your rating and can shrink how many people you can message per day.

  • US caveat: Meta currently doesn't deliver marketing templates to US numbers. Keep SMS for US marketing.

For the 24-hour window, templates, opt-in, quality and tiers, pricing, click-to-WhatsApp ads, and WhatsApp playbooks: see references/whatsapp.md.


Compliance — Read First

Compliance is the foundation, not an afterthought. A single TCPA class-action settlement runs $5M–$40M. The basics:

US — TCPA (Telephone Consumer Protection Act)
  1. Express written consent required for marketing SMS. Implied consent doesn't count.

  2. Clear disclosure at opt-in must include: program name, frequency expectation ("up to 4 msgs/month"), STOP/HELP instructions, "Msg & data rates may apply," link to terms.

  3. Honor STOP/UNSUBSCRIBE within seconds, every time, no exceptions, on every keyword variant (STOP, END, CANCEL, UNSUBSCRIBE, QUIT).

  4. Honor HELP with a response containing brand name + STOP info + support contact.

  5. Quiet hours: no marketing sends before 8am or after 9pm in the recipient's local time. Carrier rules and state laws (e.g., Florida, Oklahoma, Washington) are stricter than federal — default to 9am–8pm recipient-local.

  6. Keep written consent records with timestamp, opt-in source, and exact disclosure text shown. Auditable.

US — A2P 10DLC Registration (required since 2022)

Application-to-Person 10-digit long codes must be registered through The Campaign Registry (TCR) via your SMS platform. Without registration:

  • Throughput is throttled (or zero)

  • Carriers filter your messages

  • You'll see "delivered" status but recipients won't get them

Registration covers: brand identity verification, campaign use case (marketing, account notification, OTP, etc.), sample messages, opt-in mechanism, opt-out language. Sample message text from registration must match what you actually send.

  • Explicit opt-in required (no pre-checked boxes)

  • Right to withdraw consent must be as easy as giving it

  • Data subject access requests apply to SMS records

  • ePrivacy Directive layered on top of GDPR

Canada — CASL
  • Express consent + sender identification + unsubscribe in every message

  • Implied consent allowed for existing business relationships within 24 months

  • Penalties up to CAD $10M per violation

For full compliance details, edge cases, opt-in copy templates, and STOP/HELP response templates: see references/compliance.md.


Phone Number Types (US)

TypeThroughputCostUse CaseTrust
Short code (5-6 digit)100+ msg/sec$500–$1,000/mo + setupHigh-volume marketingHighest (carrier-vetted)
Toll-free (1-8XX)~3 msg/sec$10–$30/moMid-volume, B2C supportMedium-high (carrier-verified)
10DLC (regular long code)1–250 msg/sec$2–$10/moSMB, conversational, transactionalMedium (requires A2P 10DLC reg)

Rule of thumb: list <10K = 10DLC. List 10K–100K = toll-free. List 100K+ = short code.


Core Principles

1. Every send has a real cost

SMS isn't free. At $0.0075–$0.04 per send + carrier fees, a 100K send costs $750–$4,000. This forces relevance — you can't "blast." Segment hard.

2. Opt-in is your most valuable asset

Opt-in rate from email → SMS is typically 5–25%. A high-quality SMS list of 10K beats a low-quality list of 100K. Optimize opt-in quality, not volume.

3. Each message must justify itself

The recipient gave you their phone number. Every send should pass: "would I be glad I got this text?" If no, don't send.

4. Brevity + clarity

160 GSM-7 characters = 1 SMS segment. 161+ chars = 2 segments (you're billed for 2). Emojis force UCS-2 encoding (70 chars per segment). Plan for segment count.

Short links are mandatory (klvy.co, txt.attn.tv, branded short domain). Track UTM params on every link.

6. Sender identity, every send

"From [Brand]:" or branded short code at the start of every message. Even on automated flows. Recipients can't see "from" address — they need it inline.


SMS Sequence Types

Welcome / Opt-In Confirmation (immediate)

Send 1: Confirmation + reward (immediate)

From Acme: Thanks for joining! Here's 10% off: ACME10. Use at checkout: acme.co/sale. Reply STOP to opt out.

Optional Send 2 (24h later): Reminder + best-seller showcase

Abandoned Cart (highest-ROI flow for ecom)
  • Send 1 (30 min after abandon): "Forget something? Your cart's still here: [short link]"

  • Send 2 (4 hours later): Soft urgency + social proof

  • Send 3 (24 hours later, optional): Discount offer (only if margin allows)

Note: Discount on first message trains customers to abandon. Reserve discount for Send 2 or 3.

Browse Abandonment
  • Send 1 (1 hour after browse): Product + "Thinking it over?" + link

Post-Purchase
  • Send 1 (immediate): Order confirmation + delivery ETA (transactional, separate consent OK)

  • Send 2 (after delivery + 2 days): "How are you liking [product]?" + review prompt + cross-sell

Win-Back (lapsed)
  • Send 1 (60–90 days after last purchase): "We miss you" + curated picks

  • Send 2 (14 days later): Discount offer

  • Send 3 (final, 14 days later): Opt-out warning + last chance

Promotional / Campaign Sends
  • Flash sales, drops, launches, BFCM

  • 1–2 sends max per campaign

  • Stack against email send schedule to avoid same-day double-tap

Transactional (separate compliance bucket)
  • Order updates, shipping, delivery, auth codes, account alerts

  • Generally OK without separate marketing consent if directly related to a transaction the user initiated

  • Still subject to A2P 10DLC registration in US

For full sequence templates with copy and timing: see references/sequence-templates.md.


SMS Copy Guidelines

Structure
  1. Sender ID ("From Acme:" or brand short code) — required

  2. Hook — first 5 words decide if they read on

  3. Value — what's in it for them, specifically

  4. CTA + short link — single action, single URL

  5. Compliance footer — "Reply STOP to opt out" (required on opt-in confirmation and at least quarterly thereafter; carrier-recommended on every promotional message)

Length
  • 160 chars (GSM-7) = 1 segment. Aim here.

  • 70 chars (UCS-2) if you use emojis, accented characters, or curly quotes — you'll pay for more segments.

  • 161–306 chars = 2 segments (concatenated SMS). Acceptable for richer messages, but you're paying double per send.

  • MMS (image + up to 1,600 chars) = 3–5× the SMS cost. Use sparingly for high-impact moments.

Voice
  • Conversational, not corporate. SMS feels personal — write like you're texting a friend.

  • No subject line, no formatting, no marketing-speak.

  • Emojis are fine in moderation (one per message, situationally).

  • ALL CAPS reads as shouting. Avoid except for explicit codes (e.g., "Use ACME10").

Personalization
  • First name token if available (boosts CTR ~20%)

  • Recent product/category browse-based

  • Location-based offers (where applicable)

  • Don't fake intimacy ("Hey friend!") — it backfires

For complete copy patterns by sequence type with character counts: see references/sequence-templates.md.


Platform Selection

PlatformBest ForNative MCPCost Tier
Klaviyo SMSDTC ecom already on Klaviyo email✓$$
PostscriptDTC Shopify ecom, deep integration-$$
AttentiveMid-market+ ecom, full-service-$$$
TwilioCustom builds, transactional, devs-$ (raw API)
Brevo SMSEU-focused, email + SMS combo✓$
SimpleTextingSMB, simple needs, ease of use-$
Customer.ioBehavior-based automation + SMS-$$

Quick picks:

  • Already on Klaviyo for email + DTC/ecom → Klaviyo SMS (no second platform to learn)

  • Shopify ecom, want deeper SMS-specific features → Postscript

  • Building custom SMS into a product → Twilio

  • B2B SaaS doing transactional/auth → Twilio or Customer.io

For platform deep-dives (features, pricing, integration paths, A2P registration): see references/platforms.md.


Measurement

Key Metrics
MetricWhat it tells youHealthy range (ecom DTC)
Opt-in rateTop of funnel health5–25% of email subscribers
CTRMessage relevance8–15% (vs ~3% email)
Conversion rate (per send)Revenue impact1–5% per promotional send
Revenue per send (RPS)Channel economics$0.20–$2.00
Opt-out rate per sendAudience fatigue<2% per send, <0.5% for promotional
Cost per sendChannel cost discipline$0.0075–$0.04
List growth rateAudience momentum5–15%/month early, 1–3% steady-state
What to track in analytics
  • UTM tag every link: utm_source=sms&utm_medium=sms&utm_campaign=[campaign-name]

  • Conversion attribution: SMS-driven sessions, last-click revenue, assisted conversions

  • LTV impact: SMS subscribers vs email-only subscribers (typically 1.5–3× LTV for SMS opt-ins)

What to A/B test
  • Send time (afternoon vs evening, local time)

  • Copy length (short SMS vs MMS with image)

  • Discount amount and trigger (immediate vs delayed)

  • Personalization tokens (with first name vs without)

  • CTA copy ("Shop now" vs "See it" vs "Last chance")

Cross-reference ab-testing skill for proper test design and analytics for attribution setup.


Output Format

When the user asks for an SMS plan, return:

  1. Compliance check: Are they registered for A2P 10DLC (if US)? Is the opt-in mechanism compliant? Flag blockers first.

  2. Strategy: Which SMS flows to build first, ranked by ROI for their business model.

  3. Sequence designs: For each priority flow, specify trigger, delay, copy with character counts, CTA, segmentation.

  4. Platform recommendation: Based on stack, list size, and complexity.

  5. Measurement plan: KPIs, benchmarks, A/B test queue.

  6. Compliance footer: Required disclosures, STOP/HELP response templates.

Keep recommendations specific. Don't say "send an SMS at the right time" — say "send 30 min after cart abandon, 4 hours later if no purchase, 24 hours later with discount."


Task-Specific Questions

  1. Are you US, EU, or both? (Changes compliance approach entirely.)

  2. Is A2P 10DLC registration complete (US)?

  3. What platform are you on or considering?

  4. Email list size and SMS opt-in rate (if any)?

  5. What sequences do you already have running?

  6. Are you DTC ecom, mobile app, B2B SaaS, services?

  7. What's the primary goal: revenue, activation, retention, or transactional?


Common Mistakes

  1. Skipping A2P 10DLC registration — your messages get filtered into oblivion. Register first, send second.

  2. Treating SMS like email — sending daily promotional blasts. Opt-out rates spike, list dies.

  3. Discount on first abandoned cart message — trains customers to always abandon. Reserve for second or third send.

  4. Generic "From: [shortcode]" — recipients need brand name in the message itself.

  5. Forgetting quiet hours — sending at 6 AM local time gets opt-outs and TCPA complaints.

  6. No STOP/HELP handling — non-negotiable. Every platform handles this; verify yours does.

  7. Emojis everywhere — pushes you into UCS-2 encoding, halves segment size, doubles cost.

  8. Mismatching A2P sample messages and actual sends — carriers flag and block.

  9. Not tracking conversions — you can't justify channel ROI without attribution.

  10. No throttling on bulk sends — burst sends trigger carrier filtering. Use platform throttling.


Tool Integrations

For implementation, see the tools registry. Key SMS tools:

ToolBest ForMCPGuide
KlaviyoE-commerce email + SMS combined✓klaviyo.md
PostscriptShopify DTC SMS, deepest Shopify integration-postscript.md
AttentiveMid-market+ DTC SMS, full-service-attentive.md
TwilioRaw API for custom builds, transactional, dev-first-twilio.md
PlivoTwilio alternative, lower per-send cost-plivo.md
AudienceTapAI-forward DTC, on-pack QR opt-in-audiencetap.md
BrevoEU email + SMS, SMB-friendly✓brevo.md
Customer.ioBehavior-based SMS automation-customer-io.md

  • emails: Sister channel — almost always run together. Email carries the long-form content; SMS carries the urgent nudges.

  • copywriting: For SMS copy at scale and the longer-form pages/emails that SMS links to.

  • popups: For phone number capture popups on-site.

  • churn-prevention: For win-back flows that combine SMS + email.

  • onboarding: For post-signup SMS milestone nudges.

  • analytics: For attribution and RPS measurement.

  • ab-testing: For SMS-specific test design.

  • lead-magnets: For incentivizing opt-in (the "10% off for joining" offer).

Files

evals/evals.json

{
  "skill_name": "sms",
  "evals": [
    {
      "id": 1,
      "prompt": "We're a Shopify DTC brand doing $5M/year in skincare. We have 80K email subscribers but no SMS program yet. Where do we start?",
      "expected_output": "Should check for product-marketing.md first. Should run Phase 0 compliance check: are they US-based, is A2P 10DLC registration started, is the opt-in mechanism planned. Should recommend Klaviyo SMS or Postscript given Shopify + DTC ecom (Klaviyo if already on Klaviyo email, Postscript for SMS-first depth). Should rank flows by ROI for skincare: (1) abandoned cart sequence first (highest-ROI flow), (2) post-purchase + replenishment (skincare has predictable cycles), (3) welcome opt-in flow with capture incentive, (4) win-back at 60-90 days. Should warn about treating SMS like email (frequency cap, relevance bar, real per-send cost ~$0.0075-$0.04). Should reference compliance.md for opt-in disclosure language and quiet hours.",
      "assertions": [
        "Checks for product-marketing.md",
        "Runs compliance/A2P 10DLC readiness check",
        "Recommends Klaviyo SMS or Postscript with rationale",
        "Prioritizes abandoned cart as highest-ROI flow",
        "Mentions replenishment for skincare specifically",
        "Warns about treating SMS like email",
        "References compliance.md or opt-in disclosure requirements",
        "Mentions per-send cost economics"
      ],
      "files": []
    },
    {
      "id": 2,
      "prompt": "Write me an abandoned cart SMS sequence. We sell custom apparel, average order $80.",
      "expected_output": "Should output a 3-message sequence following references/sequence-templates.md pattern. Should specify timing: Send 1 at 30 min after abandon (no discount, gentle reminder), Send 2 at 4 hours (soft urgency, no discount), Send 3 at 24 hours (discount allowed). Should include actual SMS copy with character counts (target 160 GSM-7 for 1 segment). Each message must start with sender ID 'From [Brand]:', have a single CTA + short link, and the first message should include 'Reply STOP to opt out' compliance footer. Should warn against discount on first send (trains customers to abandon). Should mention exclusion rules: stop sequence on purchase, opt-out, or 48 hours elapsed. Should recommend UTM tagging for attribution and cross-reference analytics skill for measurement.",
      "assertions": [
        "Outputs 3-message sequence with timing",
        "Send 1 at 30 min, Send 2 at 4 hours, Send 3 at 24 hours",
        "No discount on Send 1",
        "Each message has sender ID + single CTA + short link",
        "Character counts shown, target ~160 GSM-7",
        "Compliance footer on first send (STOP to opt out)",
        "Warns about discount on first send",
        "Mentions exclusion rules",
        "Mentions UTM tagging or attribution"
      ],
      "files": []
    },
    {
      "id": 3,
      "prompt": "Can I just send SMS without any opt-in if customers gave me their phone number at checkout?",
      "expected_output": "Should refuse and explain TCPA requires express written consent for marketing SMS. Should distinguish marketing SMS (requires express written consent) from transactional/account SMS (order updates, auth — implied consent during transaction OK if directly related). Should explain the express written consent requirements: clear disclosure adjacent to the phone field, frequency expectation, msg & data rates notice, STOP/HELP instructions, terms link, electronically captured with timestamp. Should mention penalty exposure: $500-$1,500 per message, class actions reach 7-8 figures. Should recommend implementing a compliant opt-in flow: checkbox + disclosure text, double opt-in optional but cleaner. Should reference compliance.md for the full disclosure template. Should warn that 'customers gave their number at checkout' is NOT sufficient for marketing SMS — it's only sufficient for the specific transaction's communications.",
      "assertions": [
        "Refuses the no-opt-in approach",
        "Distinguishes marketing SMS from transactional SMS",
        "Lists express written consent requirements",
        "Mentions TCPA penalty exposure ($500-$1,500 per message)",
        "Mentions class action risk",
        "Recommends compliant opt-in flow",
        "References compliance.md",
        "Clarifies checkout phone capture is not marketing consent"
      ],
      "files": []
    },
    {
      "id": 4,
      "prompt": "Our SMS list is 50K subscribers. We send 3 promotional messages per week. Opt-out rate has crept up to 4% per send. What's wrong?",
      "expected_output": "Should diagnose this as audience fatigue from over-sending. Should reference healthy benchmarks: opt-out rate should be <2% per send and <0.5% for promotional sends — 4% is significantly elevated. Should review send frequency: 3 promotional sends/week is on the high side; recommend reducing to 1-2/week, especially for newer subscribers. Should audit relevance: are sends segmented or going to entire list? Generic blasts to a 50K list will burn out the inactive 30K. Should recommend segmenting by engagement (recently engaged vs cold), purchase recency, and opt-in source. Should suggest reactivating cold subscribers with a re-engagement flow before sending more promos. Should warn that 4% opt-out per send means the list is being destroyed at the rate of ~2K/week. Should cross-reference analytics for proper measurement and the principle 'every send must justify itself.'",
      "assertions": [
        "Diagnoses as over-sending / audience fatigue",
        "Cites healthy benchmark (<2% opt-out per send, <0.5% promotional)",
        "Recommends reducing send frequency",
        "Recommends segmentation by engagement",
        "Suggests reactivation flow for cold subscribers",
        "Calculates list erosion impact",
        "Mentions 'every send must justify itself' principle"
      ],
      "files": []
    },
    {
      "id": 5,
      "prompt": "We just submitted our A2P 10DLC registration and our sends are working. Can we start scaling to 100K+ messages per day?",
      "expected_output": "Should ask about phone number type currently in use: 10DLC, toll-free, or short code. Should explain throughput limits: 10DLC standard brand ~4-10 msg/sec, verified brand ~75-100+ msg/sec, toll-free ~3 msg/sec, short code 100+ msg/sec. Should calculate: 100K msgs at 10 msg/sec = ~2.8 hours of continuous send time, may run into quiet hour cutoff. Should recommend short code lease for 100K+/day sustained volume. Should warn about carrier filtering on burst sends — use platform throttling. Should mention that sample message text from A2P registration must match actual sends or carriers will flag. Should recommend monitoring trust score and deliverability dashboards. Should reference platforms.md for short code provisioning details.",
      "assertions": [
        "Asks about phone number type (10DLC vs toll-free vs short code)",
        "Explains throughput limits with specific msg/sec numbers",
        "Calculates time-to-send for 100K volume",
        "Mentions quiet hour considerations",
        "Recommends short code for high sustained volume",
        "Warns about carrier filtering / throttling",
        "Mentions A2P sample text alignment requirement",
        "References platforms.md or trust score monitoring"
      ],
      "files": []
    },
    {
      "id": 6,
      "prompt": "Should we put emojis in our SMS messages? Other brands seem to use them a lot.",
      "expected_output": "Should explain the cost trade-off: emojis force UCS-2 encoding, which cuts segment size from 160 GSM-7 chars to 70 chars. A 100-char message with one emoji becomes 2 segments billed instead of 1 — effectively doubling the per-send cost. Should advise: 1 emoji per message max, situationally relevant, only when the emoji genuinely earns its segment cost (high-energy promotional, brand-personality fit, etc.). Should warn against emoji clutter — it signals 'mass send' rather than personal. Should note that some accented characters (curly quotes, em dashes) also force UCS-2 — copy-pasting from Word/Google Docs is a common silent cause of doubled costs. Should recommend testing in the platform's preview to verify segment count before scheduling. Should remind that segment count matters at scale: 100K sends at 2 segments instead of 1 = $750-$4,000 in extra cost per campaign.",
      "assertions": [
        "Explains UCS-2 encoding cost",
        "Specifies 160 GSM-7 vs 70 UCS-2 segment sizes",
        "Recommends max 1 emoji per message",
        "Warns about doubled per-send cost",
        "Mentions accented characters / curly quotes also trigger UCS-2",
        "Recommends previewing segment count",
        "Calculates cost impact at scale"
      ],
      "files": []
    },
    {
      "id": 7,
      "prompt": "We sell fashion accessories in Brazil and Mexico and get about 1,500 abandoned carts a week. Most customers use WhatsApp, not SMS. Can we send cart reminders on WhatsApp an hour after they leave, and what will it cost?",
      "expected_output": "Should check for product-marketing.md first. Should confirm WhatsApp fits better than SMS for Brazil and Mexico and reference references/whatsapp.md. Should explain that a reminder 1 hour after abandonment falls outside the 24-hour customer service window, so it must be a Meta-approved template, and that cart reminders are classified as marketing templates (submitting as utility gets recategorized). Should require WhatsApp-specific opt-in that names the business, captured at checkout or in chat, plus an opt-out button or STOP footer on every marketing template. Should explain current per-message pricing (since July 1, 2025): every delivered marketing template is charged at a per-country rate, with no free window unless the customer recently messaged for these reminders, and recommend modeling cost per recovered order using current Meta or BSP rate cards rather than old per-conversation pricing. Should warn that blocks and reports lower the quality rating, can flag the number and cut the messaging limit, and recommend warming up a new number, business verification, and limiting to 1-2 cart touches with exit on purchase or opt-out. Should design the template with name, product, and checkout URL button, holding any discount for a later touch.",
      "assertions": [
        "Checks for product-marketing.md",
        "Checks whether a 24-hour service window (or a click-to-WhatsApp free window) is open from the customer's messaging history, and uses an approved template when it isn't",
        "Classifies cart reminders as marketing templates",
        "Requires opt-in that names the business (and ideally WhatsApp), compliant with local law",
        "Includes an opt-out button or STOP footer",
        "Explains per-message pricing with marketing templates charged per delivery",
        "Does not quote per-conversation pricing as current",
        "Warns about quality rating, flagging, and messaging limit risk from blocks",
        "Recommends number warm-up or business verification",
        "References references/whatsapp.md"
      ],
      "files": []
    }
  ]
}

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Corey Haines
Publisher
Corey Haines (Community)
Source
coreyhaines31/marketingskills · skills/sms · commit 96798cf
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Corey Haines.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download sms.zip