Twilio Messaging Channel Advisor
- 110 installs
- 26 repo stars
- Updated July 29, 2026
- twilio/ai
Which Twilio messaging channel (SMS, MMS, RCS, WhatsApp) best fits the developer's use case, recipients, content type, and business constraints?
About
A planning skill that qualifies messaging intent across content type, geography, use case, cost model, and brand presence to recommend the right Twilio channel. Educates developers who default to SMS vocabulary when RCS or WhatsApp would better serve their needs. Evaluates plain text vs. rich media, recipient location (US, LATAM, APAC, EU), use case category (marketing, transactional, OTP, support), cost tolerance, and brand visibility requirements. Pairs with twilio-send-message, twilio-messaging-services, and twilio-content-template-builder for execution and fallback configuration.
- Qualifies messaging intent across 5 dimensions: content, geography, use case, cost, brand
- Translates loose developer vocabulary (text, SMS, branded message) to channel recommendations
- Provides geomatch logic: WhatsApp for LATAM/APAC, RCS for US branded, SMS as universal fallback
- Educates when to redirect to twilio-verify-send-otp for OTP/verification flows
- Recommends multi-channel with fallback strategy via Messaging Services for production reliability
Twilio Messaging Channel Advisor by the numbers
- 110 all-time installs (skills.sh)
- +10 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #4,062 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/twilio/ai --skill twilio-messaging-channel-advisorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 110 |
|---|---|
| repo stars | ★ 26 |
| Last updated | July 29, 2026 |
| Repository | twilio/ai ↗ |
What it does
Select optimal Twilio messaging channel (SMS, MMS, RCS, WhatsApp) based on content type, geography, use case, cost, and brand requirements.
Who is it for?
Developers planning messaging campaigns, notifications, OTP flows, or customer support integrations who need guidance on channel selection and multi-region strategy.
Skip if: Developers already committed to a specific channel; those needing hands-on send implementation (use twilio-send-message instead); solo or indie builders.
When should I use this skill?
Developer asks which channel to use, compares channels (SMS vs RCS vs WhatsApp), mentions geography or branded messaging, or describes rich content or fallback needs. Proactively invoke when developer says send SMS but u
What you get
Developer confidently selects the right channel(s) with fallback strategy, understands trade-offs, and invokes the next skill (send-message, messaging-services, or verify-send-otp) with correct parameters.
Files
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
interface:
display_name: "Messaging Channel Advisor"
short_description: "Planning skill for picking the right Twilio messaging channel — SMS, MMS, RCS, or WhatsApp — based on use case, geography, cost, and brand requirements."
icon_small: "./assets/icon-small.png"
icon_large: "./assets/icon-large.png"
brand_color: "#EF223A"
default_prompt: "Which Twilio messaging channel should I use for my use case?"
policy:
allow_implicit_invocation: true
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10