architect-sms-infrastructure

Design SMS and MMS infrastructure with number selection and compliance controls.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-sms-infrastructure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-sms-infrastructure
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/architect-sms-infrastructure
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-sms-infrastructure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps architects and platform engineers avoid costly mistakes when provisioning and governing SMS, MMS, and RCS sending infrastructure by centralizing decisions about number selection, compliance, keyword handling, and geographic permissions. It reduces the risk of delivery failures, carrier filtering, legal exposure, and unexpected cost overruns by translating documentation into concrete provisioning and lifecycle actions.

Core Features & Use Cases

  • Provisioning guidance: Compare short codes, long codes (10DLC), toll-free, and alphanumeric sender IDs and understand provisioning timelines and entitlements for MMS.
  • Compliance & policy mapping: Actionable rules for TCPA, CTIA (SHAFT), GDPR considerations, and carrier filtering mitigation including opt-in/opt-out lifecycle handling.
  • Operational controls: Subscription group design, geographic allowlists, keyword precedence, unknown inbound number handling, and message usage accounting.
  • Use case: For a global marketing program, use this skill to choose appropriate number types per country, configure subscription groups and geographic allowlists, register TCR/10DLC where required, and define keyword handling to preserve legal opt-in states.

Quick Start

Audit my SMS/MMS setup and recommend number types, subscription group configuration, keyword handling, and compliance steps for US and Canada.

Frequently Asked Questions about architect-sms-infrastructure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between short codes, 10DLC, and toll-free for SMS provisioning?

SMS compliance requires explicit opt-in and opt-out lifecycle handling, TCPA adherence, and CTIA SHAFT content filtering rules. You must configure keyword precedence, manage subscription groups, and maintain geographic allowlists to prevent legal exposure and delivery failures.

What is TCR registration and when do I need it for 10DLC messaging?

For multi-country SMS campaigns, configure geographic allowlists, select appropriate alphanumeric or numeric sender IDs per region, and apply country-specific subscription groups. Ensure localized compliance rules and MMS enablement are applied across all targeted geographic regions.

How do I handle inbound SMS keyword precedence and unknown numbers?

Handling inbound SMS requires configuring keyword precedence for opt-in and opt-out states to preserve legal compliance. Define explicit administrative permission controls and lifecycle rules for managing unknown inbound numbers to maintain subscription group integrity.

How does message segment accounting work for MMS infrastructure?

Message segment accounting for MMS tracks message throughput and cost by calculating payload segments across enabled sending infrastructure. Proper accounting prevents unexpected cost overruns when provisioning high-throughput multimedia messaging campaigns.