Who This Is For / Who It Is Not For
Who this is for: US businesses, compliance owners, marketing ops, and product teams that send or enable A2P SMS and need practical registration, consent, or troubleshooting guidance tied to 10DLC/TCR and TCPA concepts.
Who this is not for: Readers seeking invented fine amounts, guaranteed approval rates, or universal throughput figures; purely P2P consumer texting with no application layer; teams outside US A2P rules who need only foreign-regulator advice.
Short answer: Missing company texts usually come from carrier/app filtering, the business’s unregistered or misconfigured A2P 10DLC setup, your prior STOP/opt-out, or device/plan settings—not from a single mysterious “text outage.” Consumers can check device and carrier basics; businesses must verify Brand/Campaign registration, number association, and consent status.
Definitions
| Term | Meaning |
|---|---|
| A2P 10DLC | Application-to-person messaging over US 10-digit long codes that requires Brand and Campaign registration |
| Brand | Legal business identity registered through a CSP into The Campaign Registry |
| Campaign | Declared messaging use case with samples, description, and opt-in narrative |
| CSP | Campaign Service Provider / messaging platform that submits TCR registrations |
| TCR | The Campaign Registry—central Brand/Campaign registry for 10DLC |
| TCPA | Telephone Consumer Protection Act and implementing FCC rules (including 47 CFR § 64.1200) |
| Prior express written consent | Elevated consent standard often required for telemarketing/advertising texts |
| STOP | Consumer opt-out keyword that must be honored across sending systems |
Quick Checks for Consumers
Try these before assuming the company “isn’t texting”:
- Confirm the number you gave them (new phone? typo?).
- Check spam/junk SMS folders or blocked-sender lists on iOS/Android.
- Disable third-party SMS blocker apps temporarily.
- Ensure SMS is allowed on the plan (some MVNOs or data-only SIMs differ).
- Reply history — if you texted STOP earlier, you may need to opt in again intentionally.
- Ask the company which number they send from and the approximate send time.
- Restart the device / toggle Airplane mode to refresh network registration.
If personal texts work but all business texts fail, filtering or A2P path issues are more likely than a total SMS outage.
Why Businesses’ Messages Get Blocked (Behind the Scenes)
When companies send application-to-person SMS in the US on local long codes, carriers expect A2P 10DLC registration. Per Twilio’s overview, senders must register. Major platforms have moved from surcharging unregistered traffic to blocking it—Twilio announced full blocking of unregistered US A2P 10DLC effective September 1, 2023, with error 30034 as a common signal on that stack.
So a company may “send” from its CRM while the CSP never delivers to your handset.
Business troubleshooting hubs:
Other Business-Side Causes
| Cause | What happens |
|---|---|
| Campaign still Pending | Sends may be disallowed until approval |
| Number not linked to approved Campaign | Looks unregistered |
| Content filtering | Links, SHAFT content, or spam patterns blocked even when registered |
| You are on suppression after STOP | Correct behavior—company should not keep texting |
| Wrong channel | Company emailed or app-pushed instead of SMS |
| Throughput caps | Bursts delayed or partially sent (Brand/Campaign limits; more numbers ≠ more capacity per TCR FAQ) |
| Toll-free unverified | Different path—unverified TFN SMS may be blocked by CSP rules |
Consent vs Deliverability
Even when messages are allowed onto the network, companies should only text recipients who opted in for that program. If you never agreed—or only agreed to shipping alerts—marketing blasts may be unlawful even if they “would have delivered.” Consumers who want messages should complete the company’s opt-in (form, keyword, etc.) again if unsure.
What Businesses Should Do When Customers Report Silence
- Pull the message log / CSP error code for that MSISDN.
- Confirm Brand + Campaign approved and number associated.
- Confirm recipient not on STOP list.
- Compare template to registered samples/use case.
- Test to multiple carriers (AT&T, T-Mobile, Verizon) — filtering can differ.
- Fix registration or content; then notify the customer through an alternate channel.
Preflight and remediation helpers: MyTCRPlus tools and registration guide how to register with TCR.
Device and Carrier Quirks Worth Knowing
- Short codes sometimes fail on certain MVNOs or international roaming setups differently than long codes.
- Group message threading bugs can hide business traffic in unexpected threads.
- iMessage vs SMS confusion when the company sends SMS from a long code while you expect blue-bubble iMessage.
- Number recycling — your new number may have prior STOP history at some senders until refreshed.
For Support Agents Taking “I Never Got the Text” Tickets
Script:
- Ask for the mobile number on file and confirm it matches the ticket.
- Ask whether the customer ever replied STOP or “unsubscribe.”
- Check CSP logs for that number’s last 48 hours—note error codes.
- If error indicates unregistered/blocked A2P, escalate to messaging compliance—not marketing copywriters.
- If delivered but invisible, coach spam-folder / blocked-sender checks.
- Offer alternate channel (email/voice) for time-sensitive items while deliverability is fixed.
- After fix, send a single confirmed test only if consent still valid.
Never tell customers “carriers banned business texts.” Say “application texts need registration and can be filtered; we’re checking our setup.”
Operating Model and RACI
Treat compliance as an operating system. Assign owners who remain accountable after launch:
| Activity | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Brand legal identity | Finance | Controller | Legal | Ops |
| Campaign samples and descriptions | Marketing ops | Growth lead | Compliance | Support |
| Consent capture UX | Product | Product lead | Legal | Engineering |
| STOP suppression SLA | Engineering | Eng lead | Support | Compliance |
| CSP invoice and fee review | Finance | Controller | Ops | Leadership |
| Incident response for blocks | Messaging ops | COO | CSP support | All senders |
When ownership is ambiguous, shadow IT sending tools appear and registered Campaigns drift from production copy. Reconfirm the RACI every quarter and after any CSP migration. Document escalation contacts for rejection codes and who may edit live templates during incidents.
Evidence Binder and Audit Readiness
Maintain a living binder with Brand submission payloads or console screenshots (secrets redacted); formation and EIN documents used during verification; dated archives of website, privacy policy, and SMS terms URLs; opt-in journey screenshots or recordings; Campaign description, message_flow, and versioned samples; CSP approval or rejection emails and reason codes; STOP and HELP response templates; and monthly exports of opt-out volume and complaint tags. These artifacts accelerate CSP remediations and support legal holds. Align retention with counsel because message logs are frequently discoverable. Index the binder by Campaign ID so on-call staff can find evidence in minutes.
Technical Controls Matrix
| Control | Why it matters | Validation |
|---|---|---|
| Attach numbers only to approved Campaigns | Stops unregistered A2P | Quarterly console audit |
| Immutable production templates | Prevents silent sample drift | RBAC review |
| Dual-write opt-outs to CRM and messaging platform | Closes sync gaps | Automated integration test |
| Link-domain allowlist | Avoids public shortener filters | CI template linter |
| Quiet hours by recipient timezone | Reduces nuisance complaints | Platform config review |
| Fail closed if Campaign inactive | Blocks accidental sends | Pre-send API check |
| Rate caps per Campaign | Avoids burst abuse patterns | Load test and alerts |
| Alert on carrier error spikes | Faster incident response | Observability dashboard |
Engineering should treat Campaign-not-active as a hard failure, not a warning. Pair controls with runbooks that name the first three debugging steps for the most common CSP error codes.
Governance Cadence
Weekly: deliverability and error-code review; spot-check Brand identification and STOP language on random outbound messages. Monthly: consent QA for every new lead source; confirm privacy and SMS URLs still load without login. Quarterly: full Campaign-to-production alignment; refresh training; read the CSP 10DLC changelog end to end. Annually: reconfirm legal name, tax ID, and authorized representatives; renew vendor diligence. Publish a one-page leadership scorecard covering share of traffic on registered Campaigns, opt-out rate, open remediations, and time-to-suppress after STOP.
Vendor and ISV Diligence
If an agency, ATS, EHR, CRM, or ISV sends on your behalf, contract for your organization as Brand of record unless a deliberate reseller model applies; notice within an agreed window of Campaign rejection or suspension; shared dashboards or weekly status exports; STOP propagation into your system of record within minutes; prohibition on mixing unrelated customers onto your Campaign; and an annual security and compliance questionnaire. Many filtering events originate in reseller infrastructure. Diligence is cheaper than silent non-delivery during peak season. Keep a vendor inventory that lists every system capable of emitting SMS.
Legal Overlay (Not Legal Advice)
Registration and consent are related but distinct. An approved Campaign does not prove TCPA consent for a particular send; perfect consent records do not move unregistered traffic through carrier blocks. Coordinate with counsel on when prior express written consent is required, how revocation must be honored under 47 CFR section 64.1200 and related FCC guidance, which state mini-TCPA rules apply to your footprint, retention periods for consent artifacts, and vendor liability terms. Do not invent statutory penalty figures in training decks—cite primary sources and counsel memos instead. Revisit the overlay whenever marketing launches a new list source or message purpose.
Soft CTA
Prepare Brand packets, public SMS disclosures, and pre-submission diagnostics with MyTCRPlus tools at https://mytcrplus.com/tools/ and related microsite options. They help you organize evidence for your CSP—they do not guarantee approval, throughput, or legal compliance. Pair preparation with the step-by-step TCR registration guide at https://mytcrplus.com/how-to-register-with-tcr-the-complete-step-by-step-process-for-10dlc/ and troubleshooting pages for unregistered traffic blocks when deliverability collapses.
Change-Control Playbook
When templates, vendors, or CSP rules change: log the source URL and timestamp; classify impact across Brand, Campaign, consent UX, billing, and API; freeze related sends if resubmission is likely; assign one incident owner with a clear due date; notify support and marketing with non-speculative language; retest major US carriers after the fix; and write a short postmortem that updates the runbook. Controlled change beats reactive copy edits during an outage. Store playbook outcomes beside the evidence binder so audits show both prevention and response.
Launch and Scale Checklist
| Step | Owner | Artifact |
|---|---|---|
| Inventory senders and templates | Ops | Spreadsheet |
| Classify marketing vs operational | Compliance | Matrix |
| Confirm Brand legal entity | Finance | EIN docs |
| Publish SMS disclosures | Web / legal | Live URLs |
| Draft Campaign packet | Ops | Samples and flow |
| Submit Brand and Campaign via CSP | Admin | IDs and status |
| Configure STOP and HELP | Engineering | Test log |
| Train staff | Manager | Sign-off |
| Carrier smoke test | Engineering | Delivery matrix |
| Quarterly audit | Compliance | Memo |
Do not skip the smoke test. A Campaign can show approved while a single MNO still has not provisioned the share, producing carrier-specific failures that look like random filtering to marketers.
Decision Framework Recap
- Confirm you are sending US A2P over local 10DLC (vs toll-free or short code).
- Map each template to marketing or operational purpose.
- Assemble accurate Brand identity and public website evidence.
- Write Campaign narratives and samples that match production truth.
- Submit through your CSP and wait for Brand eligibility before Campaign create.
- Attach numbers only after Campaign approval and provisioning.
- Enforce STOP globally and monitor error codes.
- Audit consent artifacts and sample drift on a fixed calendar.
- Escalate CSP reason codes with evidence—not guesses.
- Keep TCPA counsel in the loop for new message purposes.
This framework applies whether you run healthcare reminders, staffing shift fills, nonprofit fundraising, or retail promotions.
Operating Model and RACI (continued 10)
Treat compliance as an operating system. Assign owners who remain accountable after launch:
| Activity | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Brand legal identity | Finance | Controller | Legal | Ops |
| Campaign samples and descriptions | Marketing ops | Growth lead | Compliance | Support |
| Consent capture UX | Product | Product lead | Legal | Engineering |
| STOP suppression SLA | Engineering | Eng lead | Support | Compliance |
| CSP invoice and fee review | Finance | Controller | Ops | Leadership |
| Incident response for blocks | Messaging ops | COO | CSP support | All senders |
When ownership is ambiguous, shadow IT sending tools appear and registered Campaigns drift from production copy. Reconfirm the RACI every quarter and after any CSP migration. Document escalation contacts for rejection codes and who may edit live templates during incidents.
Evidence Binder and Audit Readiness (continued 11)
Maintain a living binder with Brand submission payloads or console screenshots (secrets redacted); formation and EIN documents used during verification; dated archives of website, privacy policy, and SMS terms URLs; opt-in journey screenshots or recordings; Campaign description, message_flow, and versioned samples; CSP approval or rejection emails and reason codes; STOP and HELP response templates; and monthly exports of opt-out volume and complaint tags. These artifacts accelerate CSP remediations and support legal holds. Align retention with counsel because message logs are frequently discoverable. Index the binder by Campaign ID so on-call staff can find evidence in minutes.
Technical Controls Matrix (continued 12)
| Control | Why it matters | Validation |
|---|---|---|
| Attach numbers only to approved Campaigns | Stops unregistered A2P | Quarterly console audit |
| Immutable production templates | Prevents silent sample drift | RBAC review |
| Dual-write opt-outs to CRM and messaging platform | Closes sync gaps | Automated integration test |
| Link-domain allowlist | Avoids public shortener filters | CI template linter |
| Quiet hours by recipient timezone | Reduces nuisance complaints | Platform config review |
| Fail closed if Campaign inactive | Blocks accidental sends | Pre-send API check |
| Rate caps per Campaign | Avoids burst abuse patterns | Load test and alerts |
| Alert on carrier error spikes | Faster incident response | Observability dashboard |
Engineering should treat Campaign-not-active as a hard failure, not a warning. Pair controls with runbooks that name the first three debugging steps for the most common CSP error codes.
Governance Cadence (continued 13)
Weekly: deliverability and error-code review; spot-check Brand identification and STOP language on random outbound messages. Monthly: consent QA for every new lead source; confirm privacy and SMS URLs still load without login. Quarterly: full Campaign-to-production alignment; refresh training; read the CSP 10DLC changelog end to end. Annually: reconfirm legal name, tax ID, and authorized representatives; renew vendor diligence. Publish a one-page leadership scorecard covering share of traffic on registered Campaigns, opt-out rate, open remediations, and time-to-suppress after STOP.
Risks and Failure Modes
| Risk / failure mode | Impact | Mitigation |
|---|---|---|
| Unregistered or mismatched Campaign traffic | Blocking or filtering | Register accurately; align samples to production |
| Consent gaps on marketing sends | Legal and complaint exposure | Capture purpose-specific consent; retain artifacts |
| Slow or partial STOP handling | Carrier and TCPA risk | Automate suppression across all senders |
| Website or policy URL failures | Brand/Campaign rejection | Keep public HTTPS pages live and consistent |
| Sample drift after approval | Filtering or re-review | Change-control templates; version samples |
| Treating TCR status as legal safe harbor | False confidence | Maintain separate TCPA/compliance program |
FAQ
Why do I get texts from friends but not from stores?
Personal P2P traffic differs from A2P application traffic. Stores must register and pass filters; friends generally do not use TCR Campaigns.
Did carriers ban all company texts?
No. Registered, consented, non-abusive programs continue. Unregistered 10DLC is widely blocked on major CSP platforms.
I texted STOP by mistake—how do I fix it?
Contact the company through another channel and complete a fresh opt-in if you want messages again. Do not expect STOP to reverse automatically.
Can MyTCRPlus make my phone receive texts?
It helps businesses fix registration/compliance packaging. Consumers should work with the sender and their carrier/device settings.
Key Takeaways
- Meet both carrier registration duties and consent/legal duties—neither replaces the other.
- Keep Brand identity, website evidence, Campaign samples, and production traffic aligned.
- Document who messages are for and how consumers opted in; honor STOP quickly.
- Use CSP reason codes and primary sources when remediating—not rumor threads.
- Avoid inventing fees, fines, or throughput guarantees in policies or marketing.
- Audit quarterly for consent drift, template drift, and vendor sprawl.
- Escalate legally sensitive launches to qualified counsel.
- MyTCRPlus tools can help organize evidence; they do not guarantee approval or delivery.
Disclaimer
This article is for informational purposes only and is not legal advice. Carrier filtering, CSP errors, and TCPA rules change. Businesses should confirm configurations with their CSP; consumers with persistent device issues should contact their wireless carrier.