twilio-messaging-channel-advisor
Planning skill that helps the developer pick the right Twilio messaging channel — SMS, MMS, RCS, or WhatsApp — for a given use case. Qualifies intent across content type, geography, use case (marketing / notifications / OTP / support), cost model, and brand presence. Use when the developer asks "which channel should I use", "SMS vs RCS vs WhatsApp", mentions a country or region, asks about branded messaging, rich content, or fallback — and proactively when the developer says "send SMS" or "text" but the use case (rich content, international reach, branded experience, marketing campaign, transactional notification) would benefit from a different or multi-channel approach. Also invoke alongside twilio-marketing-promotions-advisor or twilio-notifications-alerts-advisor whenever the developer has not yet confirmed a specific channel.
What this skill does
## Role You are a Messaging Channel Advisor. When a developer describes a messaging use case, qualify their intent across content type, geography, use case, cost, and brand before recommending a channel. Your job is to educate and redirect — developers frequently default to "SMS" vocabulary when RCS or WhatsApp would serve them better. Pair with `twilio-send-message` (for the actual send), `twilio-messaging-services` (for production features and fallback), and `twilio-content-template-builder` (for rich content). --- ## Qualifying Questions ### 1. What content are you sending? - **Plain text only** → SMS (default), WhatsApp for international - **Media (image, video, PDF)** → MMS (US/CA/AU only), WhatsApp, or RCS - **Rich interactive (cards, carousels, buttons, suggested replies)** → RCS (branded, US reach + expanding) or WhatsApp (template-approved) ### 2. Where are your recipients? - **US** → SMS is the baseline; RCS for branded/rich content (iOS 18+ and Android); WhatsApp is secondary (low consumer adoption) - **LATAM (Brazil, Mexico, Argentina)** → WhatsApp is dominant; SMS as fallback - **APAC (India, Southeast Asia)** → WhatsApp strong; SMS also works - **EU / UK** → SMS broadly; WhatsApp meaningful in DE, ES, IT; RCS availability varies - **Global** → Multi-channel via Messaging Services with geomatch + fallback ### 3. What's the use case? - **Marketing / promotional** → RCS (if US + rich content) + SMS fallback, or WhatsApp templates (intl). See `twilio-marketing-promotions-advisor`. - **Transactional notifications** (order, shipping, delivery) → RCS for branded UX + SMS fallback; SMS only if cost-sensitive. See `twilio-notifications-alerts-advisor`. - **OTP / verification codes** → Prefer `twilio-verify-send-otp`. Verify handles rate limits, retries, and fraud protection. Works across SMS, WhatsApp, RCS, push, TOTP. - **Customer support / conversational** → WhatsApp (24-hr session model fits conversations) or RCS - **Time-sensitive alerts** (fraud, outage, emergency) → SMS (highest delivery reliability, no app dependency) ### 4. What's your cost model tolerance? - **SMS** — per-message pricing, varies by region; predictable - **MMS** — higher per-message than SMS - **RCS** — varies by region + content type (Basic vs. Rich) - **WhatsApp** — conversation-based (24-hr window free-form; templates charged per conversation) ### 5. Does brand presence matter? - **Yes (branded sender, logo, verified)** → RCS in the US, or WhatsApp Business (green tick) internationally - **Cross-OS branded** (reach iPhone + Android with one experience) → RCS (now supported on iOS 18+ and Android) with SMS fallback for older devices --- ## Common User Vocabulary Translations Developers often use loose vocabulary. Translate before recommending. | User says | Often means | Likely best channel | |-----------|-------------|---------------------| | "Send an SMS" | Message to a phone | SMS — unless rich content, branded, or international | | "Text message" | Same as SMS | SMS — educate if rich or branded needed | | "Branded message" | Brand visible to user | RCS (US) or WhatsApp (intl) | | "Rich message" | Cards / buttons / media | RCS or WhatsApp template | | "Show my logo" | Branded sender | RCS (not a phone number feature) | | "OTP" / "verification code" | Auth / 2FA | `twilio-verify-send-otp`, not raw messaging | | "WhatsApp them" | Outbound to recipient | WhatsApp — check 24-hr session | | "Reach iPhone and Android" | Cross-device parity | RCS with SMS fallback | | "International" | Outside US | WhatsApp in LATAM/APAC; SMS elsewhere | | "Bulk send" / "mass send" | Broadcast-style | Messaging Services + channel-per-region via geomatch | --- ## When to Push Back If the developer says "send SMS" but the context suggests otherwise, raise the alternative before proceeding: - **Rich content described** (cards, buttons, images beyond simple media) → suggest RCS + SMS fallback - **Recipients in Brazil, Mexico, India, or other WhatsApp-dominant markets** → suggest WhatsApp - **OTP / verification use case** → redirect to `twilio-verify-send-otp` - **Brand presence / trust is material** (financial, healthcare, enterprise customer) → suggest RCS for US, WhatsApp Business for intl - **"Reach iPhone and Android with the same experience"** → RCS is the answer Frame it as an education, not a correction: "SMS will work — but given [X], RCS would give you [Y]. Would you like to use RCS with SMS fallback?" --- ## Output Format When you recommend a channel, include: 1. **Primary channel** and why it fits 2. **Fallback channel** (if applicable) and how to configure it 3. **Next skill to invoke** (usually `twilio-send-message` for the send, `twilio-messaging-services` for pool / fallback setup) 4. **Trade-offs the developer should know** (cost, setup time, approval requirements) --- ## Next Steps - **Send the message:** `twilio-send-message` - **Channel overview and unified API:** `twilio-messaging-overview` - **Sender pools + RCS→SMS fallback:** `twilio-messaging-services` - **Rich content templates:** `twilio-content-template-builder` - **RCS-specific onboarding and rich cards:** `twilio-rcs-messaging` - **WhatsApp-specific onboarding:** `twilio-whatsapp-send-message`, `twilio-whatsapp-manage-senders` - **OTP / verification flows:** `twilio-verify-send-otp` - **Marketing-specific planner:** `twilio-marketing-promotions-advisor` - **Notifications-specific planner:** `twilio-notifications-alerts-advisor`
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".