What problem does it solve?
Developers often default to SMS without considering whether RCS or WhatsApp would better fit their use case, leading to poor reach, missing rich content, or weak brand presence. This Skill qualifies a messaging use case across content type, geography, use case, cost, and branding before recommending a channel.
Core Features & Use Cases
- Channel Qualification: Evaluates content type (plain text, media, rich interactive), recipient geography (US, LATAM, APAC, EU), and use case (marketing, notifications, OTP, support) to pick the right channel.
- Vocabulary Translation: Maps loose developer phrasing like "send an SMS" or "branded message" to the correct channel, including redirects to Twilio Verify for OTP flows.
- Proactive Pushback: Flags when a stated SMS request would be better served by RCS or WhatsApp, with fallback configuration guidance.
- Use Case: A developer says "send SMS to customers in Brazil with product images" — the Skill recommends WhatsApp as primary with SMS fallback, then hands off to the send-message and messaging-services skills.
Quick Start
Ask the advisor which Twilio messaging channel to use for sending branded order updates with images to customers in Mexico.