Question 1

What does auto-text SMS followup on missed inbound calls actually deliver, and where does it sit in the lost-call-recovery workflow?

Accepted Answer

An orchestration layer that sits above the operator SMS-platform + 10DLC-registration + call-tracking + lifecycle + DNC + consent-management + number-lookup + spam-detection + policy-as-code + WORM-storage stack and fires a per-lost-call text-back response within the recovery half-life that vendor benchmarks place in the low-single-digit minutes after a missed inbound call. The skill is a two-skill bundle on the lost-call-recovery agent. Skill 1 — per-lost-call template selection: consume the canonical missed-call event from the cross-vendor missed-call event normalization sibling skill, classify the lost-call type across 11 categories (no-answer, voicemail-only, abandoned-in-IVR, abandoned-in-queue, dropped-mid-call, wrong-number-but-qualified, after-hours, holiday, all-agents-busy, wrong-language, wrong-location-routing), and pick a template from the operator-counsel-and-marketing-team-maintained per-location per-vertical SMS template library. Skill 2 — per-jurisdiction send-time gating + per-response branching: gate the send against TCPA 8am-9pm local time zone restriction (47 CFR 64.1200), federal and state holidays per operator counsel policy, the caller’s opt-in history loaded from the operator consent register, the Federal Do Not Call Registry and per-state DNC subscriptions, the caller’s STOP-list status on every operator SMS platform, the operator’s 10DLC throughput allocation (with The Campaign Registry per-campaign throttle), and the receiving carrier’s deliverability tier. Send through the operator-chosen SMS platform (Twilio, Bandwidth, Plivo, Inteliquent, Telnyx, Vonage SMS, MessageBird, Sinch, Infobip). Listen for the inbound response, classify across nine response types (yes, no, maybe, question, opt-out, do-not-call, wrong-number, autoresponse, complaint), and route through ten downstream decisions (auto-followup, queue-for-human-CSR, auto-callback-schedule, auto-appointment-booking, auto-link-redirect, auto-FAQ-answer, auto-deliver-quote, escalate-to-counsel, escalate-to-CS-manager, auto-DNC-flag). Closed-loop feedback to the lost-call CRM record creation sibling skill updates the deliverability + engagement + response + conversion + revenue + LTV data on the CRM record. Every send and every response routes through the 5-anchor compliance gate before commit and writes to the WORM audit trail. The vendors below ship strong primitives. The orchestration above them — template selection, jurisdiction gating, response branching, compliance gate, closed-loop feedback, audit trail — is operator-side architecture.

Question 2

Where does single-vendor SMS automation stop compounding for multi-location lost-call-recovery operators?

Accepted Answer

Single-vendor SMS automation is solved. Twilio ships strong SMS-send primitives. Bandwidth ships strong carrier-relationships. Klaviyo ships strong lifecycle-SMS sequences. The compound case the lost-call-recovery agent has to handle is the one where a 200-location multi-unit franchise operator has a mixed call-tracking footprint (some franchisees on CallRail, some on CallTrackingMetrics, some on Invoca), a mixed SMS-platform footprint (Twilio for corporate-tier, Bandwidth for some franchisees, MessageBird for international markets), a 10DLC registration that the operator counsel maintains under The Campaign Registry with per-campaign approval and per-carrier-vetting trust scores, an opt-in register that spans the operator commerce platform + lifecycle vendor + CRM, a DNC obligation that includes the Federal DNC + 12-plus state DNC registries + per-vertical DNC + the per-platform STOP-list per operator account, and per-jurisdiction TCPA 8am-9pm sending windows that vary by caller location and operator location (the sending hour is the caller’s local time, not the operator’s). Without an orchestration layer above the SMS platforms + 10DLC registration + DNC services + consent vendors + call-tracking vendors, the per-lost-call text-back either fires too late to recover, fires outside the TCPA window, fires to a number on the DNC, fires through an unregistered 10DLC campaign and gets carrier-filtered, or fires from a vendor that the caller’s carrier has down-trust-scored. The lost-call-recovery agent is the orchestration that holds the cross-vendor + cross-jurisdiction + cross-platform invariants.

Question 3

What does 10DLC + The Campaign Registry add, and why is it the central A2P SMS deliverability anchor?

Accepted Answer

For US-originated A2P (application-to-person) SMS sent from a 10-digit long code to a US wireless number, the carriers (T-Mobile, AT&T, Verizon) require registration through The Campaign Registry (TCR). The operator (or operator’s 10DLC service provider) registers a brand with TCR, registers one or more campaigns per use case (Customer Care, Marketing, Account Notification, Public Service Announcement, Lower-volume Mixed, and so on per the current TCR Use Case taxonomy), and gets back a per-carrier-vetting trust score that determines per-campaign throughput (messages per second to T-Mobile, AT&T, Verizon, and the smaller carriers). The orchestration layer reads the operator brand + per-campaign registration + per-campaign throughput + per-carrier-trust-score from the SMS platform’s TCR integration (Twilio, Bandwidth, Plivo, Inteliquent, Telnyx, Vonage SMS, MessageBird, Sinch all integrate with TCR), and gates per-lost-call sends against the available throughput so the operator does not exceed per-carrier limits (which would cause filtering or rate-limit fallback). The orchestration also tracks per-campaign-status (registered, pending, suspended) and routes lost-call followup to the right campaign per the SMS-content classification (a missed-call recovery SMS that includes a transactional callback link maps to Customer Care; a missed-call recovery SMS that includes a promotional offer maps to Marketing — these are different campaigns with different throughput and different vetted-throughput tiers). The orchestration writes the per-send {campaign_id, carrier_trust_score, throughput_consumed, send_status} to the WORM audit trail. The Campaign Registry, the SMS platforms, and the carriers ship strong primitives. The per-campaign routing + per-throughput gating + per-trust-score visibility above them is operator-side architecture.

Question 4

How does the per-response branching layer route opt-outs, do-not-call requests, and complaint signals?

Accepted Answer

Inbound SMS responses route through the SMS-platform inbound webhook (Twilio Inbound SMS, Bandwidth Inbound, etc.) into the orchestration layer’s response classifier. The classifier is an LLM-as-judge (operator chooses model — Claude, GPT, Gemini, Mistral) wrapped with a deterministic STOP-keyword pre-filter and a deterministic DNC-keyword pre-filter. The STOP-keyword pre-filter catches every variant the wireless carriers require platforms to honor (STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT — per CTIA Messaging Principles + Best Practices). Any STOP variant routes immediately to the auto-DNC-flag decision, fires a suppression-list update across every operator SMS platform (so the caller is suppressed even on operator-owned platforms the caller did not specifically opt out from per operator counsel policy), updates the canonical consent register through the operator consent-management vendor (OneTrust, TrustArc, Ketch, Securiti, BigID), and writes the opt-out event to the customer-change-event-emission sibling skill (sibling on the customer-graph agent — handles statutory-window propagation across every linked downstream system). The DNC-keyword pre-filter catches "do not call" variants and routes to the same suppression path. Non-STOP, non-DNC responses route through the LLM classifier (yes, no, maybe, question, autoresponse, complaint, wrong-number). Complaint signals route to escalate-to-counsel + escalate-to-CS-manager per operator counsel policy. Wrong-number signals trigger a number-lookup re-validation (Twilio Lookup, Numverify, NumLookup) and a possible carrier-type reclassification (the caller’s phone may have been reassigned per FCC reassigned-numbers database). Every response classification, every downstream-decision routing, and every consent-register update writes to the WORM audit trail with rule_id, policy_version, decision, and TCPA-compliance-attestation.

Question 5

What compliance does the per-event gate enforce, and how does it map to TCPA, 10DLC/TCR, state DNC, state two-party consent, and per-vertical claims allowlist?

Accepted Answer

Five anchors. Anchor 1: TCPA (47 USC 227 + 47 CFR Part 64). Per-lost-call SMS followup is a wireless-marketing communication unless operator counsel has classified the use case as transactional under the FCC Solicited Messages and Required Disclosures framework. TCPA prior express written consent is required for marketing SMS to a wireless number, and 47 CFR 64.1200(c) restricts call-and-text times to 8am-9pm at the called party’s location. The gate refuses to commit a send outside the TCPA window per the caller’s state (resolved from the caller’s phone NPA-NXX or from caller-provided location). Statutory damages are $500 per negligent violation up to $1,500 per willful violation; the orchestration design treats TCPA as the highest-severity gate. Anchor 2: 10DLC + The Campaign Registry (TCR) + per-carrier vetting + CTIA Messaging Principles + carrier-acceptable-use policies. The per-campaign registration determines per-carrier throughput; the orchestration routes per-content-classification to the right campaign; the gate refuses to commit a send through an unregistered or suspended campaign. Per-carrier acceptable-use policies (T-Mobile Code of Conduct, AT&T Code of Conduct, Verizon Wireless Messaging Policy) layer additional content restrictions (SHAFT-C — Sex, Hate, Alcohol, Firearms, Tobacco, Cannabis — and the operator-vertical-specific carrier rules); the gate composes with the per-vertical claims allowlist (Anchor 5) for these categories. Anchor 3: State DNC + Federal DNC + state-comprehensive-privacy + CCPA right to opt out of sale/sharing. The orchestration runs every send through the Federal DNC (TPS-administered), per-state DNC registries the operator has subscribed to, and per-state-comprehensive-privacy opt-out lists. CCPA Section 1798.120 right to opt out of sale/sharing applies when the lost-call event was captured from a source where data was shared; the gate checks the caller’s CCPA opt-out status before committing the send. Anchor 4: State two-party consent recording laws + CAN-SPAM (when SMS contains commercial-email-equivalent content). When the SMS references a call recording (e.g., "we recorded your call earlier today and want to follow up"), the eleven all-party-consent states (California Penal Code 632, Florida 934.03, Connecticut, Delaware, Illinois 720 ILCS 5/14-2, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, Washington) require the caller’s consent to the recording was obtained — the gate composes with the cross-vendor missed-call event normalization sibling skill (which captures the recording-consent state on the canonical event) and refuses to reference the recording in the SMS body if recording-consent-validated is false. CAN-SPAM (15 USC 7701) applies if the SMS includes a commercial-email-equivalent body (rare but possible for richer SMS or RCS); the gate enforces unsubscribe-link + physical-address + accurate-header requirements where applicable. Anchor 5: Per-vertical claims allowlist + per-state licensing-board advertising rules + HIPAA. For healthcare-vertical lost-calls (dental, medical, optometry, pharmacy, physical therapy), the SMS body cannot include PHI without HIPAA-compliant authorization on file, and state medical/dental/optometry/pharmacy/PT licensing-board advertising rules govern claims language (most state boards prohibit superlative claims like "best dentist" without board-recognized specialty designation). For legal-services lost-calls, state bar advertising rules apply. For financial-services lost-calls, FINRA Rule 2210 applies. For prescription-related lost-calls, FDA OPDP rules apply. For controlled-substance-adjacent lost-calls, DEA scrutiny applies. For cannabis lost-calls, per-state cannabis-regulator rules apply. For alcohol lost-calls, DISCUS Code of Responsible Practices + state liquor-board rules apply. The gate composes with the per-vertical compliance overlay (sibling skill on the compliance-overlay-manager agent) and refuses to commit a send whose anchor text or body content fails the per-vertical claims-allowlist check. Broader gate also enforced: GDPR + UK PECR + EU ePrivacy + CASL when the caller is in those jurisdictions + 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 + HIPAA 6yr + 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 ($10k, 2-3 weeks, diagnostic): audits the operator current auto-text SMS posture against the 2-skill bundle + 5-anchor compliance gate + closed-loop feedback policy; deliverable is a gap-pack report identifying which lost-call types are unhandled, which jurisdictions have unenforced send-time windows, which 10DLC campaigns are mis-registered for the content classification, which DNC subscriptions are missing, which per-vertical claims-allowlist checks are absent, and a recommended remediation sequence for Tier 2. Tier 2 AI Swarm Setup Sprint ($25-50k, 4-8 weeks): builds the 2-skill bundle on the lost-call-recovery agent, wires the operator-chosen SMS platforms with 10DLC/TCR registration, configures per-state DNC subscriptions (PossibleNOW, Contact Center Compliance, Gryphon Networks, ContactSafe — operator chooses), wires the operator consent-management vendor for opt-in/opt-out propagation, configures the operator-counsel-and-marketing-team-approved per-location per-vertical SMS template library, wires the response classifier (LLM-as-judge with deterministic STOP/DNC pre-filter), configures the closed-loop feedback into the lost-call CRM record creation sibling, wires policy-as-code engine, wires WORM-storage, runs 30-day shadow + canary period before flipping to enforce-mode. Tier 3 Fractional CMO with AI Swarm ($15-25k/month, 6-month minimum, 1-2 days/wk embedded): continues operating with per-campaign 10DLC re-registration cycles, per-jurisdiction send-time window updates as regulations change, per-vertical claims-allowlist library maintenance, per-carrier trust-score monitoring, per-response classifier tuning, dead-letter triage, and quarterly compliance evidence packages. Tier 3 reporting is a 6-workstream pre-engagement-baseline reporting cycle (per-lost-call-type template coverage + per-jurisdiction send-time gate adherence + per-campaign 10DLC throughput utilization + per-response classifier accuracy + closed-loop 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 SLA + carrier-trust-score updates (T-Mobile + AT&T + Verizon update per-campaign trust scores on their own cadence) + The Campaign Registry use-case taxonomy updates + per-state DNC registry subscription renewals + per-jurisdiction TCPA implementing regulation changes + FCC reassigned-numbers database updates + CTIA Messaging Principles amendments + per-state licensing-board rule changes + per-state cannabis-regulator updates sit outside Completions control. Attorney-client privilege preservation across per-lost-call-type template library + per-jurisdiction send-time policy + per-campaign 10DLC registration + per-vertical claims-allowlist rules is maintained per operator counsel policy.

Question 7

Who owns the SMS template library, the 10DLC registration, the consent register, the audit trail, and the response classifier?

Accepted Answer

Operator owns every artifact. The SMS template library lives in operator code repo, counsel-and-marketing-team-maintained, with per-location and per-vertical variants. The 10DLC brand and campaign registrations live under operator account ownership on The Campaign Registry (TCR) or through the operator’s 10DLC service provider; per-campaign trust scores and per-carrier vetting all attach to the operator brand. The DNC subscriptions (Federal DNC + per-state DNC + per-vertical DNC + per-platform STOP-list) run under operator account ownership; the orchestration layer reads but does not own these subscriptions. The consent register lives under the operator-chosen consent-management vendor (OneTrust, TrustArc, Ketch, Securiti, BigID) on operator account. The SMS platform subscriptions (Twilio, Bandwidth, Plivo, Inteliquent, Telnyx, Vonage SMS, MessageBird, Sinch, Infobip) run under operator billing. The call-tracking subscriptions (CallRail, Invoca, CallTrackingMetrics, etc.) run under operator billing. The response classifier (LLM-as-judge with deterministic STOP/DNC pre-filter), the per-jurisdiction send-time gate, the per-campaign-routing logic, the per-vertical claims-allowlist library, the closed-loop feedback wiring, and the policy-as-code policies (OPA Rego, AWS Cedar, Casbin, Cerbos, Oso) all live in the operator code repo. The WORM audit trail lives on operator-controlled cloud storage (AWS S3 Object Lock, GCS retention, Azure Blob immutable, Snowflake Time Travel). The TCPA prior express written consent records, the CCPA/state-privacy opt-in/opt-out records, the per-state two-party consent recording records, the HIPAA authorizations (where applicable), and the per-vertical regulatory-attestation records are all operator-counsel-maintained. Completions owns the orchestration knowledge — how to design the per-lost-call-type template selection contract, how to gate sends against TCPA + DNC + 10DLC + per-vertical claims-allowlist simultaneously, how to tune the response classifier without over-classifying STOP-variants, how to route per-content-classification to the right 10DLC campaign, how to debug carrier-trust-score regressions, how to design the closed-loop feedback into the lost-call CRM record creation sibling — and that knowledge transfers under the Tier 3 transition path (30-60 days at engagement end with full hand-off of the template library, the response classifier, the per-campaign routing logic, the per-vertical claims-allowlist library, the closed-loop feedback wiring, and the compliance evidence-package generation playbook). Completions credentials revoke on engagement-end.

Auto-text SMS followup on missed inbound calls for multi-location operators — per-lost-call template selection, per-jurisdiction send-time gating, per-response branching, closed-loop CRM feedback, under a 5-anchor compliance gate

The real ecosystem this sits above

SMS platforms

10DLC + The Campaign Registry

Call tracking (upstream lost-call detection)

DNC services

Consent management + lifecycle + number lookup + spam

Policy-as-code, WORM storage, compliance evidence

Frequently asked