Question 1

What does multi-location SMS broadcast actually deliver, and how does it sit relative to the auto-text SMS followup sibling skill?

Accepted Answer

An orchestration layer that sits above the operator SMS-platform + marketing-automation + 10DLC-registration + carrier-verification + DNC + FCC-RND + consent-management + lookup + spam-detection + policy-as-code + WORM-storage stack and runs proactive operator-initiated marketing SMS to opted-in subscribers across all operator locations. Where the auto-text SMS followup sibling skill (covered at the lost-call-recovery agent) fires reactively in response to a missed inbound call within the recovery half-life, multi-location SMS broadcast fires proactively — scheduled or event-triggered campaigns to large opted-in subscriber populations. The compliance posture differs: proactive marketing SMS requires TCPA prior express written consent obtained at subscriber acquisition (the consent record must survive TCPA discovery years later); reactive auto-text-back has a narrower consent path tied to the incoming call. The skill is a five-skill bundle on the communication-broadcast agent. Skill 1 — Segment: build per-location SMS broadcast audiences across 18+ segmentation dimensions (active subscriber, lapsed subscriber, dormant subscriber, tier-based, vertical-based, RFM, LTV projection, propensity to convert, propensity to churn, response history, offer redemption history, appointment history, complaint history, refund history, NPS history, chargeback history, language preference, communication preference) with per-segment eligibility + frequency cap + cool down + budget cap. Skill 2 — Personalize: render per-broadcast per-recipient personalization (first name, last name, location name, banner name, tier name, offer-personalization token, timezone-aware localization, language-aware localization, currency-aware localization, per-jurisdiction-disclosure localization, per-jurisdiction-footer localization). Skill 3 — Throttle: route through operator-chosen SMS platforms (Twilio, Bandwidth, Plivo, Inteliquent, Telnyx, Vonage SMS, MessageBird, Sinch, Infobip, Tata Communications) and marketing-automation SMS vendors (Klaviyo, Iterable, Braze, Customer.io, Attentive, Postscript, Yotpo SMSBump, Privy, Sender, SimpleTexting, EZ Texting) with throttling against per-platform 10DLC per-second/minute/hour/day/month throughput + per-carrier trust-score (T-Mobile, AT&T, Verizon — set by The Campaign Registry vetting) + per-carrier rate limit + STIR/SHAKEN attestation tier + per-platform queue-depth management. Skill 4 — Gate: verify per-broadcast per-recipient compliance (TCPA prior express written consent, per-state mini-TCPA enhanced consent where applicable, 10DLC + TCR per-campaign registration, state DNC, Federal DNC, state Wiretap, Federal Wiretap, per-vertical DNC, STOP-list, HELP-keyword, UNSUBSCRIBE-keyword, per-recipient HIPAA, FDA OPDP, DEA, DISCUS, FDA CTP, state licensing-board, FTC Section 5, state UCEMA, state telemarketing acts, CASL, UK PECR, EU ePrivacy, state CARD Act, COPPA, AADC). Skill 5 — Feedback: emit per-broadcast per-outcome to the lost-call-recovery + auto-text-SMS-followup + customer-graph + master-record-sync sibling skills via the operator-chosen event broker (shared event broker with customer-change-event-emission + master-record-sync) with deliverability, engagement, response, conversion, revenue, LTV, opt-out, complaint, DNC-flag signals. Every Segment, Personalize, Throttle, Gate, Feedback decision routes through the 5-anchor compliance gate and writes to the WORM audit trail. The SMS-platform, marketing-automation, 10DLC/TCR, carrier-verification, DNC, FCC-RND, consent, lookup, spam-detection vendors below ship strong primitives. The orchestration above them — segmentation, personalization, throttling, compliance gating, outcome feedback, audit trail — is operator-side architecture.

Question 2

Where does single-vendor SMS broadcast stop compounding for multi-location operators?

Accepted Answer

Single-vendor SMS broadcast is solved. Attentive ships a strong multi-segment SMS marketing platform with built-in compliance helpers. Postscript ships strong Shopify-native SMS. Klaviyo + Iterable + Braze + Customer.io ship strong omnichannel including SMS. Twilio + Bandwidth + Plivo ship strong SMS-platform primitives. The compound case the communication-broadcast agent has to handle is the one where a 200-1,500 location operator has 1M-10M opted-in subscribers spread across multiple banners + multiple verticals + multiple jurisdictions, sends scheduled + event-triggered broadcasts that respect per-location frequency caps (a subscriber opted into Banner A and Banner B should not get two competing broadcasts in the same hour), per-vertical compliance overlays (alcohol-vertical SMS triggers DISCUS Code, -vertical SMS triggers per--regulator restrictions, pharma-vertical SMS triggers FDA OPDP, healthcare-vertical SMS triggers HIPAA when subscriber data carries PHI), per-state mini-TCPA enhancements (Florida Telephone Solicitation Act of 2021 enhances consent requirements beyond TCPA federal baseline; Oklahoma Mini-TCPA + Washington CEMA + Maryland Telephone Consumer Protection Act do similar), per-carrier SHAFT-C category restrictions enforced through The Campaign Registry vetting and per-carrier trust scores (T-Mobile and Verizon score campaigns; low trust scores throttle per-second throughput aggressively), international subscribers governed by CASL Section 6 (Canada) + UK PECR Regulation 22 (UK) + EU ePrivacy Article 13(3) (EU). Without an orchestration layer above the SMS-platform + marketing-automation + 10DLC/TCR + DNC + consent vendors, per-location frequency cap enforcement breaks down across banners, per-vertical SHAFT-C category restrictions get flagged inconsistently across vendors, per-state mini-TCPA enhanced consent requirements get missed (Florida ATDS-equivalent definitions broader than federal TCPA), international consent regimes get unapplied, and the audit trail of "what consent did we have, when, against what privacy-policy version, with what carrier-trust-score routing, against which campaign registration" splinters across vendor consoles. The orchestration above the vendors is what holds the cross-vendor + cross-banner + cross-vertical + cross-state + cross-international invariants.

Question 3

How does Skill 4 Gate handle TCPA + state mini-TCPA + 10DLC/TCR + SHAFT-C + STIR/SHAKEN in sequence?

Accepted Answer

The Gate runs as a sequential check cascade with operator-counsel-set fail-fast behavior. Step 1: TCPA prior express written consent verification. The operator consent-management vendor (OneTrust, TrustArc, Ketch, Securiti, BigID — operator chooses) returns the subscriber consent state with timestamp + IP + user-agent + privacy-policy-version + terms-of-service-version + disclosure-language-version at the moment of consent capture. The Gate verifies the consent is for the specific marketing class the broadcast falls into; operator counsel maintains the per-class mapping (transactional vs marketing vs informational). TCPA prior express written consent for marketing requires a clear and conspicuous disclosure that the subscriber agreed to receive marketing SMS at a specific number using an automatic telephone dialing system (or its equivalent); the operator counsel maintains the per-acquisition-channel disclosure-language library. Step 2: per-state mini-TCPA enhanced consent check. Florida Telephone Solicitation Act of 2021 broadens the "automated system" definition; operator counsel sets the per-state enhanced-consent threshold. Oklahoma Mini-TCPA + Washington CEMA + Maryland TCPA + similar state patchwork apply. The Gate routes the per-recipient through the per-state enhanced consent register. Step 3: 10DLC + The Campaign Registry per-campaign routing. The operator brand is registered on TCR; per-campaign registration determines per-carrier trust score + per-carrier throughput; the Gate routes the broadcast through the matching TCR campaign (Customer Care for transactional, Marketing for promotional, Lower-volume Mixed for blended, etc per current TCR Use Case taxonomy). Step 4: SHAFT-C category check. Each carrier (T-Mobile, AT&T, Verizon) maintains its own acceptable-use policy with restrictions on Sex + Hate + Alcohol + Firearms + Tobacco +  content categories. For alcohol-vertical operators, DISCUS Code adds + state liquor-board adds; the per-carrier SHAFT-C check refuses to commit alcohol-marketing SMS through campaigns or carriers that prohibit. For  operators, most carriers + most states refuse SMS marketing entirely; the operator counsel maintains the per-state per-carrier -SMS allow list. Step 5: STIR/SHAKEN attestation tier check. The FCC TRACED Act + STIR/SHAKEN call-authentication framework requires originating carriers to attest to caller-ID; the Gate reads the STIR/SHAKEN attestation tier (A, B, C) for outbound numbers and downgrades trust for B-attest + C-attest per operator counsel policy. Step 6: Federal DNC + per-state DNC + FCC Reassigned Numbers Database re-verification. Federal DNC, state DNC registries the operator subscribes to (PossibleNOW, Contact Center Compliance, Gryphon Networks, ContactSafe, direct DNC.gov), and FCC RND (Numeracle, RealNumber DB, carrier-vetted partners) all check the per-recipient at send-time (because subscribers can add themselves to DNC after consenting; phone numbers can be reassigned after consent). Step 7: per-vertical claims allowlist + per-vertical SMS-specific restrictions (FDA OPDP DTC pharma SMS rules + DISCUS Code SMS-to-alcohol + per--regulator SMS + FDA CTP tobacco + state medical/dental/pharmacy/optometry/PT licensing-board). Step 8: international consent regimes when applicable (CASL Section 6, UK PECR Regulation 22, EU ePrivacy Article 13(3)). Step 9: COPPA + California AADC + state children-online-privacy when under-13 audience exposure. Every step logs to the WORM audit trail with rule_id + policy_version + decision + evidence_pointer for TCPA + state-AG + private-right-of-action discovery survival. Failed steps fail fast — the Gate refuses to commit the send.

Question 4

How does Skill 3 Throttle manage 10DLC carrier trust scores + per-carrier throughput against per-broadcast urgency?

Accepted Answer

The Throttle skill reads the operator brand + per-campaign trust score from The Campaign Registry via the operator SMS-platform integration (Twilio, Bandwidth, Plivo, Inteliquent, Telnyx, Vonage SMS, MessageBird, Sinch, Infobip, Tata Communications — each integrates with TCR). Per-campaign trust score determines per-carrier per-second throughput cap. T-Mobile applies Vet 5 + Vet 4 + Vet 3 + Vet 1 + Vet 0 trust tiers with corresponding per-second throughput caps (Vet 5 highest, Vet 0 effectively zero). AT&T applies its own ATT 1 + ATT 2 + ATT 3 tiers with corresponding throughput. Verizon applies its own tier system. The Throttle skill reads the per-carrier trust score in real time before the broadcast fires, computes the maximum-deliverable rate against the per-campaign trust-score floor across carriers, and allocates send batches against the cap. When a broadcast has higher urgency than the available throughput would allow within the operator-marketing-team-set delivery window, the Throttle skill surfaces the conflict to the operator marketing team with options — (a) accept slower delivery within compliance, (b) split the broadcast across multiple TCR campaigns with different use-case categories, (c) defer to a future window when carrier trust scores have recovered after recent vetting updates. The Throttle skill never bypasses carrier trust-score throttling; carriers actively monitor per-campaign behavior and downgrade trust scores when senders exceed throughput. STIR/SHAKEN attestation tier (A, B, C) compounds with trust score: B-attest and C-attest calls already carry per-carrier downgraded routing; high-throughput operations must operate at A-attest to maintain reliable delivery. The Throttle skill maintains an operator-counsel-and-engineering-team-approved per-carrier trust-score-recovery playbook for handling sudden trust-score drops (the carrier flagged the operator brand for a content issue — typical recovery involves operator counsel review + content remediation + TCR re-verification cycle). All trust-score reads + throttle decisions write to the WORM audit trail.

Question 5

What compliance does the per-event gate enforce, and how does it map to TCPA + state mini-TCPA, 10DLC/TCR + SHAFT-C, STIR/SHAKEN + FCC RND + DNC, international consent (CASL + PECR + ePrivacy), and per-vertical SMS restrictions?

Accepted Answer

Five anchors. Anchor 1: TCPA (47 USC 227 + 47 CFR 64.1200) + state mini-TCPA laws. TCPA prior express written consent required for marketing SMS to wireless number; statutory damages $500 per negligent violation + $1,500 per willful violation. The FCC 2024-2025 rulemaking around one-to-one consent (proposed effective January 27 2025, requiring per-seller consent for telemarketing) was vacated by the 11th Circuit in IMC v FCC March 2024 before its effective date; operator counsel typically still requires per-recipient + per-seller consent attestation per industry-standard discovery survival. State mini-TCPA laws (Florida Telephone Solicitation Act 2021, Oklahoma Mini-TCPA, Washington Commercial Electronic Mail Act, Maryland Telephone Consumer Protection Act, similar state patchwork) enhance the federal TCPA baseline — Florida specifically broadens the "automated system" definition to include systems federal TCPA does not cover. The gate enforces both federal TCPA + applicable state mini-TCPA per recipient. Anchor 2: 10DLC + The Campaign Registry + CTIA Messaging Principles + per-carrier vetting + SHAFT-C (Sex + Hate + Alcohol + Firearms + Tobacco + ) carrier restrictions. The operator brand registers with TCR + registers per-campaign use cases (Customer Care, Marketing, Account Notification, Public Service Announcement, Lower-volume Mixed, etc per current TCR Use Case taxonomy). Per-campaign vetting produces per-carrier trust scores (T-Mobile + AT&T + Verizon + smaller carriers) that determine per-carrier throughput. SHAFT-C category restrictions vary per carrier; alcohol-vertical operators face DISCUS + state liquor-board restrictions; -vertical operators face per--regulator restrictions plus per-carrier prohibitions in many cases; tobacco-vertical operators face FDA CTP + per-carrier prohibitions; firearms-vertical operators face per-carrier restrictions; sex + hate content faces per-carrier prohibitions. Anchor 3: STIR/SHAKEN + FCC TRACED Act + FCC Reassigned Numbers Database + ROBOCALL Mitigation Database (RMD) + Federal DNC + per-state DNC + state Unfair Commercial Electronic Mail Acts (UCEMA) + state telemarketing-sales-acts. STIR/SHAKEN attestation tier (A, B, C) governs outbound caller-ID trust; the gate refuses or downgrades B-attest and C-attest sends per operator counsel policy. FCC RND query before each send catches reassigned numbers since consent capture. RMD registration is required for operators using A2P SMS at certain volumes. Federal DNC + per-state DNC re-check enforces opt-out status as of send time. State UCEMA + state telemarketing-sales-acts add per-state enforcement layers. Anchor 4: CASL Section 6 (Canadian Anti-Spam Law) + UK PECR Regulation 22 + EU ePrivacy Article 13(3) when international subscribers are present. CASL requires express or implied consent for commercial electronic messages with stricter consent standards than TCPA. UK PECR Regulation 22 requires opt-in for direct marketing electronic communications. EU ePrivacy Article 13(3) requires opt-in for unsolicited communications for direct marketing purposes. The gate enforces per-subscriber-jurisdiction consent regime when the subscriber phone number resolves to Canada, UK, or EU. CAN-SPAM (15 USC 7701) does not directly cover SMS but state-level CEMA equivalents do; the gate composes with state UCEMA where applicable. Anchor 5: Per-vertical SMS-specific marketing restrictions. FDA OPDP rules for direct-to-consumer pharma SMS marketing (specific to prescription products, with substantiation + risk-disclosure obligations). DISCUS Code of Responsible Practices for alcohol-related SMS (age verification + no over-consumption encouragement + state-specific restrictions). Per--regulator SMS rules (most states prohibit or severely restrict  marketing SMS; some states allow only to state-verified-21+ subscribers; some prohibit entirely). FDA Center for Tobacco Products SMS marketing restrictions. State medical/dental/optometry/pharmacy/PT licensing-board rules when SMS targets licensed-professional services. Per-vertical SMS-specific HIPAA implications when healthcare-vertical SMS touches PHI. Broader gate also enforced: COPPA + California AADC + Connecticut SB 3 + DSA Article 28 + ADA Title III + WCAG 2.2 AA + NIST AI RMF + ISO 42001 + ISO 27001 + SOC 2 Type II via policy-as-code (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso). WORM audit trail (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention (TCPA 4yr + CAN-SPAM 5yr + FTC 7yr + state mini-TCPA variable + state UCEMA variable + CASL 6yr + UK PECR 6yr + GDPR 6yr + CCPA 3yr + IRS 7yr + state variable) per operator counsel policy.

Question 6

What does the engagement look like across Tier 1 → Tier 2 → Tier 3, and what does the Tier 3 reporting cycle commit to?

Accepted Answer

Tier 1 AI Readiness Assessment (2-3 weeks, diagnostic): audits the operator current SMS broadcast posture against the 5-skill bundle + 5-anchor compliance gate + per-vendor 10DLC + TCR + carrier-trust-score state; deliverable is a gap-pack report identifying which segmentation dimensions are absent, which personalization paths break per-jurisdiction localization, which throttling configurations are over/under-allocated against per-carrier vetting, which compliance steps in the Gate are missing for which state mini-TCPA jurisdictions, which per-vertical SMS-specific restrictions are unenforced, which international subscriber jurisdictions lack CASL/PECR/ePrivacy consent verification, and a recommended remediation sequence for Tier 2. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the 5-skill bundle on the communication-broadcast agent, wires SMS platforms + marketing-automation SMS vendors (operator-chosen subset), wires 10DLC + TCR brand + per-campaign registration, configures per-carrier vetting + per-carrier trust-score read pipeline, wires Federal DNC + per-state DNC + FCC RND integration, wires consent-management vendor for TCPA + state mini-TCPA + CASL + PECR + ePrivacy verification, configures per-vertical SMS-specific compliance overlay, wires per-platform STIR/SHAKEN attestation tier integration, wires policy-as-code + WORM-storage, runs 30-day shadow + canary period before flipping to enforce-mode. Tier 3 Fractional CMO with AI Swarm (6-month minimum, 1-2 days/wk embedded): continues operating with daily per-broadcast trust-score reads + DNC + FCC RND re-verification, weekly per-state mini-TCPA enhanced consent audits, monthly TCR per-campaign re-vetting cycles, quarterly per-vertical SMS-specific compliance overlay updates, quarterly international subscriber CASL + PECR + ePrivacy audit, quarterly compliance evidence packages. Tier 3 reporting is a 6-workstream pre-engagement-baseline reporting cycle (per-segment broadcast coverage trend + per-recipient personalization completeness + per-broadcast per-carrier deliverability trend + per-recipient compliance-gate pass rate + per-broadcast outcome feedback completeness + WORM audit-trail completeness) measured against the operator’s pre-engagement baseline. Each workstream surfaces trend direction and the gap to operator-defined targets. Reporting carries explicit caveats: SMS-platform + marketing-automation vendor SLA + 10DLC TCR vetting cycle updates + per-carrier trust-score policy updates + FCC RND update cadence + state mini-TCPA statute amendments + CASL + PECR + ePrivacy implementing guidance + FCC TRACED Act + STIR/SHAKEN implementing guidance + per-vertical SMS-specific regulatory amendments + per--regulator + DISCUS Code amendments + FDA OPDP DTC pharma SMS guidance updates + FDA CTP tobacco rule updates sit outside Completions control. Attorney-client privilege preservation across per-acquisition-channel TCPA consent disclosure-language library + per-state mini-TCPA enhanced consent register + per-vertical SMS-specific compliance library + per-vendor TCR + carrier-vetting attestation library + international subscriber CASL + PECR + ePrivacy compliance records is maintained per operator counsel policy.

Question 7

Who owns the SMS platform + marketing-automation relationships, the TCR registration, the consent register, and the audit trail?

Accepted Answer

Operator owns every artifact. The SMS-platform subscriptions (Twilio + Bandwidth + Plivo + Inteliquent + Telnyx + Vonage SMS + MessageBird + Sinch + Infobip + Tata Communications — operator chooses) all run under operator billing on operator-controlled accounts. The marketing-automation SMS subscriptions (Klaviyo + Iterable + Braze + Customer.io + Attentive + Postscript + Yotpo SMSBump + Privy + Sender + SimpleTexting + EZ Texting — operator chooses) run under operator billing. The 10DLC + The Campaign Registry brand + per-campaign registrations run under operator TCR account ownership. The DNC service subscriptions (PossibleNOW + Contact Center Compliance + Gryphon Networks + ContactSafe + direct DNC.gov subscription — operator chooses) run under operator account. The FCC Reassigned Numbers Database access (Numeracle + RealNumber DB + carrier-vetted partners) runs under operator account. The consent-management vendor (OneTrust + TrustArc + Ketch + Securiti + BigID — operator chooses, shared with sibling skills) runs under operator account. The number lookup (Twilio Lookup + Numverify + NumLookup) and spam-detection (Truecaller + Robokiller + Hiya + Nomorobo) integrations run under operator account. The per-acquisition-channel TCPA consent disclosure-language library + per-state mini-TCPA enhanced consent register + per-vertical SMS-specific compliance library + per-vendor TCR + carrier-vetting attestation library + international subscriber CASL + PECR + ePrivacy compliance records all live in operator counsel repo. The Segment + Personalize + Throttle + Gate + Feedback code lives in operator code repo. The per-vertical compliance overlay rule library lives in operator code repo, attorney-approved. The WORM audit trail lives on operator-controlled cloud storage (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention enforcement. The policy-as-code policies (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso) live in operator code repo, counsel-aligned. The TCPA + state mini-TCPA + CAN-SPAM + CASL + PECR + ePrivacy + per-vertical SMS-specific + FDA OPDP + DISCUS + per--regulator + FDA CTP + state licensing-board + COPPA + AADC compliance evidence records are operator-counsel-maintained. Completions owns the orchestration knowledge — how to design the per-location SMS broadcast segmentation for the operator’s actual subscriber + banner + vertical mix, how to wire per-carrier trust-score reads against the operator TCR campaign mix, how to compose the Gate cascade across TCPA + state mini-TCPA + 10DLC/TCR + SHAFT-C + STIR/SHAKEN + DNC + per-vertical + international consent regimes, how to manage trust-score-recovery playbooks with operator counsel, how to integrate Feedback with lost-call-recovery + auto-text-SMS-followup + customer-graph + master-record-sync sibling skills — and that knowledge transfers under the Tier 3 transition path (30-60 days at engagement end with full hand-off of the segmentation contract, the personalization library, the throttling policy, the Gate cascade, the Feedback wiring, and the compliance evidence-package generation playbook). Completions credentials revoke on engagement-end.

The real ecosystem this sits above

SMS platforms

Marketing-automation SMS

10DLC + The Campaign Registry + carrier verification

DNC services + FCC RND + STIR/SHAKEN

Consent management + lookup + spam detection

Policy-as-code + WORM storage + legal research

Frequently asked