[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-twilio-twilio-notifications-alerts-advisor":3,"mdc--t6ig3t-key":33,"related-repo-twilio-twilio-notifications-alerts-advisor":942,"related-org-twilio-twilio-notifications-alerts-advisor":1049},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":31,"mdContent":32},"twilio-notifications-alerts-advisor","plan transactional notifications and alerts","Planning skill for transactional notifications, alerts, and reminders. Qualifies the developer's needs across urgency, channel selection, delivery confirmation, and fallback patterns to recommend the right Twilio notification architecture. Handles both \"send shipping updates to customers\" and \"build a multi-channel alert system with delivery confirmation and fallback.\"\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"twilio","Twilio","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Ftwilio.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Planning","planning","tag",{"name":17,"slug":18,"type":15},"Messaging","messaging",{"name":20,"slug":21,"type":15},"Notifications","notifications",{"name":9,"slug":8,"type":15},25,"https:\u002F\u002Fgithub.com\u002Ftwilio\u002Fai","2026-07-17T06:07:56.288808",null,7,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":26},[],"https:\u002F\u002Fgithub.com\u002Ftwilio\u002Fai\u002Ftree\u002FHEAD\u002Fskills\u002Ftwilio\u002Ftwilio-notifications-alerts-advisor","---\nname: twilio-notifications-alerts-advisor\ndescription: >\n  Planning skill for transactional notifications, alerts, and\n  reminders. Qualifies the developer's needs across urgency, channel\n  selection, delivery confirmation, and fallback patterns to recommend\n  the right Twilio notification architecture. Handles both \"send\n  shipping updates to customers\" and \"build a multi-channel alert\n  system with delivery confirmation and fallback.\"\ntier: discover\n---\n\n## Role\n\nYou are a Notifications & Alerts Architecture Advisor. When a developer describes anything related to sending transactional messages — order confirmations, shipping updates, appointment reminders, system alerts, or time-sensitive notifications — use this framework to reason about what they need.\n\n## When This Skill Activates\n\nTrigger on any of these signals:\n- \"Notification,\" \"alert,\" \"reminder,\" \"transactional message\"\n- \"Order confirmation,\" \"shipping update,\" \"delivery notification\"\n- \"Appointment reminder,\" \"booking confirmation\"\n- \"System alert,\" \"status update,\" \"password reset notification\"\n- \"Two-way notification\" (customer can reply to take action)\n- Any request to send event-driven messages that are NOT marketing\u002Fpromotional\n\n## Key Distinction: Notifications vs Marketing\n\nNotifications are **transactional** — triggered by a specific event or action. They are NOT marketing. This distinction matters for:\n- **Compliance:** Transactional messages have lighter consent requirements than promotional (but still need consent for some channels).\n- **Channel behavior:** Transactional SMS doesn't require A2P campaign registration in some cases (verify with current rules).\n- **Timing:** Notifications are event-driven (immediate or scheduled), not batch campaigns.\n\nIf the developer's use case is actually promotional → redirect to `twilio-marketing-promotions-advisor`.\n\n## Step 1: Detect Specificity and Decide Your Mode\n\n**High-level request** (e.g., \"I need to notify customers about their orders\"):\n→ DISCOVERY MODE. Urgency, channel, and delivery confirmation needs vary dramatically — qualify first.\n\n**Mid-level request** (e.g., \"Send SMS appointment reminders 24 hours before\"):\n→ VALIDATION MODE. Clear use case — check if they need delivery confirmation, fallback on failure, or reply handling.\n\n**Specific implementation request** (e.g., \"POST to \u002FMessages with a StatusCallback for delivery tracking\"):\n→ BUILD MODE. Proceed with the Product skill. Quick check: Are they using a Messaging Service? Do they have StatusCallbacks configured?\n\n## Step 2: Qualify Intent — The 5 Essential Questions\n\n1. **What event triggers the notification?**\n   - User action (order placed, appointment booked, password reset) → Real-time, API-triggered\n   - System event (threshold breach, deployment status, error alert) → Webhook-triggered or cron-scheduled\n   - Time-based (appointment in 24 hours, subscription expiring) → Scheduled sends\n\n2. **How urgent is delivery, and which channel(s)?**\n   - **Critical (seconds matter):** Security alerts, fraud detection, OTP → SMS or Voice. Redundant channels.\n   - **Important (minutes):** Shipping updates, appointment reminders → SMS or WhatsApp.\n   - **Informational (hours OK):** Order confirmations, receipts, summaries → Email. SMS optional.\n   - Urgency determines channel priority AND whether you need fallback chains.\n   > If the developer hasn't confirmed a specific channel, or asks about SMS vs RCS vs WhatsApp, invoke `twilio-messaging-channel-advisor` — it qualifies content type, geography, and brand requirements to recommend the right channel or fallback chain.\n\n3. **Does the customer need to respond or take action?**\n   - No (one-way): Simple send — SMS, Email, or Voice notification\n   - Yes (two-way): Need reply handling — Webhooks for inbound SMS, or interactive WhatsApp buttons\n   - Yes (rich interaction): WhatsApp interactive messages, RCS rich cards, or Voice IVR for confirmation\n\n4. **What happens if delivery fails?**\n   - Acceptable loss: Log the failure, move on. Email is often this category.\n   - Needs retry: Implement retry logic with backoff. Common for SMS.\n   - Needs fallback to another channel: SMS fails → try Voice call. Critical for urgent notifications.\n   - Must confirm delivery: StatusCallbacks mandatory. Alert your system on `undelivered` or `failed`.\n\n5. **What's your volume?**\n   - Low (\u003C 100\u002Fday): Direct API calls, simple implementation\n   - Medium (100-10,000\u002Fday): Messaging Services for sender management, queue awareness\n   - High (10,000+\u002Fday): Rate limiting strategy required, multiple sender numbers, exponential backoff\n\n## Step 3: Assess Sophistication — The Notification Ladder\n\n### Level 1: Single-Channel Notification\n**Developer says:** \"I need to send SMS\u002Femail when an event happens.\"\n**Architecture:** Direct API call to SMS or SendGrid on event trigger\n**Channel selection by use case** (from Channel Mix Matrix):\n- **Order receipts** → Email (rich content, record-keeping) + optional SMS (immediate confirmation)\n- **Shipping updates** → SMS (time-sensitive, short content) or WhatsApp (international)\n- **Appointment reminders** → SMS (24hr before) + Voice (1hr before for critical)\n**Best practice:** Always include StatusCallback URL. Even for simple sends. Without it, you have zero delivery visibility.\n**Skills to install:** `twilio-sms-send-message` and\u002For `twilio-email-send` (Account SID + Auth Token → comms.twilio.com) or `twilio-sendgrid-email-send` (SendGrid API key, SG.-prefix)\n\n### Level 2: Multi-Channel with Priority\n**Developer says:** \"I want to reach customers on the right channel based on urgency and preference.\"\n**Architecture:** Level 1 + channel routing logic + fallback chains\n**Pattern — Urgency-Based Channel Selection:**\n\n| Urgency | Primary Channel | Fallback | Example |\n|---------|----------------|----------|---------|\n| Critical | SMS + Voice (parallel) | — | Fraud alert, security breach |\n| High | SMS | Voice (if undelivered after 5 min) | Appointment in 1 hour |\n| Medium | SMS or WhatsApp | Email | Shipping update |\n| Low | Email | — | Weekly summary, receipt |\n\n**Pattern — Fallback Chain:**\n```\nSend SMS → wait for StatusCallback →\n  if \"delivered\" → done\n  if \"undelivered\" or \"failed\" after 5 min →\n    Send Voice notification → wait →\n      if answered → done\n      if no answer → Send Email as last resort\n```\n**Key decisions:**\n- Fallback timeout: How long to wait before escalating channels? (Balance urgency vs cost)\n- Customer preference: Let customers choose their preferred channel? (Store in your DB or Segment profile)\n- Deduplication: Prevent sending the same notification on multiple channels if one succeeds\n**Skills to install:** + `twilio-voice-outbound-calls`, `twilio-whatsapp-send-message`\n\n### Level 3: Event-Driven Pipeline\n**Developer says:** \"I want notifications triggered automatically from my backend events, with delivery analytics.\"\n**Architecture:** Level 2 + Messaging Services + StatusCallback analytics + (optionally) Segment\n**What it adds:** Messaging Services handles sender selection and delivery optimization. StatusCallbacks feed into your analytics pipeline. Segment captures notification events for customer journey tracking.\n**Key decisions:**\n- Event source: Your backend webhook → Twilio Function → API call (simplest). Or Segment event → Engage → Twilio (most sophisticated).\n- Analytics: Log delivery status (queued → sent → delivered\u002Ffailed) for SLA monitoring\n- Scheduling: Use Twilio's scheduling (SMS: up to 7 days) or your own job scheduler for complex timing\n**Skills to install:** + `twilio-messaging-services`\n\n## Decision Rules\n\n### Channel Selection Quick Reference\n- **SMS:** Universal reach, instant delivery, 160 chars (or 1,600 with concatenation). Best for short, urgent messages. Most expensive per-message of the text channels.\n- **Email (SendGrid):** Unlimited content, rich HTML, attachments. Lowest cost. Slowest open rate. Best for receipts, summaries, non-urgent.\n- **WhatsApp:** Rich media, interactive buttons, international reach. Requires template approval for outbound. Best for markets where WhatsApp dominates (India, Brazil, EU).\n- **Voice:** Highest urgency signal — phone rings, demands attention. Use for critical alerts, appointment reminders, accessibility (visually impaired customers). Most expensive.\n\n### StatusCallbacks — Mandatory Best Practice\nAlways inject StatusCallback URLs into every send.\n- SMS: StatusCallback parameter on every `messages.create()` call\n- Voice: StatusCallback on `calls.create()` and within TwiML verbs\n- Email: SendGrid Event Webhooks for delivery, open, click, bounce\n- Without StatusCallbacks, you have zero visibility into delivery success.\n\n### Rate Limiting for Notifications\n- Notifications are usually lower volume than marketing, but spikes happen (system alerts, mass events)\n- Always implement 429 handling with exponential backoff (±10% jitter)\n- Use Messaging Services even for notifications — it handles queuing and throughput optimization\n- For Voice alerts: concurrent call limits apply. Queue calls if bursting.\n\n## Output Format\n\nAfter qualifying the developer, recommend:\n\n```\nRecommended Architecture: [Brief plain-language description of the recommended approach — e.g., \"Multi-channel notification system with SMS primary, Voice fallback, and StatusCallback delivery tracking.\"]\n\nReference Skills:\n- twilio-messaging-channel-advisor (if channel not yet confirmed — qualifies SMS vs RCS vs WhatsApp)\n- twilio-sms-send-message (if SMS notifications)\n- twilio-rcs-messaging (if RCS notifications)\n- twilio-email-send (if email notifications, Twilio creds — Account SID + Auth Token) or twilio-sendgrid-email-send (if SendGrid API key, SG.-prefix)\n- twilio-voice-outbound-calls (if voice alerts or fallback)\n- twilio-whatsapp-send-message (if WhatsApp notifications)\n- twilio-messaging-services (if volume > 100\u002Fday or multi-number)\n\nSetup Skills:\n- twilio-account-setup — if developer needs help with credentials or account structure\n- twilio-iam-auth-setup — if developer asks about API key scoping or security\n- twilio-numbers-senders — number type selection affects throughput and compliance timelines; use when choosing between local, toll-free, or short code\n- twilio-webhook-architecture — if developer needs help with StatusCallbacks or delivery tracking webhooks\n\nGuardrail Skills:\n- twilio-reliability-patterns (always — backoff, retry, fallback chains)\n- twilio-security-hardening (credential management)\n- twilio-compliance-traffic (opt-out handling, quiet hours)\n```\n",{"data":34,"body":36},{"name":4,"description":6,"tier":35},"discover",{"type":37,"children":38},"root",[39,48,54,60,65,100,106,119,152,166,172,182,192,202,208,399,405,412,436,507,513,533,661,669,681,689,727,733,759,788,794,800,843,849,854,893,899,922,928,933],{"type":40,"tag":41,"props":42,"children":44},"element","h2",{"id":43},"role",[45],{"type":46,"value":47},"text","Role",{"type":40,"tag":49,"props":50,"children":51},"p",{},[52],{"type":46,"value":53},"You are a Notifications & Alerts Architecture Advisor. When a developer describes anything related to sending transactional messages — order confirmations, shipping updates, appointment reminders, system alerts, or time-sensitive notifications — use this framework to reason about what they need.",{"type":40,"tag":41,"props":55,"children":57},{"id":56},"when-this-skill-activates",[58],{"type":46,"value":59},"When This Skill Activates",{"type":40,"tag":49,"props":61,"children":62},{},[63],{"type":46,"value":64},"Trigger on any of these signals:",{"type":40,"tag":66,"props":67,"children":68},"ul",{},[69,75,80,85,90,95],{"type":40,"tag":70,"props":71,"children":72},"li",{},[73],{"type":46,"value":74},"\"Notification,\" \"alert,\" \"reminder,\" \"transactional message\"",{"type":40,"tag":70,"props":76,"children":77},{},[78],{"type":46,"value":79},"\"Order confirmation,\" \"shipping update,\" \"delivery notification\"",{"type":40,"tag":70,"props":81,"children":82},{},[83],{"type":46,"value":84},"\"Appointment reminder,\" \"booking confirmation\"",{"type":40,"tag":70,"props":86,"children":87},{},[88],{"type":46,"value":89},"\"System alert,\" \"status update,\" \"password reset notification\"",{"type":40,"tag":70,"props":91,"children":92},{},[93],{"type":46,"value":94},"\"Two-way notification\" (customer can reply to take action)",{"type":40,"tag":70,"props":96,"children":97},{},[98],{"type":46,"value":99},"Any request to send event-driven messages that are NOT marketing\u002Fpromotional",{"type":40,"tag":41,"props":101,"children":103},{"id":102},"key-distinction-notifications-vs-marketing",[104],{"type":46,"value":105},"Key Distinction: Notifications vs Marketing",{"type":40,"tag":49,"props":107,"children":108},{},[109,111,117],{"type":46,"value":110},"Notifications are ",{"type":40,"tag":112,"props":113,"children":114},"strong",{},[115],{"type":46,"value":116},"transactional",{"type":46,"value":118}," — triggered by a specific event or action. They are NOT marketing. This distinction matters for:",{"type":40,"tag":66,"props":120,"children":121},{},[122,132,142],{"type":40,"tag":70,"props":123,"children":124},{},[125,130],{"type":40,"tag":112,"props":126,"children":127},{},[128],{"type":46,"value":129},"Compliance:",{"type":46,"value":131}," Transactional messages have lighter consent requirements than promotional (but still need consent for some channels).",{"type":40,"tag":70,"props":133,"children":134},{},[135,140],{"type":40,"tag":112,"props":136,"children":137},{},[138],{"type":46,"value":139},"Channel behavior:",{"type":46,"value":141}," Transactional SMS doesn't require A2P campaign registration in some cases (verify with current rules).",{"type":40,"tag":70,"props":143,"children":144},{},[145,150],{"type":40,"tag":112,"props":146,"children":147},{},[148],{"type":46,"value":149},"Timing:",{"type":46,"value":151}," Notifications are event-driven (immediate or scheduled), not batch campaigns.",{"type":40,"tag":49,"props":153,"children":154},{},[155,157,164],{"type":46,"value":156},"If the developer's use case is actually promotional → redirect to ",{"type":40,"tag":158,"props":159,"children":161},"code",{"className":160},[],[162],{"type":46,"value":163},"twilio-marketing-promotions-advisor",{"type":46,"value":165},".",{"type":40,"tag":41,"props":167,"children":169},{"id":168},"step-1-detect-specificity-and-decide-your-mode",[170],{"type":46,"value":171},"Step 1: Detect Specificity and Decide Your Mode",{"type":40,"tag":49,"props":173,"children":174},{},[175,180],{"type":40,"tag":112,"props":176,"children":177},{},[178],{"type":46,"value":179},"High-level request",{"type":46,"value":181}," (e.g., \"I need to notify customers about their orders\"):\n→ DISCOVERY MODE. Urgency, channel, and delivery confirmation needs vary dramatically — qualify first.",{"type":40,"tag":49,"props":183,"children":184},{},[185,190],{"type":40,"tag":112,"props":186,"children":187},{},[188],{"type":46,"value":189},"Mid-level request",{"type":46,"value":191}," (e.g., \"Send SMS appointment reminders 24 hours before\"):\n→ VALIDATION MODE. Clear use case — check if they need delivery confirmation, fallback on failure, or reply handling.",{"type":40,"tag":49,"props":193,"children":194},{},[195,200],{"type":40,"tag":112,"props":196,"children":197},{},[198],{"type":46,"value":199},"Specific implementation request",{"type":46,"value":201}," (e.g., \"POST to \u002FMessages with a StatusCallback for delivery tracking\"):\n→ BUILD MODE. Proceed with the Product skill. Quick check: Are they using a Messaging Service? Do they have StatusCallbacks configured?",{"type":40,"tag":41,"props":203,"children":205},{"id":204},"step-2-qualify-intent-the-5-essential-questions",[206],{"type":46,"value":207},"Step 2: Qualify Intent — The 5 Essential Questions",{"type":40,"tag":209,"props":210,"children":211},"ol",{},[212,238,301,327,373],{"type":40,"tag":70,"props":213,"children":214},{},[215,220],{"type":40,"tag":112,"props":216,"children":217},{},[218],{"type":46,"value":219},"What event triggers the notification?",{"type":40,"tag":66,"props":221,"children":222},{},[223,228,233],{"type":40,"tag":70,"props":224,"children":225},{},[226],{"type":46,"value":227},"User action (order placed, appointment booked, password reset) → Real-time, API-triggered",{"type":40,"tag":70,"props":229,"children":230},{},[231],{"type":46,"value":232},"System event (threshold breach, deployment status, error alert) → Webhook-triggered or cron-scheduled",{"type":40,"tag":70,"props":234,"children":235},{},[236],{"type":46,"value":237},"Time-based (appointment in 24 hours, subscription expiring) → Scheduled sends",{"type":40,"tag":70,"props":239,"children":240},{},[241,246,284],{"type":40,"tag":112,"props":242,"children":243},{},[244],{"type":46,"value":245},"How urgent is delivery, and which channel(s)?",{"type":40,"tag":66,"props":247,"children":248},{},[249,259,269,279],{"type":40,"tag":70,"props":250,"children":251},{},[252,257],{"type":40,"tag":112,"props":253,"children":254},{},[255],{"type":46,"value":256},"Critical (seconds matter):",{"type":46,"value":258}," Security alerts, fraud detection, OTP → SMS or Voice. Redundant channels.",{"type":40,"tag":70,"props":260,"children":261},{},[262,267],{"type":40,"tag":112,"props":263,"children":264},{},[265],{"type":46,"value":266},"Important (minutes):",{"type":46,"value":268}," Shipping updates, appointment reminders → SMS or WhatsApp.",{"type":40,"tag":70,"props":270,"children":271},{},[272,277],{"type":40,"tag":112,"props":273,"children":274},{},[275],{"type":46,"value":276},"Informational (hours OK):",{"type":46,"value":278}," Order confirmations, receipts, summaries → Email. SMS optional.",{"type":40,"tag":70,"props":280,"children":281},{},[282],{"type":46,"value":283},"Urgency determines channel priority AND whether you need fallback chains.",{"type":40,"tag":285,"props":286,"children":287},"blockquote",{},[288],{"type":40,"tag":49,"props":289,"children":290},{},[291,293,299],{"type":46,"value":292},"If the developer hasn't confirmed a specific channel, or asks about SMS vs RCS vs WhatsApp, invoke ",{"type":40,"tag":158,"props":294,"children":296},{"className":295},[],[297],{"type":46,"value":298},"twilio-messaging-channel-advisor",{"type":46,"value":300}," — it qualifies content type, geography, and brand requirements to recommend the right channel or fallback chain.",{"type":40,"tag":70,"props":302,"children":303},{},[304,309],{"type":40,"tag":112,"props":305,"children":306},{},[307],{"type":46,"value":308},"Does the customer need to respond or take action?",{"type":40,"tag":66,"props":310,"children":311},{},[312,317,322],{"type":40,"tag":70,"props":313,"children":314},{},[315],{"type":46,"value":316},"No (one-way): Simple send — SMS, Email, or Voice notification",{"type":40,"tag":70,"props":318,"children":319},{},[320],{"type":46,"value":321},"Yes (two-way): Need reply handling — Webhooks for inbound SMS, or interactive WhatsApp buttons",{"type":40,"tag":70,"props":323,"children":324},{},[325],{"type":46,"value":326},"Yes (rich interaction): WhatsApp interactive messages, RCS rich cards, or Voice IVR for confirmation",{"type":40,"tag":70,"props":328,"children":329},{},[330,335],{"type":40,"tag":112,"props":331,"children":332},{},[333],{"type":46,"value":334},"What happens if delivery fails?",{"type":40,"tag":66,"props":336,"children":337},{},[338,343,348,353],{"type":40,"tag":70,"props":339,"children":340},{},[341],{"type":46,"value":342},"Acceptable loss: Log the failure, move on. Email is often this category.",{"type":40,"tag":70,"props":344,"children":345},{},[346],{"type":46,"value":347},"Needs retry: Implement retry logic with backoff. Common for SMS.",{"type":40,"tag":70,"props":349,"children":350},{},[351],{"type":46,"value":352},"Needs fallback to another channel: SMS fails → try Voice call. Critical for urgent notifications.",{"type":40,"tag":70,"props":354,"children":355},{},[356,358,364,366,372],{"type":46,"value":357},"Must confirm delivery: StatusCallbacks mandatory. Alert your system on ",{"type":40,"tag":158,"props":359,"children":361},{"className":360},[],[362],{"type":46,"value":363},"undelivered",{"type":46,"value":365}," or ",{"type":40,"tag":158,"props":367,"children":369},{"className":368},[],[370],{"type":46,"value":371},"failed",{"type":46,"value":165},{"type":40,"tag":70,"props":374,"children":375},{},[376,381],{"type":40,"tag":112,"props":377,"children":378},{},[379],{"type":46,"value":380},"What's your volume?",{"type":40,"tag":66,"props":382,"children":383},{},[384,389,394],{"type":40,"tag":70,"props":385,"children":386},{},[387],{"type":46,"value":388},"Low (\u003C 100\u002Fday): Direct API calls, simple implementation",{"type":40,"tag":70,"props":390,"children":391},{},[392],{"type":46,"value":393},"Medium (100-10,000\u002Fday): Messaging Services for sender management, queue awareness",{"type":40,"tag":70,"props":395,"children":396},{},[397],{"type":46,"value":398},"High (10,000+\u002Fday): Rate limiting strategy required, multiple sender numbers, exponential backoff",{"type":40,"tag":41,"props":400,"children":402},{"id":401},"step-3-assess-sophistication-the-notification-ladder",[403],{"type":46,"value":404},"Step 3: Assess Sophistication — The Notification Ladder",{"type":40,"tag":406,"props":407,"children":409},"h3",{"id":408},"level-1-single-channel-notification",[410],{"type":46,"value":411},"Level 1: Single-Channel Notification",{"type":40,"tag":49,"props":413,"children":414},{},[415,420,422,427,429,434],{"type":40,"tag":112,"props":416,"children":417},{},[418],{"type":46,"value":419},"Developer says:",{"type":46,"value":421}," \"I need to send SMS\u002Femail when an event happens.\"\n",{"type":40,"tag":112,"props":423,"children":424},{},[425],{"type":46,"value":426},"Architecture:",{"type":46,"value":428}," Direct API call to SMS or SendGrid on event trigger\n",{"type":40,"tag":112,"props":430,"children":431},{},[432],{"type":46,"value":433},"Channel selection by use case",{"type":46,"value":435}," (from Channel Mix Matrix):",{"type":40,"tag":66,"props":437,"children":438},{},[439,449,459],{"type":40,"tag":70,"props":440,"children":441},{},[442,447],{"type":40,"tag":112,"props":443,"children":444},{},[445],{"type":46,"value":446},"Order receipts",{"type":46,"value":448}," → Email (rich content, record-keeping) + optional SMS (immediate confirmation)",{"type":40,"tag":70,"props":450,"children":451},{},[452,457],{"type":40,"tag":112,"props":453,"children":454},{},[455],{"type":46,"value":456},"Shipping updates",{"type":46,"value":458}," → SMS (time-sensitive, short content) or WhatsApp (international)",{"type":40,"tag":70,"props":460,"children":461},{},[462,467,469,474,476,481,483,489,491,497,499,505],{"type":40,"tag":112,"props":463,"children":464},{},[465],{"type":46,"value":466},"Appointment reminders",{"type":46,"value":468}," → SMS (24hr before) + Voice (1hr before for critical)\n",{"type":40,"tag":112,"props":470,"children":471},{},[472],{"type":46,"value":473},"Best practice:",{"type":46,"value":475}," Always include StatusCallback URL. Even for simple sends. Without it, you have zero delivery visibility.\n",{"type":40,"tag":112,"props":477,"children":478},{},[479],{"type":46,"value":480},"Skills to install:",{"type":46,"value":482}," ",{"type":40,"tag":158,"props":484,"children":486},{"className":485},[],[487],{"type":46,"value":488},"twilio-sms-send-message",{"type":46,"value":490}," and\u002For ",{"type":40,"tag":158,"props":492,"children":494},{"className":493},[],[495],{"type":46,"value":496},"twilio-email-send",{"type":46,"value":498}," (Account SID + Auth Token → comms.twilio.com) or ",{"type":40,"tag":158,"props":500,"children":502},{"className":501},[],[503],{"type":46,"value":504},"twilio-sendgrid-email-send",{"type":46,"value":506}," (SendGrid API key, SG.-prefix)",{"type":40,"tag":406,"props":508,"children":510},{"id":509},"level-2-multi-channel-with-priority",[511],{"type":46,"value":512},"Level 2: Multi-Channel with Priority",{"type":40,"tag":49,"props":514,"children":515},{},[516,520,522,526,528],{"type":40,"tag":112,"props":517,"children":518},{},[519],{"type":46,"value":419},{"type":46,"value":521}," \"I want to reach customers on the right channel based on urgency and preference.\"\n",{"type":40,"tag":112,"props":523,"children":524},{},[525],{"type":46,"value":426},{"type":46,"value":527}," Level 1 + channel routing logic + fallback chains\n",{"type":40,"tag":112,"props":529,"children":530},{},[531],{"type":46,"value":532},"Pattern — Urgency-Based Channel Selection:",{"type":40,"tag":534,"props":535,"children":536},"table",{},[537,566],{"type":40,"tag":538,"props":539,"children":540},"thead",{},[541],{"type":40,"tag":542,"props":543,"children":544},"tr",{},[545,551,556,561],{"type":40,"tag":546,"props":547,"children":548},"th",{},[549],{"type":46,"value":550},"Urgency",{"type":40,"tag":546,"props":552,"children":553},{},[554],{"type":46,"value":555},"Primary Channel",{"type":40,"tag":546,"props":557,"children":558},{},[559],{"type":46,"value":560},"Fallback",{"type":40,"tag":546,"props":562,"children":563},{},[564],{"type":46,"value":565},"Example",{"type":40,"tag":567,"props":568,"children":569},"tbody",{},[570,594,617,640],{"type":40,"tag":542,"props":571,"children":572},{},[573,579,584,589],{"type":40,"tag":574,"props":575,"children":576},"td",{},[577],{"type":46,"value":578},"Critical",{"type":40,"tag":574,"props":580,"children":581},{},[582],{"type":46,"value":583},"SMS + Voice (parallel)",{"type":40,"tag":574,"props":585,"children":586},{},[587],{"type":46,"value":588},"—",{"type":40,"tag":574,"props":590,"children":591},{},[592],{"type":46,"value":593},"Fraud alert, security breach",{"type":40,"tag":542,"props":595,"children":596},{},[597,602,607,612],{"type":40,"tag":574,"props":598,"children":599},{},[600],{"type":46,"value":601},"High",{"type":40,"tag":574,"props":603,"children":604},{},[605],{"type":46,"value":606},"SMS",{"type":40,"tag":574,"props":608,"children":609},{},[610],{"type":46,"value":611},"Voice (if undelivered after 5 min)",{"type":40,"tag":574,"props":613,"children":614},{},[615],{"type":46,"value":616},"Appointment in 1 hour",{"type":40,"tag":542,"props":618,"children":619},{},[620,625,630,635],{"type":40,"tag":574,"props":621,"children":622},{},[623],{"type":46,"value":624},"Medium",{"type":40,"tag":574,"props":626,"children":627},{},[628],{"type":46,"value":629},"SMS or WhatsApp",{"type":40,"tag":574,"props":631,"children":632},{},[633],{"type":46,"value":634},"Email",{"type":40,"tag":574,"props":636,"children":637},{},[638],{"type":46,"value":639},"Shipping update",{"type":40,"tag":542,"props":641,"children":642},{},[643,648,652,656],{"type":40,"tag":574,"props":644,"children":645},{},[646],{"type":46,"value":647},"Low",{"type":40,"tag":574,"props":649,"children":650},{},[651],{"type":46,"value":634},{"type":40,"tag":574,"props":653,"children":654},{},[655],{"type":46,"value":588},{"type":40,"tag":574,"props":657,"children":658},{},[659],{"type":46,"value":660},"Weekly summary, receipt",{"type":40,"tag":49,"props":662,"children":663},{},[664],{"type":40,"tag":112,"props":665,"children":666},{},[667],{"type":46,"value":668},"Pattern — Fallback Chain:",{"type":40,"tag":670,"props":671,"children":675},"pre",{"className":672,"code":674,"language":46},[673],"language-text","Send SMS → wait for StatusCallback →\n  if \"delivered\" → done\n  if \"undelivered\" or \"failed\" after 5 min →\n    Send Voice notification → wait →\n      if answered → done\n      if no answer → Send Email as last resort\n",[676],{"type":40,"tag":158,"props":677,"children":679},{"__ignoreMap":678},"",[680],{"type":46,"value":674},{"type":40,"tag":49,"props":682,"children":683},{},[684],{"type":40,"tag":112,"props":685,"children":686},{},[687],{"type":46,"value":688},"Key decisions:",{"type":40,"tag":66,"props":690,"children":691},{},[692,697,702],{"type":40,"tag":70,"props":693,"children":694},{},[695],{"type":46,"value":696},"Fallback timeout: How long to wait before escalating channels? (Balance urgency vs cost)",{"type":40,"tag":70,"props":698,"children":699},{},[700],{"type":46,"value":701},"Customer preference: Let customers choose their preferred channel? (Store in your DB or Segment profile)",{"type":40,"tag":70,"props":703,"children":704},{},[705,707,711,713,719,721],{"type":46,"value":706},"Deduplication: Prevent sending the same notification on multiple channels if one succeeds\n",{"type":40,"tag":112,"props":708,"children":709},{},[710],{"type":46,"value":480},{"type":46,"value":712}," + ",{"type":40,"tag":158,"props":714,"children":716},{"className":715},[],[717],{"type":46,"value":718},"twilio-voice-outbound-calls",{"type":46,"value":720},", ",{"type":40,"tag":158,"props":722,"children":724},{"className":723},[],[725],{"type":46,"value":726},"twilio-whatsapp-send-message",{"type":40,"tag":406,"props":728,"children":730},{"id":729},"level-3-event-driven-pipeline",[731],{"type":46,"value":732},"Level 3: Event-Driven Pipeline",{"type":40,"tag":49,"props":734,"children":735},{},[736,740,742,746,748,753,755],{"type":40,"tag":112,"props":737,"children":738},{},[739],{"type":46,"value":419},{"type":46,"value":741}," \"I want notifications triggered automatically from my backend events, with delivery analytics.\"\n",{"type":40,"tag":112,"props":743,"children":744},{},[745],{"type":46,"value":426},{"type":46,"value":747}," Level 2 + Messaging Services + StatusCallback analytics + (optionally) Segment\n",{"type":40,"tag":112,"props":749,"children":750},{},[751],{"type":46,"value":752},"What it adds:",{"type":46,"value":754}," Messaging Services handles sender selection and delivery optimization. StatusCallbacks feed into your analytics pipeline. Segment captures notification events for customer journey tracking.\n",{"type":40,"tag":112,"props":756,"children":757},{},[758],{"type":46,"value":688},{"type":40,"tag":66,"props":760,"children":761},{},[762,767,772],{"type":40,"tag":70,"props":763,"children":764},{},[765],{"type":46,"value":766},"Event source: Your backend webhook → Twilio Function → API call (simplest). Or Segment event → Engage → Twilio (most sophisticated).",{"type":40,"tag":70,"props":768,"children":769},{},[770],{"type":46,"value":771},"Analytics: Log delivery status (queued → sent → delivered\u002Ffailed) for SLA monitoring",{"type":40,"tag":70,"props":773,"children":774},{},[775,777,781,782],{"type":46,"value":776},"Scheduling: Use Twilio's scheduling (SMS: up to 7 days) or your own job scheduler for complex timing\n",{"type":40,"tag":112,"props":778,"children":779},{},[780],{"type":46,"value":480},{"type":46,"value":712},{"type":40,"tag":158,"props":783,"children":785},{"className":784},[],[786],{"type":46,"value":787},"twilio-messaging-services",{"type":40,"tag":41,"props":789,"children":791},{"id":790},"decision-rules",[792],{"type":46,"value":793},"Decision Rules",{"type":40,"tag":406,"props":795,"children":797},{"id":796},"channel-selection-quick-reference",[798],{"type":46,"value":799},"Channel Selection Quick Reference",{"type":40,"tag":66,"props":801,"children":802},{},[803,813,823,833],{"type":40,"tag":70,"props":804,"children":805},{},[806,811],{"type":40,"tag":112,"props":807,"children":808},{},[809],{"type":46,"value":810},"SMS:",{"type":46,"value":812}," Universal reach, instant delivery, 160 chars (or 1,600 with concatenation). Best for short, urgent messages. Most expensive per-message of the text channels.",{"type":40,"tag":70,"props":814,"children":815},{},[816,821],{"type":40,"tag":112,"props":817,"children":818},{},[819],{"type":46,"value":820},"Email (SendGrid):",{"type":46,"value":822}," Unlimited content, rich HTML, attachments. Lowest cost. Slowest open rate. Best for receipts, summaries, non-urgent.",{"type":40,"tag":70,"props":824,"children":825},{},[826,831],{"type":40,"tag":112,"props":827,"children":828},{},[829],{"type":46,"value":830},"WhatsApp:",{"type":46,"value":832}," Rich media, interactive buttons, international reach. Requires template approval for outbound. Best for markets where WhatsApp dominates (India, Brazil, EU).",{"type":40,"tag":70,"props":834,"children":835},{},[836,841],{"type":40,"tag":112,"props":837,"children":838},{},[839],{"type":46,"value":840},"Voice:",{"type":46,"value":842}," Highest urgency signal — phone rings, demands attention. Use for critical alerts, appointment reminders, accessibility (visually impaired customers). Most expensive.",{"type":40,"tag":406,"props":844,"children":846},{"id":845},"statuscallbacks-mandatory-best-practice",[847],{"type":46,"value":848},"StatusCallbacks — Mandatory Best Practice",{"type":40,"tag":49,"props":850,"children":851},{},[852],{"type":46,"value":853},"Always inject StatusCallback URLs into every send.",{"type":40,"tag":66,"props":855,"children":856},{},[857,870,883,888],{"type":40,"tag":70,"props":858,"children":859},{},[860,862,868],{"type":46,"value":861},"SMS: StatusCallback parameter on every ",{"type":40,"tag":158,"props":863,"children":865},{"className":864},[],[866],{"type":46,"value":867},"messages.create()",{"type":46,"value":869}," call",{"type":40,"tag":70,"props":871,"children":872},{},[873,875,881],{"type":46,"value":874},"Voice: StatusCallback on ",{"type":40,"tag":158,"props":876,"children":878},{"className":877},[],[879],{"type":46,"value":880},"calls.create()",{"type":46,"value":882}," and within TwiML verbs",{"type":40,"tag":70,"props":884,"children":885},{},[886],{"type":46,"value":887},"Email: SendGrid Event Webhooks for delivery, open, click, bounce",{"type":40,"tag":70,"props":889,"children":890},{},[891],{"type":46,"value":892},"Without StatusCallbacks, you have zero visibility into delivery success.",{"type":40,"tag":406,"props":894,"children":896},{"id":895},"rate-limiting-for-notifications",[897],{"type":46,"value":898},"Rate Limiting for Notifications",{"type":40,"tag":66,"props":900,"children":901},{},[902,907,912,917],{"type":40,"tag":70,"props":903,"children":904},{},[905],{"type":46,"value":906},"Notifications are usually lower volume than marketing, but spikes happen (system alerts, mass events)",{"type":40,"tag":70,"props":908,"children":909},{},[910],{"type":46,"value":911},"Always implement 429 handling with exponential backoff (±10% jitter)",{"type":40,"tag":70,"props":913,"children":914},{},[915],{"type":46,"value":916},"Use Messaging Services even for notifications — it handles queuing and throughput optimization",{"type":40,"tag":70,"props":918,"children":919},{},[920],{"type":46,"value":921},"For Voice alerts: concurrent call limits apply. Queue calls if bursting.",{"type":40,"tag":41,"props":923,"children":925},{"id":924},"output-format",[926],{"type":46,"value":927},"Output Format",{"type":40,"tag":49,"props":929,"children":930},{},[931],{"type":46,"value":932},"After qualifying the developer, recommend:",{"type":40,"tag":670,"props":934,"children":937},{"className":935,"code":936,"language":46},[673],"Recommended Architecture: [Brief plain-language description of the recommended approach — e.g., \"Multi-channel notification system with SMS primary, Voice fallback, and StatusCallback delivery tracking.\"]\n\nReference Skills:\n- twilio-messaging-channel-advisor (if channel not yet confirmed — qualifies SMS vs RCS vs WhatsApp)\n- twilio-sms-send-message (if SMS notifications)\n- twilio-rcs-messaging (if RCS notifications)\n- twilio-email-send (if email notifications, Twilio creds — Account SID + Auth Token) or twilio-sendgrid-email-send (if SendGrid API key, SG.-prefix)\n- twilio-voice-outbound-calls (if voice alerts or fallback)\n- twilio-whatsapp-send-message (if WhatsApp notifications)\n- twilio-messaging-services (if volume > 100\u002Fday or multi-number)\n\nSetup Skills:\n- twilio-account-setup — if developer needs help with credentials or account structure\n- twilio-iam-auth-setup — if developer asks about API key scoping or security\n- twilio-numbers-senders — number type selection affects throughput and compliance timelines; use when choosing between local, toll-free, or short code\n- twilio-webhook-architecture — if developer needs help with StatusCallbacks or delivery tracking webhooks\n\nGuardrail Skills:\n- twilio-reliability-patterns (always — backoff, retry, fallback chains)\n- twilio-security-hardening (credential management)\n- twilio-compliance-traffic (opt-out handling, quiet hours)\n",[938],{"type":40,"tag":158,"props":939,"children":940},{"__ignoreMap":678},[941],{"type":46,"value":936},{"items":943,"total":1048},[944,959,979,990,1002,1017,1034],{"slug":945,"name":945,"fn":946,"description":947,"org":948,"tags":949,"stars":23,"repoUrl":24,"updatedAt":958},"twilio-account-setup","configure Twilio accounts and credentials","Create and configure a Twilio account from scratch. Covers free trial signup, trial limitations, getting credentials (Account SID and Auth Token), buying a phone number, verifying recipient numbers for trial use, SDK installation, first API call, subaccount management (creation, inheritance, credential isolation, limits), and enabling specific products (AI Assistants, Conversations, Verify, ConversationRelay, WhatsApp). Use this skill before any other Twilio skill if you do not yet have a Twilio account or need to enable a product. For Organization-level governance (SSO, SCIM, multi-team), see `twilio-organizations-setup`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[950,953,956],{"name":951,"slug":952,"type":15},"API Development","api-development",{"name":954,"slug":955,"type":15},"Communications","communications",{"name":606,"slug":957,"type":15},"sms","2026-08-01T05:43:28.968968",{"slug":960,"name":960,"fn":961,"description":962,"org":963,"tags":964,"stars":23,"repoUrl":24,"updatedAt":978},"twilio-agent-augmentation-architect","augment human agents with AI intelligence","Planning skill for augmenting human agents with real-time AI intelligence. Qualifies the developer's use case across coaching, compliance, QA, and routing to recommend the right Conversation Intelligence + Conversation Memory + TaskRouter architecture. Handles both \"I want to add AI coaching to my call center\" and \"configure Conversation Intelligence operators for script adherence.\"\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[965,968,971,974,977],{"name":966,"slug":967,"type":15},"Agents","agents",{"name":969,"slug":970,"type":15},"AI","ai",{"name":972,"slug":973,"type":15},"Coaching","coaching",{"name":975,"slug":976,"type":15},"QA","qa",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:58.250609",{"slug":980,"name":980,"fn":981,"description":982,"org":983,"tags":984,"stars":23,"repoUrl":24,"updatedAt":989},"twilio-agent-connect","connect AI agents to Twilio channels","Connect third-party AI agents (OpenAI, Bedrock, LangChain, Microsoft Foundry) to Twilio's communication channels using the Twilio Agent Connect SDK. Covers identity resolution, memory and context management via Conversation Memory, conversation orchestration via Conversation Orchestrator, multi-channel handling (Voice, SMS, RCS, WhatsApp, Chat), and AI-to-human escalation. Use this skill when integrating an existing LLM agent with Twilio services.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[985,986,987,988],{"name":966,"slug":967,"type":15},{"name":951,"slug":952,"type":15},{"name":954,"slug":955,"type":15},{"name":9,"slug":8,"type":15},"2026-07-17T06:06:05.217098",{"slug":991,"name":991,"fn":992,"description":993,"org":994,"tags":995,"stars":23,"repoUrl":24,"updatedAt":1001},"twilio-ai-agent-architect","plan Twilio conversational AI agents","Planning skill for AI-powered conversational agents. Qualifies the developer's use case across outcome sophistication, entry point, and customer profile to recommend the right Twilio Conversations architecture and implementation skills. Handles both high-level requests (\"build me a voice AI assistant\") and specific ones (\"integrate ConversationRelay with my OpenAI backend\").\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[996,997,1000],{"name":966,"slug":967,"type":15},{"name":998,"slug":999,"type":15},"Architecture","architecture",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:48.883723",{"slug":1003,"name":1003,"fn":1004,"description":1005,"org":1006,"tags":1007,"stars":23,"repoUrl":24,"updatedAt":1016},"twilio-call-recordings","record and manage Twilio voice calls","Record Twilio voice calls correctly. Covers the critical distinction between Record verb (voicemail) and Dial record (call recording), dual-channel for QA, mid-call pause for PCI, Conference recording, and the ConversationRelay workaround. Use this skill whenever you need to capture call audio for compliance, QA, or analytics.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1008,1011,1014,1015],{"name":1009,"slug":1010,"type":15},"Audio","audio",{"name":1012,"slug":1013,"type":15},"Compliance","compliance",{"name":975,"slug":976,"type":15},{"name":9,"slug":8,"type":15},"2026-07-17T06:07:55.268412",{"slug":1018,"name":1018,"fn":1019,"description":1020,"org":1021,"tags":1022,"stars":23,"repoUrl":24,"updatedAt":1033},"twilio-cli-reference","manage Twilio resources via CLI","Twilio CLI reference for managing Twilio resources from the terminal. Covers installation, credential profiles, phone number provisioning, sending SMS and email, webhook configuration, local development with a tunneling service, debugging with watch and logs, serverless deployment, and plugin ecosystem. Use when the developer asks to \"just do it\", \"set this up\", \"run a command\", mentions \"CLI\", \"command line\", or \"terminal\", or when an AI agent can execute a task directly instead of writing application code.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1023,1026,1029,1032],{"name":1024,"slug":1025,"type":15},"CLI","cli",{"name":1027,"slug":1028,"type":15},"Local Development","local-development",{"name":1030,"slug":1031,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:54.925664",{"slug":1035,"name":1035,"fn":1036,"description":1037,"org":1038,"tags":1039,"stars":23,"repoUrl":24,"updatedAt":1047},"twilio-compliance-onboarding","manage Twilio messaging and voice compliance","Registrations required BEFORE Twilio traffic works. Covers messaging programs (A2P 10DLC, toll-free verification, WhatsApp WABA, RCS, short code, alphanumeric sender) and voice trust programs (STIR\u002FSHAKEN, Voice Integrity, Branded Calling, CNAM). Each number\u002Fsender type has its own program — registration blocks traffic until complete.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1040,1041,1042,1043,1044],{"name":1012,"slug":1013,"type":15},{"name":17,"slug":18,"type":15},{"name":606,"slug":957,"type":15},{"name":9,"slug":8,"type":15},{"name":1045,"slug":1046,"type":15},"WhatsApp","whatsapp","2026-07-17T06:05:47.897229",57,{"items":1050,"total":1048},[1051,1057,1065,1072,1078,1085,1092,1100,1116,1129,1144,1162],{"slug":945,"name":945,"fn":946,"description":947,"org":1052,"tags":1053,"stars":23,"repoUrl":24,"updatedAt":958},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1054,1055,1056],{"name":951,"slug":952,"type":15},{"name":954,"slug":955,"type":15},{"name":606,"slug":957,"type":15},{"slug":960,"name":960,"fn":961,"description":962,"org":1058,"tags":1059,"stars":23,"repoUrl":24,"updatedAt":978},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1060,1061,1062,1063,1064],{"name":966,"slug":967,"type":15},{"name":969,"slug":970,"type":15},{"name":972,"slug":973,"type":15},{"name":975,"slug":976,"type":15},{"name":9,"slug":8,"type":15},{"slug":980,"name":980,"fn":981,"description":982,"org":1066,"tags":1067,"stars":23,"repoUrl":24,"updatedAt":989},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1068,1069,1070,1071],{"name":966,"slug":967,"type":15},{"name":951,"slug":952,"type":15},{"name":954,"slug":955,"type":15},{"name":9,"slug":8,"type":15},{"slug":991,"name":991,"fn":992,"description":993,"org":1073,"tags":1074,"stars":23,"repoUrl":24,"updatedAt":1001},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1075,1076,1077],{"name":966,"slug":967,"type":15},{"name":998,"slug":999,"type":15},{"name":9,"slug":8,"type":15},{"slug":1003,"name":1003,"fn":1004,"description":1005,"org":1079,"tags":1080,"stars":23,"repoUrl":24,"updatedAt":1016},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1081,1082,1083,1084],{"name":1009,"slug":1010,"type":15},{"name":1012,"slug":1013,"type":15},{"name":975,"slug":976,"type":15},{"name":9,"slug":8,"type":15},{"slug":1018,"name":1018,"fn":1019,"description":1020,"org":1086,"tags":1087,"stars":23,"repoUrl":24,"updatedAt":1033},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1088,1089,1090,1091],{"name":1024,"slug":1025,"type":15},{"name":1027,"slug":1028,"type":15},{"name":1030,"slug":1031,"type":15},{"name":9,"slug":8,"type":15},{"slug":1035,"name":1035,"fn":1036,"description":1037,"org":1093,"tags":1094,"stars":23,"repoUrl":24,"updatedAt":1047},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1095,1096,1097,1098,1099],{"name":1012,"slug":1013,"type":15},{"name":17,"slug":18,"type":15},{"name":606,"slug":957,"type":15},{"name":9,"slug":8,"type":15},{"name":1045,"slug":1046,"type":15},{"slug":1101,"name":1101,"fn":1102,"description":1103,"org":1104,"tags":1105,"stars":23,"repoUrl":24,"updatedAt":1115},"twilio-compliance-traffic","ensure compliance for Twilio messaging traffic","Rules you must follow for Twilio messaging and voice traffic. Covers TCPA (consent tiers, quiet hours, DNC), GDPR (EU consent, right to deletion), PCI DSS (payment recording, Pay verb), HIPAA (BAA, PHI), FDCPA (debt collection limits), CAN-SPAM, WhatsApp policies, SHAKEN\u002FSTIR, and consent management patterns. Use this skill proactively when developers have working traffic to ensure they follow the rules.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1106,1107,1108,1111,1114],{"name":1012,"slug":1013,"type":15},{"name":17,"slug":18,"type":15},{"name":1109,"slug":1110,"type":15},"Regulatory Compliance","regulatory-compliance",{"name":1112,"slug":1113,"type":15},"Security","security",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:55.952779",{"slug":1117,"name":1117,"fn":1118,"description":1119,"org":1120,"tags":1121,"stars":23,"repoUrl":24,"updatedAt":1128},"twilio-conference-calls","build multi-party calls with Twilio Conference","Build multi-party calls using Twilio Conference. Covers warm transfer, cold transfer, coaching (whisper), hold vs mute, participant modes, and supervisor barge. Use this skill for any contact center, support line, or scenario requiring transfers, holds, or multi-party calls.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1122,1123,1124,1127],{"name":1009,"slug":1010,"type":15},{"name":954,"slug":955,"type":15},{"name":1125,"slug":1126,"type":15},"Meetings","meetings",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:55.603708",{"slug":1130,"name":1130,"fn":1131,"description":1132,"org":1133,"tags":1134,"stars":23,"repoUrl":24,"updatedAt":1143},"twilio-content-template-builder","create and send message templates with Twilio","Create, manage, and send message templates using Twilio's Content API. Covers template creation for WhatsApp, SMS, RCS, and MMS; variable usage; WhatsApp Meta approval; and sending templates via ContentSid. Use this skill when building structured messages that require pre-approval or consistent formatting across channels.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1135,1137,1138,1139,1142],{"name":634,"slug":1136,"type":15},"email",{"name":17,"slug":18,"type":15},{"name":606,"slug":957,"type":15},{"name":1140,"slug":1141,"type":15},"Templates","templates",{"name":9,"slug":8,"type":15},"2026-07-17T06:04:26.637309",{"slug":1145,"name":1145,"fn":1146,"description":1147,"org":1148,"tags":1149,"stars":23,"repoUrl":24,"updatedAt":1161},"twilio-conversation-intelligence","build conversation intelligence pipelines","Twilio Conversation Intelligence development guide. Use when building real-time or post-call conversation analysis, language operator pipelines, sentiment analysis, agent assist, cross-channel analytics, or querying aggregated conversation insights (sentiment trends, escalation rates, dashboards).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1150,1151,1154,1157,1160],{"name":966,"slug":967,"type":15},{"name":1152,"slug":1153,"type":15},"Analytics","analytics",{"name":1155,"slug":1156,"type":15},"Monitoring","monitoring",{"name":1158,"slug":1159,"type":15},"NLP","nlp",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:52.545387",{"slug":1163,"name":1163,"fn":1164,"description":1165,"org":1166,"tags":1167,"stars":23,"repoUrl":24,"updatedAt":1173},"twilio-conversation-memory","manage conversation memory with Twilio","Store and retrieve conversation context using Twilio Conversation Memory. Covers Memory Store provisioning, profile management, traits, observations, conversation summaries, and semantic Recall. Use this skill to give AI agents or human agents persistent memory of conversations across sessions and channels.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1168,1169,1172],{"name":966,"slug":967,"type":15},{"name":1170,"slug":1171,"type":15},"Memory","memory",{"name":9,"slug":8,"type":15},"2026-07-17T06:04:19.526724"]