MyTCRPlus.com
Complete User Guide for Plivo Customers
Application-to-Person (A2P) SMS Registration, 10-Digit Long Code (10DLC)
Campaign Administration & Ongoing Compliance Operations
Powered by mytcrplus.com | Tools, Diagnostics, Remediation & Compliance Intelligence
For Plivo Customers | A2P SMS & Business Messaging Compliance
Last Updated: 2025 | mytcrplus.com
Important Notice
This guide is written for Plivo customers using MyTCRPlus.com tools to navigate Application-to-Person (A2P) SMS registration, 10-Digit Long Code (10DLC) compliance, campaign management, and ongoing business text messaging operations.
MyTCRPlus.com provides diagnostic tools, compliance intelligence, documentation generators, and remediation workflows. The platform does not submit registrations directly to The Campaign Registry (TCR) on your behalf — submissions are completed through your Communications Service Provider (CSP), which for the purposes of this guide is Plivo.
⚠ MyTCRPlus.com is a compliance tooling and education platform, not a legal services provider. All guidance reflects established TCPA requirements and carrier best practices. Consult qualified legal counsel for advice specific to your business, use case, and jurisdiction.
Table of Contents
Section 1: Understanding the A2P SMS Compliance Ecosystem
1.1 What Is A2P SMS and Why Compliance Matters
Application-to-Person (A2P) SMS refers to any text message sent from a software application or business platform to a mobile phone. This includes marketing messages, order confirmations, appointment reminders, two-factor authentication codes, and any other business-initiated text communication.
Since February 2025, all A2P traffic sent over US carrier networks — including traffic routed through Plivo — requires registration with The Campaign Registry (TCR). Unregistered messages are blocked or filtered. Compliance is not optional.
1.2 The Three-Tier Registration Architecture
A2P SMS compliance in the United States operates through a three-tier structure. Understanding each tier is essential before using any MyTCRPlus tools.
| Tier | Entity | Role in Your Registration |
|---|---|---|
| Tier 1 | The Campaign Registry (TCR) | Central authority. Stores brand and campaign records. Issues approvals and trust scores. |
| Tier 2 | Plivo (Your CSP) | Communications Service Provider. Submits your brand and campaign to TCR on your behalf. Routes approved traffic to carriers. |
| Tier 3 | Carriers (AT&T, T-Mobile, Verizon) | Final delivery networks. Enforce campaign approvals, trust score thresholds, and content filters. |
✓ MyTCRPlus.com tools operate between you and Plivo. They help you prepare accurate, complete registration packages, diagnose rejections, generate compliant documentation, and monitor ongoing campaign health — all before and after Plivo submits to TCR.
1.3 What MyTCRPlus.com Tools Do for Plivo Customers
MyTCRPlus.com provides 16 compliance tools organized across three functional pillars:
- Diagnostic Tools: Identify registration readiness gaps, existing error codes, trust score factors, and website compliance issues before submission.
- Documentation Generators: Produce compliant consent language, privacy policy SMS sections, sample messages, and verbal opt-in scripts matched to your specific use case.
- Remediation Workflows: Provide step-by-step fix instructions for every TCR rejection code, with success probability indicators and resubmission checklists.
The recommended workflow for Plivo customers using MyTCRPlus:
| Step | MyTCRPlus Tool | Action | Then In Plivo |
|---|---|---|---|
| 1 | Symptom Checker (newclient) | Diagnose readiness before first submission | Do not submit yet |
| 2 | Brand Readiness Audit | Verify website, EIN, DUNS, SSL | Fix all flagged items |
| 3 | AI Document Generator (aio) | Generate consent forms, privacy policy, sample messages | Upload to your opt-in pages |
| 4 | Use Case Selector | Choose correct TCR use case category | Enter use case in Plivo dashboard |
| 5 | Brand Registration via Plivo | Submit via mytcrplus.com guidance | Plivo submits to TCR |
| 6 | Campaign Builder Guide | Build compliant campaign with samples | Plivo submits campaign to TCR |
| 7 | Rejection Remediation Tool | Fix any rejection codes received | Resubmit through Plivo |
| 8 | Campaign Health Monitor | Ongoing opt-out rate, volume, trust score monitoring | Adjust messaging accordingly |
Section 2: Pre-Registration Readiness — Before You Submit to Plivo
2.1 Running the MyTCRPlus Symptom Checker
Before initiating any brand or campaign registration in Plivo, run the MyTCRPlus Symptom Checker at newclient.mytcrplus.com. This 60-second diagnostic tool identifies the most common registration failure points before they trigger TCR rejection codes.
How to Use the Symptom Checker
- Navigate to: newclient.mytcrplus.com
- Enter your business website URL, legal business name, and EIN (Employer Identification Number).
- Select your intended message type from the dropdown (promotional, transactional, 2FA, appointment reminders, etc.).
- The tool runs automated checks across five readiness domains and returns a diagnostic report.
- Address every flagged item before proceeding to Plivo's registration portal.
What the Symptom Checker Evaluates
| Domain | What Gets Checked | Common Failure Point |
|---|---|---|
| Website Accessibility | SSL certificate validity, HTTPS enforcement, page load, no 'Coming Soon' screens | Error 1003, 1103 |
| Business Identity | EIN verification, legal name match to domain, online presence | Error 1100, 1101 |
| Privacy Policy | SMS section present, third-party sharing language, data retention statement | Error 9108 |
| Opt-In Documentation | Consent form present, unchecked checkbox, five required consent elements | Error 2100, 2101 |
| Use Case Alignment | Intended message type matches available TCR use cases | Error 9001, 2003 |
2.2 Building Your Trust Score Before Registration
TCR assigns every registered brand a trust score on a scale of 0–100. This score directly governs your message throughput on T-Mobile and influences approval speed on AT&T and Verizon. Low trust scores result in reduced sending capacity, slower approvals, and higher rejection risk.
⚠ New businesses with no digital footprint (no website, no DUNS, no reviews, no social presence) face significantly higher rejection rates. MyTCRPlus recommends completing trust score building steps before submitting any registration.
Trust Score Optimization — Action Timeline
| Timeframe | Action | Estimated Score Impact |
|---|---|---|
| Day 1 | Register EIN if not already registered | +10 points potential |
| Day 1 | Apply for DUNS number at dnb.com | +15 points after processing (~30 days) |
| Day 1 | Purchase domain, deploy website with HTTPS and privacy policy | +10 points |
| Day 1–7 | Create LinkedIn or Facebook Business Page | +5 points |
| Day 30 | Domain ages to minimum threshold | +5 additional points |
| Day 30 | Generate 3+ business reviews at 4+ stars | +5 points |
| Day 90 | Domain reaches preferred age threshold | +3 additional points |
| Day 90 | Build review presence to 5+ reviews | +5 additional points |
✓ Established businesses with an EIN, existing website, DUNS number, and online reviews can typically register immediately. New businesses should wait 30–90 days after initial setup to allow their digital footprint to mature before submitting to TCR through Plivo.
2.3 Website Compliance Requirements
TCR reviewers visit your website as part of brand verification. Your site must meet specific requirements or your brand registration will be rejected.
Website Requirements Checklist
- HTTPS Enforced: Your website must load over HTTPS with a valid, non-expired SSL certificate. HTTP-only sites trigger Error 1103.
- No Coming Soon / Maintenance Pages: Your homepage must show actual business content. Placeholder or construction pages trigger Error 1003.
- Business Identity Visible: Your legal business name or recognized DBA must appear on the site. The domain must logically relate to your business name.
- Privacy Policy Present and Accessible: A dedicated privacy policy page must be linked from your homepage footer. Broken links or missing pages trigger Error 9108.
- SMS Section in Privacy Policy: Your privacy policy must contain a dedicated 'SMS Communications' section. This is required by T-Mobile and verified during campaign review.
- Opt-In Form Accessible: The URL where you collect SMS consent must be live, load properly over HTTPS, and display the required consent language.
2.4 Using the AI Document Generator (aio.mytcrplus.com)
The MyTCRPlus AI document generator at aio.mytcrplus.com produces compliant, carrier-ready documentation for your specific business type and use case. Generate these documents before submitting your registration to Plivo.
Documents You Can Generate
- Privacy Policy SMS Section: Produces the exact 'SMS Communications' section required by carriers, including the mandatory third-party non-sharing language.
- Website Opt-In Consent Language: Produces compliant checkbox consent text for your web forms, including all five required TCPA elements.
- Verbal Opt-In Scripts: For phone-based consent collection, produces word-for-word scripts that satisfy TCR verbal consent documentation requirements.
- Welcome / STOP / HELP Message Templates: Produces the automated response messages required for every A2P program.
- Sample Message Library: Produces 3–5 compliant sample messages for your declared use case, pre-populated with realistic variables and required opt-out language.
Using the Generator — Step by Step
- Navigate to aio.mytcrplus.com.
- Select your industry vertical (healthcare, retail, real estate, financial services, etc.).
- Select your intended use case (marketing, customer care, appointment reminders, 2FA, etc.).
- Enter your brand name, website URL, and opt-in page URL.
- Select your primary opt-in collection method (web form, verbal, SMS keyword, or point of sale).
- The generator produces all required documents in editable format.
- Review, customize with your actual brand details, and deploy to your website before submitting to Plivo.
Section 3: Brand Registration Through Plivo
3.1 What Is a Brand Registration
A brand registration establishes your business identity in The Campaign Registry. It is the first required step in A2P SMS compliance and must be completed before any campaign can be registered. Your brand record stores your legal business information, EIN, website, and receives a trust score.
Brand registrations are submitted through Plivo's console. MyTCRPlus tools help you prepare the information required and verify it before submission.
3.2 Required Information for Brand Registration
| Field | Requirement | MyTCRPlus Tool to Verify |
|---|---|---|
| Legal Business Name | Exact name as registered with IRS/Secretary of State | Symptom Checker |
| EIN (Tax ID) | 9-digit Employer Identification Number — must be valid and active | Symptom Checker |
| Business Type | LLC, Corporation, Partnership, Sole Proprietor, Non-Profit | Use Case Selector |
| Business Address | Physical registered business address — must match EIN records | Brand Readiness Audit |
| Website URL | Must be HTTPS, active, and show business content | Brand Readiness Audit |
| Industry Vertical | Select closest match from TCR list | Use Case Selector |
| Contact Email | Business domain email preferred (not Gmail/Yahoo) | Symptom Checker |
| DUNS Number | Optional but strongly recommended for trust score | Brand Readiness Audit |
✗ Sole proprietors attempting to register under a Social Security Number (SSN) instead of an EIN face terminal rejection. Apply for a free EIN at irs.gov before submitting any brand registration.
3.3 Submitting Your Brand Registration in Plivo
Step-by-Step Process in the Plivo Console
- Log in to Plivo Console: Navigate to console.plivo.com and sign in with your account credentials.
- Navigate to 10DLC Registration: In the left sidebar, select Messaging > 10DLC. Click 'Register Brand.'
- Complete the Brand Form: Enter all fields from the table above. Verify every field against your EIN registration documents before submitting.
- Verify EIN Match: The legal business name entered must exactly match the name associated with your EIN. Mismatches trigger immediate rejection.
- Add DUNS Number (Recommended): Enter your Dun & Bradstreet DUNS number if you have one. This directly improves your trust score.
- Submit Registration: Plivo submits your brand record to TCR. Processing typically takes 1–3 business days for standard registrations.
- Receive Brand ID: Upon approval, Plivo provides a Brand ID. Record this — you need it for all subsequent campaign registrations.
3.4 Understanding Brand Registration Outcomes
| Outcome | What It Means | Next Step |
|---|---|---|
| Verified | Brand approved. Trust score assigned. Ready for campaign registration. | Proceed to Section 4. |
| Unverified | EIN or identity data could not be confirmed. | Use MyTCRPlus Error Code Tool. Fix identity data and resubmit. |
| Self-Declared | Business registered but EIN not verified with IRS. Lower trust score. | Provide additional documentation to Plivo for manual escalation. |
| Rejected | Specific rejection code returned. Review error codes in Plivo notification. | Use MyTCRPlus Rejection Remediation Tool (Section 6). |
Section 4: Campaign Registration — Step-by-Step
4.1 What Is a Campaign Registration
A campaign registration defines the specific messaging program you operate under your approved brand. Each campaign is associated with one use case, a set of sample messages, opt-in documentation, and a dedicated phone number (or numbers). Campaigns must be approved by carriers before you can send A2P messages through Plivo.
A single brand can operate multiple campaigns. For example, a healthcare provider might maintain separate campaigns for appointment reminders (Customer Care use case) and patient satisfaction surveys (Low Volume Mixed use case).
4.2 Selecting the Correct Use Case with MyTCRPlus
Use case selection is the single most common source of campaign rejection. The TCR use case you declare must accurately match both your sample messages and your actual message content. Mismatches trigger Error 9001 and Error 2003.
Use the MyTCRPlus Use Case Selector tool to identify your correct use case before building your campaign in Plivo.
TCR Use Case Reference Table
| Use Case | Risk Level | Approval Time | Throughput | Correct For |
|---|---|---|---|---|
| 2FA | Low | 1–2 days | 4,500 msg/min | Login codes, security verification |
| Account Notifications | Low | 1–2 days | 4,500 msg/min | Balance alerts, account changes |
| Customer Care | Low | 1–3 days | 4,500 msg/min | Support responses, appointment reminders |
| Delivery Notifications | Low | 1–3 days | 4,500 msg/min | Order/shipping confirmations |
| Higher Education | Low | 1–3 days | Variable | Campus alerts, course notifications |
| Low Volume Mixed | Medium | 3–5 days | 60 msg/min max | Combined transactional + promotional, ≤6,000/day |
| Marketing | High | 3–7 days | Trust-score dependent | Promotional offers, product announcements |
| Political | High | 5–10 days | Manual review | Candidate/issue advocacy |
| Sweepstakes | High | 5–10 days | Manual review | Contests, prize promotions |
Use Case Decision Guide — Common Mistakes
| If Your Message Says... | Correct Use Case | Common Mistake to Avoid |
|---|---|---|
| "Your login code is 847392" | 2FA | Do not use Customer Care — 2FA has higher throughput and faster approval |
| "Your account balance is $50.23" | Account Notifications | Do not use Customer Care — separate use case for financial notifications |
| "Your order shipped. Track: [URL]" | Delivery Notifications | Do not use Marketing — this is transactional, not promotional |
| "FLASH SALE: 40% off today only" | Marketing | Do not use Customer Care — promotional content requires Marketing use case |
| "Your appointment is Tuesday at 2pm" | Customer Care | Do not use Marketing — appointment reminders are not promotional |
| "Rate your recent experience" | Low Volume Mixed | Do not use Customer Care for surveys that may combine promotional follow-ups |
✓ Start with 2FA or Customer Care to establish positive messaging history before registering Marketing campaigns. Carriers apply less scrutiny to Marketing campaign approvals after 90+ days of compliant transactional history.
4.3 Building Your Campaign Description
The campaign description is reviewed by TCR and carrier compliance teams. An unclear or mismatched description is the second most common source of campaign rejection (Error 2002, 2003).
Campaign Description Formula
✓ [Brand Name] sends [specific message types] to [audience description] for [business purpose]. Minimum 40 characters. Maximum 300 characters.
Compliant Campaign Description Examples
| Use Case | Compliant Description Example |
|---|---|
| Marketing | SpringClean Co sends promotional offers, seasonal discounts, and service announcements to opted-in customers who have subscribed to receive marketing communications for e-commerce marketing purposes. |
| Customer Care | GreenLeaf Dental sends appointment reminders, confirmations, and rescheduling notifications to patients who have provided consent to receive healthcare communications. |
| Account Notifications | ABC Bank sends account balance alerts, transaction notifications, and fraud warnings to customers who have enrolled in the bank's SMS notification program. |
| 2FA | SecureApp sends one-time passcodes and security verification codes to registered users for account authentication and login verification purposes. |
4.4 Writing Compliant Sample Messages
Every campaign registration requires three sample messages. These messages must be realistic, compliant, and accurately represent the content you will actually send. TCR reviewers read and evaluate every sample message.
Seven Required Elements — Every Sample Message
- Brand Name: Legal business name or recognized DBA must appear first or within the first 10 characters.
- Opt-Out Language: "Reply STOP to opt out" or "Text STOP to unsubscribe" — present in every single sample.
- Realistic Variables: No placeholder text like [NAME] or {ORDER_ID}. Populate with real example values.
- No URL Shorteners: Bit.ly, TinyURL, and similar shorteners trigger security flags. Use your full branded domain.
- Use Case Alignment: Marketing samples must contain promotional language. Transactional samples must not contain promotional content.
- 'Msg & data rates may apply': Include in every sample message.
- Realistic Message Length: Character count must reflect actual production messages. Artificially short samples flag as incomplete.
Compliant Sample Message Examples
Marketing Use Case
✓ SpringClean Co: FLASH SALE — 40% off all services booked this weekend. Code FLASH40 at springclean.com/book Reply STOP to unsubscribe. Msg & data rates may apply.
Customer Care — Appointment Reminder
✓ GreenLeaf Dental: Reminder — your cleaning is Wed Nov 6 at 2pm. Confirm: reply YES. Reschedule: call 555-234-5678. Reply STOP to opt out. Msg & data rates may apply.
Account Notifications
✓ ABC Bank: Your savings account ending in 1234 balance is $1,234.56 as of today. View at abcbank.com/account Reply STOP to opt out. Msg & data rates may apply.
2FA
✓ SecureApp: Your verification code is 847392. This code expires in 10 minutes. Do not share it. Need help? Visit secureapp.com/support Reply STOP to opt out.
4.5 Documenting Opt-In Consent
Consent documentation is one of the most scrutinized elements of campaign registration. Incomplete or unclear opt-in documentation accounts for approximately 22% of all campaign rejections. MyTCRPlus tools generate the exact consent language required for your opt-in method.
The Five Required Consent Elements (TCPA Mandatory)
- Brand Identification: Exact legal name or recognized DBA.
- Message Type Disclosure: Specific description of message categories (promotional vs. transactional).
- Frequency Statement: "Message frequency varies" or specific count ("up to 4 messages per month").
- Rate Disclosure: "Msg & data rates may apply" — exact phrasing required.
- Opt-Out Instruction: "Reply STOP to opt out" or equivalent — must be present in consent language.
Consent Template — Website Promotional Opt-In
✓ I consent to receive promotional text messages from [BRAND NAME] at the phone number provided. Message frequency varies (up to [X] messages per month). Message and data rates may apply. Text STOP to opt out or HELP for assistance. View our Privacy Policy at [URL] and Terms of Service at [URL]. Consent is not a condition of purchase.
Consent Collection Documentation Requirements for TCR
| Collection Method | Required Documentation | TCR Verification Requirement |
|---|---|---|
| Website Form | Screenshot showing unchecked checkbox + consent language + form URL | Screenshot + live URL |
| SMS Keyword (JOIN/START) | Welcome message template + keyword documentation | Message flow diagram |
| Verbal (Phone) | Rep script + confirmation message template | Call recording policy + written script |
| Point of Sale | Staff training materials + physical consent form image | Scanned physical form |
| Email Opt-In | Email click sequence + mobile number form screenshots | Email + landing page screenshots |
⚠ Checkboxes on opt-in forms must be unchecked by default. Pre-checked checkboxes violate TCPA consent requirements and will result in campaign rejection (Error 2100, 2101). TCR reviewers specifically test this.
4.6 Submitting Your Campaign in Plivo
Step-by-Step Campaign Submission
- Navigate to Campaign Registration: In Plivo Console, go to Messaging > 10DLC > Register Campaign.
- Select Your Brand: Choose your approved brand from the dropdown. Your Brand ID must be in Verified status.
- Select Use Case: Choose the use case identified through the MyTCRPlus Use Case Selector.
- Enter Campaign Description: Use the description formula from Section 4.3. Minimum 40 characters.
- Enter Sample Messages: Enter all three compliant sample messages. Verify all seven required elements are present in each.
- Enter Opt-In Details: Provide your opt-in URL and describe your consent collection method.
- Configure Campaign Attributes: Select whether campaign contains embedded links, embedded phone numbers, or affiliate marketing content.
- Submit Campaign: Plivo submits to TCR and carrier review. Standard campaigns typically complete review in 1–7 business days depending on use case risk level.
4.7 Assigning Phone Numbers to Your Approved Campaign
Once your campaign is approved, you must assign dedicated phone numbers before sending any messages. Numbers assigned to unapproved campaigns will have traffic filtered by carriers.
Number Assignment Process in Plivo
- Navigate to Phone Numbers: In Plivo Console, go to Phone Numbers > Your Numbers.
- Select Numbers for Campaign: Choose the 10DLC numbers (local area code numbers) you wish to assign.
- Assign to Campaign: Link each number to your approved campaign. Plivo submits the number-campaign association to TCR.
- Verify Assignment: Confirm number status shows as 'Campaign Assigned' before sending any messages.
→ Each phone number can be assigned to only one campaign at a time. If you operate multiple use cases (e.g., Marketing and Customer Care), you need separate numbers assigned to each respective campaign.
Section 5: Industry-Specific Compliance Requirements
Certain industries face additional regulatory requirements beyond standard TCR/TCPA compliance. This section covers the most common industry-specific constraints Plivo customers encounter when using MyTCRPlus tools to prepare registrations.
5.1 Healthcare and Telehealth
| Requirement | Detail |
|---|---|
| Regulatory Overlay | HIPAA + TCPA + TCR carrier review |
| BAA Required | Business Associate Agreement required with Plivo and any SMS platform handling PHI-adjacent data |
| PHI Prohibited in Messages | Patient names combined with appointment details, diagnoses, prescription information — all prohibited in SMS content |
| Recommended Use Cases | Customer Care (appointment reminders), Account Notifications (test result availability notifications) |
| Separate Marketing Consent | Marketing consent must be separate from clinical/care communication consent |
5.2 Financial Services and FinTech
| Requirement | Detail |
|---|---|
| Regulatory Overlay | TCPA + CFPB + GLBA + elevated carrier scrutiny |
| Debt Collection Limit | Maximum 3 messages per week per recipient — enforced by AT&T and Verizon |
| Legal Disclaimers | Collection messages require regulatory disclosure language |
| Crypto/NFT Status | Prohibited by AT&T. Manual review (7–14 days) at T-Mobile. Restricted at Verizon. |
| Payday Loans | Restricted across all carriers. Elevated review. Expect delays. |
| Recommended Use Cases | Account Notifications, 2FA, Customer Care |
5.3 Real Estate
| Requirement | Detail |
|---|---|
| Regulatory Overlay | TCPA + state do-not-call laws + TCR |
| Property-Specific Consent | Consent must be specific to the type of property or service. Blanket consent is insufficient. |
| Lead Nurturing | Lead nurturing sequences must use Marketing use case, not Customer Care |
| TCPA Exposure | High class-action risk — use double opt-in and maintain detailed consent records |
| Recommended Use Cases | Marketing (property alerts), Customer Care (showing confirmations) |
5.4 E-Commerce and Retail
| Requirement | Detail |
|---|---|
| Order Confirmations / Shipping | Delivery Notifications use case only. Must not include promotional content in these messages. |
| Cart Abandonment | Marketing use case required. Must have explicit marketing consent. |
| Post-Purchase Surveys | Low Volume Mixed or Customer Care use case. No promotional content in survey messages. |
| Promotional Blasts | Marketing use case. Frequency capped by trust score throughput. |
5.5 Prohibited Content — All Carriers
✗ Messages containing any of the following categories will be blocked by all carriers regardless of registration status. Sending prohibited content after TCR approval will result in campaign suspension.
| Category | T-Mobile | AT&T | Verizon | Status |
|---|---|---|---|---|
| Cannabis / CBD / Hemp | Prohibited | Prohibited | Prohibited | Blocked all carriers |
| Payday Loans / High-Interest Lending | Restricted | Restricted | Restricted | Elevated review; delays expected |
| Crypto / NFT Promotions | Restricted | Prohibited | Restricted | AT&T blocks; others restrict |
| Adult / Sexual Content | Prohibited | Prohibited | Prohibited | Blocked all carriers (SHAFT) |
| Firearms Promotion | Prohibited | Prohibited | Prohibited | Blocked all carriers (SHAFT) |
| Tobacco / Vaping | Prohibited | Prohibited | Prohibited | Blocked all carriers (SHAFT) |
| Get-Rich-Quick / Pyramid Schemes | Prohibited | Prohibited | Prohibited | Blocked all carriers |
| Debt Relief / Debt Settlement | Restricted | Restricted | Restricted | Elevated review |
Section 6: Handling Rejections with MyTCRPlus Remediation Tools
6.1 When Plivo Notifies You of a Rejection
When TCR or a carrier rejects your brand or campaign registration, Plivo delivers a notification containing one or more error codes. These codes identify the specific reason for rejection. Do not resubmit without first fully remediating every error code in the notification.
The MyTCRPlus Rejection Remediation Tool at mytcrplus.com/fix provides step-by-step fix instructions for over 179 documented error codes, with success probability indicators and resubmission checklists.
6.2 The Four-Phase Remediation Workflow
Phase 1: Diagnosis (Target: Under 1 Hour)
- Identify all error codes from the Plivo rejection notification. Copy every code — do not assume a single code.
- Classify each code as Terminal, Manual Review Required, or Auto-Remediable using the classification below.
- If any code is Terminal, stop and escalate before any resubmission. Do not resubmit without full remediation of terminal codes.
- Map each code to the fix category in mytcrplus.com/fix and plan your remediation sequence.
Error Severity Classification
| Severity | Meaning | Examples | Action Required |
|---|---|---|---|
| TERMINAL | Cannot auto-remediate. Full business verification or use case change required. | Invalid EIN, dissolved entity, SHAFT content, sole proprietor without EIN | Stop. Escalate to Plivo support. Full remediation before any resubmission. |
| MANUAL REVIEW | Elevated scrutiny. May resolve with supporting documentation. | Trust score <25, financial services, healthcare, political campaigns | Prepare comprehensive supporting documentation. Submit through Plivo escalation path. |
| AUTO-REMEDIABLE | Same-day fix available. Specific documentation or content change required. | Missing opt-out language, SSL error, missing brand name in verbal script | Fix immediately. Resubmit same business day after correction. |
6.3 Most Common Error Codes and Fixes
Brand-Level Errors
| Error Code | Name | Cause | Fix Summary | Fix Time |
|---|---|---|---|---|
| 1003 | Website Inaccessible | Site down, maintenance mode, 'Coming Soon' page | Restore live website with actual business content | 2–4 hrs |
| 1100 | Online Presence Missing | No website or social media profile found | Deploy website or create LinkedIn/Facebook Business Page | 1–3 days |
| 1101 | URL Domain Mismatch | EIN entity name does not match domain | Add DBA footer: '© [Brand]. DBA of [Legal Entity] LLC.' Domain must match. | 1–2 days |
| 1103 | SSL Failed | HTTP-only site, self-signed or expired certificate | Install valid SSL certificate, enforce HTTPS redirect | 1–4 hrs |
Campaign Description Errors
| Error Code | Name | Rejection Rate | Fix Required |
|---|---|---|---|
| 2001 | Duplicate Registration | 5% | Deactivate prior campaign with identical description before resubmitting |
| 2002 | Description Unclear | 15% | Apply: '[Brand] sends [type] to [audience] for [purpose].' Minimum 40 characters. |
| 2003 | Description Mismatches Use Case | 20% | Rewrite description to match declared use case OR change use case to match description |
| 2004 | Description Mismatches Samples | 18% | Align sample messages with campaign description — all must describe the same program |
| 9001 | Use Case Mismatch | Variable | Either change use case to match content OR rewrite samples to match declared use case |
Opt-In and Consent Errors
| Error Code | Name | Rejection Rate | Fix Required |
|---|---|---|---|
| 2100 | No Opt-In Method Documented | 22% | Provide screenshot of web form with checkbox, URL, and consent language visible |
| 2101 | Marketing Missing Written Consent | 18% | Provide web form screenshot showing unchecked checkbox and all five TCPA consent elements |
| 2105 | Verbal Script Text Missing | 5% | Provide complete verbal script including brand name, STOP instruction, and privacy URL |
| 9607 | Consent Verification Problem | Variable | Screenshot + verbatim consent text + URL + timestamp proof — all required |
Sample Message Errors
| Error Code | Name | Rejection Rate | Fix Required |
|---|---|---|---|
| 9106 | Missing Opt-Out Language | 15% | Add 'Reply STOP to opt out' to all three sample messages. Resubmit same day. |
| 9108 | Privacy Policy Non-Compliant | 12% | Add 'SMS Communications' section to privacy policy. Include exact non-sharing language. |
6.4 The Required Privacy Policy SMS Section
Error 9108 is one of the most common campaign rejection triggers. Your privacy policy must contain a dedicated SMS section with the following exact language elements. Use the MyTCRPlus AI Document Generator to produce this section automatically.
Required Privacy Policy SMS Section Content
✓ SMS COMMUNICATIONS SMS DATA COLLECTION: We collect mobile phone numbers and SMS consent records when you opt in to our text message program. DATA USE: Phone numbers and SMS consent are used solely to send messages you have requested. SMS consent and phone numbers are NOT shared with third parties or affiliates for their marketing purposes. DATA RETENTION: Consent records are retained for a minimum of 4 years from the date of collection or date of opt-out, whichever is later. USER RIGHTS: You may request access to or deletion of your SMS consent record by contacting us at [EMAIL]. Opt out from all messages at any time by texting STOP. SUPPORTED KEYWORDS: STOP — Unsubscribe. START — Resubscribe. HELP — Support contact information.
✗ The phrase 'SMS consent and phone numbers are not shared with third parties' is required verbatim by T-Mobile carrier policy. Paraphrasing or omitting this exact language will cause campaign rejection on re-review.
6.5 Resubmission Preparation Checklist
Before resubmitting through Plivo after any rejection, verify every item in this checklist. Incomplete resubmissions result in repeat rejections and extended delays.
- Updated Sample Messages: All three samples contain brand name, opt-out language, realistic variables (no placeholders), full domain URLs, and use-case-aligned content.
- Consent Documentation: Screenshot of opt-in form with unchecked checkbox visible, verbatim consent language, and live opt-in URL provided.
- Privacy Policy URL: Functioning URL, SMS section present, non-sharing language exact, section header reads 'SMS Communications.'
- Business Verification: If brand-level rejection — legal name matches EIN, domain matches entity, HTTPS enforced, website accessible.
- Use Case Alignment: Campaign description, sample messages, and declared use case all describe the same messaging program.
6.6 Carrier Appeal Process
If your resubmission is rejected a second time, you may initiate a carrier escalation appeal. MyTCRPlus provides appeal email templates and escalation guidance. Appeals submitted through Plivo's CSP escalation channel typically receive responses within 3–5 business days.
Appeal Email Structure
→ Subject: URGENT: TCR Campaign Rejection — Business Impact Brand ID: [Your Brand ID] Campaign ID: [Your Campaign ID] Rejection Code(s): [ERROR CODES] Business Impact: [Daily message volume × revenue impact per day delayed] Previous Submission Attempts: [Count] Remediation Completed: [Specific actions taken, with dates] Request: Expedited review and direct carrier escalation
Section 7: Ongoing Campaign Administration and Compliance Operations
7.1 Campaign Health Monitoring — Key Metrics
Approved campaign status is not permanent. Carriers continuously monitor active campaigns for compliance signals. Metric thresholds that trigger carrier enforcement action are documented below. MyTCRPlus campaign monitoring tools track these signals and alert you before enforcement occurs.
| Metric | Safe Zone | Warning Threshold | Enforcement Trigger | Carrier Action |
|---|---|---|---|---|
| Opt-Out Rate | <1% | 1–5% | >5% | Manual review + score reduction |
| Spam Complaints | <0.05% | 0.05–0.1% | >0.1% | Throttling (T-Mobile, Verizon) |
| Volume Spike (24hr) | <100% | 100–300% increase | >300% increase | Auto-suspension (Verizon) |
| STOP Response Time | <5 sec | 5–30 sec | >30 sec | Carrier compliance notice |
7.2 STOP / HELP / START Keyword Compliance
Federal law and carrier policy require that you process opt-out keywords within 5 seconds and cease all further messaging to opted-out numbers immediately. Failure to honor opt-outs is one of the most serious compliance violations in A2P SMS.
Required Keyword Processing
| Keyword Received | Action Required | Response Message Required |
|---|---|---|
| STOP, END, CANCEL, UNSUBSCRIBE, QUIT | Immediately add number to suppression list. Cease all messages. | Send opt-out confirmation message. No further messages. |
| HELP | No list change. Send support contact information. | Send HELP response with phone number and website URL. |
| START, UNSTOP, YES | Remove from suppression list if re-subscribing. | Send re-subscribe confirmation with program details. |
Required Keyword Response Templates
STOP Response — Opt-Out Confirmation
✓ [BRAND NAME]: You've been unsubscribed. No further messages will be sent. Reply START to resubscribe. Questions? Call [PHONE] or visit [URL].
HELP Response
✓ [BRAND NAME] SMS Support: For assistance call [PHONE] or visit [URL]. Reply STOP to unsubscribe. Msg & data rates may apply.
START Response — Re-Subscribe Confirmation
✓ [BRAND NAME]: You've resubscribed to receive [message types]. Reply STOP anytime to opt out. Msg & data rates may apply.
7.3 Maintaining Your Opt-In List
Your subscriber list is a regulated asset. Maintaining compliant list hygiene is required for ongoing carrier compliance and TCPA litigation protection.
List Management Requirements
- Suppress Opted-Out Numbers Immediately: Numbers that send STOP must be added to your suppression list within seconds. Configure Plivo's opt-out handling to automatically update your list.
- Never Send to Purchased Lists: Purchased or rented phone number lists do not contain valid A2P SMS consent. Sending to them constitutes TCPA violation.
- Validate Numbers Before Adding: Use phone number validation to confirm numbers are active mobile lines before adding to lists.
- Retain Consent Records for 4+ Years: TCPA statute of limitations requires maintaining consent records for a minimum of four years from collection date or opt-out date, whichever is later.
- Honor Do-Not-Call Registry: Maintain a scrubbed suppression list against national and state DNC registries for any outbound marketing programs.
7.4 Throughput Management by Trust Score
Your message throughput — the volume of messages you can send per minute — is governed by your TCR trust score. Understanding your throughput limits prevents volume spikes that trigger auto-suspension.
T-Mobile Throughput Tiers
| Trust Score | Throughput Limit | Recommended Max Daily Volume |
|---|---|---|
| High Trust (>75) | 60–225 messages per minute per campaign | Up to ~300,000 per day with multiple numbers |
| Medium Trust (50–75) | 30–60 messages per minute per campaign | Up to ~80,000 per day with multiple numbers |
| Low Trust (<50) | 6 messages per minute per campaign | Up to ~8,000 per day with multiple numbers |
✓ If you need higher throughput than your trust score allows, use multiple 10DLC numbers assigned to the same campaign. Each number operates its own throughput allocation.
7.5 Managing Multiple Campaigns
Most Plivo customers operating SMS programs at scale maintain multiple campaigns to separate use cases, protect compliant campaigns from any enforcement action on higher-risk programs, and optimize throughput allocation.
Multi-Campaign Architecture Best Practices
- Separate by Use Case: Never mix marketing content with transactional messages in a single campaign. Maintain dedicated campaigns for each registered use case.
- Separate by Audience Segment: If different audience segments have different consent types, maintain separate campaigns with separate opt-in documentation for each.
- Separate by Risk Profile: High-scrutiny programs (financial services, debt collection) should be isolated from standard transactional campaigns to prevent enforcement spillover.
- Number Isolation: Assign dedicated phone numbers to each campaign. Do not share numbers across campaigns with different use cases.
7.6 Campaign Modification and Re-Registration
Significant changes to your messaging program may require campaign modification or re-registration. Making major content changes without updating your campaign registration is a compliance violation.
When to Update Your Campaign Registration
| Change Type | Action Required | Process |
|---|---|---|
| Adding a new message type (e.g., adding promotional messages to a transactional campaign) | Re-register or add new campaign | Register new campaign with correct use case through Plivo |
| Changing opt-in URL | Update campaign in Plivo | Submit updated opt-in URL and documentation |
| Changing brand name / DBA | Update brand registration | Submit updated brand information through Plivo |
| Minor message content changes (same type, same use case) | No action required | Content evolution within registered use case is permitted |
| Adding new phone numbers to existing campaign | Assign in Plivo | Link new numbers to approved campaign in Plivo Console |
Section 8: 2025 Carrier Policy Compliance Reference
Carrier policies governing A2P SMS traffic are actively enforced and updated throughout the year. This section reflects enforcement postures as of 2025. Use MyTCRPlus carrier policy monitoring tools to receive alerts when policies change.
8.1 T-Mobile Active Enforcement Policies
| Policy | Effective Date | Severity | Threshold / Requirement |
|---|---|---|---|
| SHAFT ML Enforcement | Nov 5, 2024 | CRITICAL | Real-time AI blocking of prohibited content categories. No warnings. |
| DUNS Verification Mandate | Sep 1, 2024 | High | Required for all new brand registrations. Missing DUNS reduces trust score. |
| Opt-Out Keyword Processing | Aug 20, 2024 | High | <5 second processing required for all opt-out keywords. |
| Volume Monitoring | Ongoing | Medium | Opt-out rate >5% triggers manual review and score reduction. |
| Spam Complaint Threshold | Ongoing | Medium | >0.1% spam complaints triggers throttling. |
| Trust Score Sharing | Jun 1, 2024 | High | Low trust scores on T-Mobile affect registration speed on AT&T and Verizon. |
8.2 AT&T Active Enforcement Policies
| Policy | Effective Date | Severity | Threshold / Requirement |
|---|---|---|---|
| Cryptocurrency Restrictions | Oct 28, 2024 | CRITICAL | Crypto/NFT promotions blocked outright. 7–14 day manual review for borderline cases. |
| ML Behavioral Analysis | Aug 15, 2024 | High | AI detection of suspicious volume and content patterns. Preemptive throttling. |
| Financial Services Scrutiny | Ongoing | High | Payday loans, debt relief, investment schemes flagged for elevated review. |
| Debt Collection Limits | Jul 30, 2024 | Medium | Maximum 3 messages per week per recipient. Legal disclaimers required. |
8.3 Verizon Active Enforcement Policies
| Policy | Effective Date | Severity | Threshold / Requirement |
|---|---|---|---|
| Automated Volume Monitoring | Oct 15, 2024 | CRITICAL | >300% volume increase in 24 hours = automatic suspension with no warning. |
| Behavioral Analysis | Ongoing | High | ML detection of unusual geographic or timing patterns. |
| Debt Collection Limits | Jul 30, 2024 | Medium | Maximum 3 messages per week per recipient, same as AT&T. |
| Trust Score Sharing | Jun 1, 2024 | High | Low score on Verizon affects registration and approval on T-Mobile and AT&T. |
⚠ Verizon's 300% volume spike auto-suspension is triggered without any warning. If you plan a large campaign send, spread volume across multiple days or use multiple numbers. Never increase daily volume by more than 200% in a 24-hour window.
Section 9: MyTCRPlus Tool Directory for Plivo Customers
The following tools are available at mytcrplus.com to support your complete A2P SMS compliance workflow. Each tool addresses a specific phase of the registration and administration lifecycle.
| Tool | URL | What It Does | When to Use |
|---|---|---|---|
| Symptom Checker | newclient.mytcrplus.com | 60-second registration readiness diagnostic. Identifies failure points before TCR submission. | Before first Plivo submission |
| Error Code Fix Directory | mytcrplus.com/fix | Step-by-step remediation for 179+ TCR rejection codes with success probability indicators. | After any rejection notification |
| AI Document Generator | aio.mytcrplus.com | Produces compliant privacy policy SMS sections, consent forms, sample messages, and verbal scripts. | Before submission and after rejections |
| Use Case Selector | mytcrplus.com/tools | Decision tree for identifying the correct TCR use case for your specific messaging program. | During campaign planning |
| Brand Readiness Audit | mytcrplus.com/tools | Automated website, SSL, privacy policy, and opt-in form compliance check. | Before brand registration |
| Trust Score Estimator | mytcrplus.com/tools | Estimates your current trust score range and recommends improvement actions. | During pre-registration planning |
| Sample Message Validator | mytcrplus.com/tools | Checks sample messages for all seven required elements before submission. | Before campaign submission |
| Carrier Policy Tracker | mytcrplus.com/tools | Current AT&T, T-Mobile, and Verizon policy enforcement status and recent changes. | Ongoing compliance monitoring |
| Consent Language Builder | mytcrplus.com/tools | Produces TCPA-compliant consent language matched to your opt-in method and use case. | Before deploying opt-in forms |
| Rejection Remediation Tool | mytcrplus.com/fix | 37+ error codes with step-by-step workflows, success probability, and resubmission checklist. | After campaign rejection |
Section 10: Quick Reference — Compliance Checklists
10.1 Pre-Registration Master Checklist
- Business Identity: EIN registered, legal name confirmed, DUNS number applied for.
- Website: HTTPS enforced, live business content, privacy policy linked in footer.
- Privacy Policy: 'SMS Communications' section present with non-sharing language.
- Opt-In Form: Unchecked checkbox by default, all five TCPA consent elements visible, form URL live over HTTPS.
- Online Presence: LinkedIn or Facebook Business Page created and live.
- Use Case Selected: Correct TCR use case identified via MyTCRPlus Use Case Selector.
- Sample Messages Ready: Three compliant messages prepared with all seven required elements.
- Welcome / STOP / HELP Templates: Automated response messages configured in Plivo.
10.2 Sample Message Pre-Submission Checklist
- Brand name present in first 10 characters of every message.
- 'Reply STOP to opt out' present in every single sample message.
- No URL shorteners — full branded domain only.
- Realistic variable values — no [PLACEHOLDER] text.
- Character count realistic — not artificially truncated.
- No SHAFT or prohibited content — verified against prohibited categories.
- Message type matches use case — promotional content only in Marketing campaigns.
- 'Msg & data rates may apply' included in every sample.
10.3 Post-Rejection Resubmission Checklist
- All error codes identified and classified (terminal / manual / auto-remediable).
- Every error code remediated before any resubmission.
- Sample messages updated with all required elements.
- Opt-in form screenshot shows unchecked checkbox and consent language.
- Privacy policy SMS section updated with required language.
- Business verification documents prepared if brand-level rejection.
- Use case aligned with campaign description and sample messages.
10.4 Ongoing Campaign Health Checklist
- Monitor opt-out rate — alert if approaching 3%.
- Monitor spam complaint rate — alert if approaching 0.08%.
- STOP keywords processed within 5 seconds.
- Suppression list updated immediately on opt-out receipt.
- No volume spikes >200% in any 24-hour window.
- All sends use registered campaign numbers only.
- No prohibited content in any production messages.
- Consent records maintained with timestamps, IPs, and verbatim language.
Legal Disclaimer and Platform Notices
MyTCRPlus.com provides compliance tooling, documentation generation, educational content, and error code remediation workflows based on established TCPA requirements, TCR registration standards, and carrier best practices.
MyTCRPlus.com does not provide legal advice. All guidance in this document and on the MyTCRPlus platform reflects industry practices and regulatory standards as documented at the time of publication. Compliance requirements, carrier policies, and TCR standards change frequently.
Organizations should consult qualified legal counsel to ensure their SMS programs meet specific business, use case, and jurisdictional requirements. Compliance outcomes depend on implementation quality, carrier-specific review decisions, and evolving regulatory interpretations outside the control of MyTCRPlus.com.
⚠ This guide is intended for use by Plivo customers operating A2P SMS programs in the United States. International SMS regulations vary significantly by jurisdiction and are not addressed in this document.
For the most current information on TCR requirements, carrier policies, and compliance standards, use the MyTCRPlus Carrier Policy Tracker and check mytcrplus.com/resources for updated guidance.
mytcrplus.com | newclient.mytcrplus.com | aio.mytcrplus.com | mytcrplus.com/fix