RingCentral A2P 10DLC Guide

Legal Disclaimer & Scope

This document provides procedural guidance for RingCentral customers using MyTCRPlus.com tools to complete 10-Digit Long Code (10DLC) Application-to-Person (A2P) SMS registration through The Campaign Registry (TCR). It does not constitute legal advice. Compliance obligations vary based on business model, use case, message content, industry vertical, and recipient jurisdiction.

RingCentral, TCR, T-Mobile, AT&T, and Verizon retain full discretion over registration approval decisions. Registration approval is not guaranteed by following the steps in this guide. Rejection for prohibited content carries no appeals path within the RingCentral system. Organizations should engage qualified legal counsel for advice specific to their Telephone Consumer Protection Act (TCPA), Cellular Telecommunications Industry Association (CTIA), and carrier-specific compliance obligations.

MyTCRPlus.com is designed to help customers achieve 10DLC compliance and carrier policy adherence. MyTCRPlus.com does not provide legal advisory services or regulatory representation.

Section 1: Regulatory Overview

1.1 What Is 10DLC and Why It Applies to RingCentral Customers

10-Digit Long Code (10DLC) is the U.S. wireless industry framework governing Application-to-Person (A2P) messaging sent from standard local phone numbers. Any RingCentral local number used to send business text messages — including appointment reminders, marketing promotions, customer service notifications, and two-factor authentication codes — falls under the 10DLC mandate.

The Cellular Telecommunications Industry Association (CTIA) authorized The Campaign Registry (TCR) to manage brand vetting and campaign registration for all A2P traffic. T-Mobile, AT&T, and Verizon enforce registration requirements at the network level. As of February 2025, unregistered outbound SMS from local numbers is blocked by all three major U.S. carriers without exception.

1.2 RingCentral's Role in the Registration Ecosystem

RingCentral functions as the interface between your business and TCR. When you complete the SMS Registration form in the Admin Portal, RingCentral forwards your brand identity (EIN, legal name, domain, contact information) and campaign details (use case, sample messages, consent methodology, keyword responses) to TCR for vetting. TCR assigns a trust score that determines message throughput limits and influences approval timelines.

RingCentral also enforces its own SMS/MMS Content Policy in addition to TCR and carrier requirements. Businesses engaging in prohibited activities face registration denial with no path forward and no appeals process. Review RingCentral's content policy at ringcentral.com/legal/sms-mms-content-policies.html before beginning registration.

1.3 TCR Trust Score Framework

TCR assigns a trust score from 0 to 100 based on external verification of your business credentials, online presence, domain age, and reputation signals. This score determines message throughput per phone number per approved campaign. Scores below 50 trigger manual carrier review, extending approval timelines by 7–10 business days.

1.4 TCPA Consent Requirements

The Telephone Consumer Protection Act (TCPA), codified at 47 U.S.C. § 227, governs automated and bulk text messaging to U.S. phone numbers. TCPA penalties range from $500 per violation for standard violations to $1,500 per willful or knowing violation, with class-action exposure reaching millions in aggregate. Express written consent is required for marketing messages. Conversational and informational messages require express verbal or written consent.

All consent records must capture the phone number, timestamp with timezone, opt-in source, IP address where applicable, the exact consent language version presented, and the affirmative action taken by the subscriber. RingCentral requires this documentation as part of the registration process and carriers may audit records post-approval.

1.5 SHAFT Content Prohibitions

The following content categories are prohibited across all carrier networks and result in permanent registration denial with no appeals path when identified in brand or campaign information:

Section 2: MyTCRPlus.com Tool Suite for RingCentral Customers

MyTCRPlus.com provides a diagnostic-first compliance infrastructure designed to optimize RingCentral A2P 10DLC registration outcomes before submission. Using these tools before accessing the RingCentral Admin Portal significantly reduces the risk of rejection and the associated resubmission costs, delays, and administrative burden.

All MyTCRPlus tools are accessible at mytcrplus.com/home/tcr-tools/. The following table maps each tool to its role in the RingCentral registration and ongoing administration workflow.

2.1 How MyTCRPlus Tools Integrate with RingCentral Registration

RingCentral's registration process accepts only finalized, validated information. There is no draft-and-save function that allows iterative refinement inside the Admin Portal without triggering review. Every submission, including resubmissions after rejection, is subject to vetting fees. MyTCRPlus tools function as the preparation layer — validating all inputs before they enter the RingCentral system.

The workflow follows a sequential pattern: validate brand identity through the Brand Consistency Checker, assess trust score trajectory through the Preflight Simulator, select the correct use case through the Use Case Selector, validate sample messages through the SMS Message Validator, and verify RingCentral-specific requirements through the Provider Checklist. Only after all tools produce passing scores should you proceed to the Admin Portal.

Section 3: Pre-Registration Preparation

Phase 1 is the most consequential stage of the registration process. Every input validated here directly determines whether your brand and campaign submissions pass or fail in the RingCentral Admin Portal. Completing all steps before accessing the Admin Portal is the primary mechanism for achieving first-submission approval.

Step 1.1 — Gather Required Documentation

Assemble all required documentation before beginning any MyTCRPlus diagnostic tool. The following information is needed for both the MyTCRPlus tools and the RingCentral Admin Portal registration form.

Step 1.2 — Run the Brand Consistency Checker

Navigate to mytcrplus.com/home/tcr-tools/ and select Brand Consistency Checker. This tool verifies that your business name, EIN, domain, and physical address align across IRS records, Dun & Bradstreet data, state business filings, and domain registration records. TCR cross-references all of these sources during vetting. Mismatches are the leading cause of trust score degradation and brand registration failure.

Enter your legal business name, EIN, business address, and domain URL exactly as they appear on your IRS documentation. The tool evaluates five alignment dimensions and returns a score from 0 to 100. A score of 80 or higher is required before proceeding. Scores below 80 indicate specific mismatches that must be resolved before submitting to RingCentral.

Common issues flagged by the Brand Consistency Checker and their resolutions:

Step 1.3 — Run the Trust Score Preflight Simulator

Navigate to the Trust Score Preflight Simulator at mytcrplus.com/home/tcr-tools/. The simulator evaluates 15 inputs across five dimensions to predict the trust score TCR is likely to assign your brand. These five dimensions and their weights are:

Interpret your simulator score as follows and take the corresponding action before proceeding:

Step 1.4 — Validate Website and Privacy Policy Compliance

RingCentral requires a working, publicly accessible website containing specific SMS compliance documentation. This is not optional — TCR reviewers access your website directly during the vetting process. Inaccessible websites or missing privacy policy elements are among the top causes of registration rejection (error codes 9108, 9110, 1003, 807).

Privacy Policy Requirements

Your privacy policy must be easily accessible, prominently displayed, and must contain all of the following elements. The privacy policy must be linked from the footer of every page of your website, from any web form that collects phone numbers, and directly accessible from your home page or Contact Us page.

• A statement of what personal information is collected, how it is used, and how it is shared.
• An explicit statement that SMS consent and phone numbers are not shared with third parties or affiliates for marketing purposes.
• SMS-specific disclosures covering message types, frequency, opt-out mechanism, and contact for support.

Required SMS disclosure language within your privacy policy (customize bracketed fields):

If you consent to receive SMS from [Business Name], you agree to receive [types of messages — must match your selected use case] SMS from us. Reply STOP to opt-out; Reply HELP for support; Message & data rates may apply; Messaging frequency may vary. Visit [privacy policy URL] to see our privacy policy and terms and conditions.

SMS Terms of Service Requirements

Your Terms of Service must be included within the privacy policy or as a standalone page. Required elements:

• Description of the types of messages recipients can expect to receive (must align with your selected use case)
• Statement: "Messaging frequency may vary."
• Statement: "Message and data rates may apply."
• Opt-out instruction: "You can opt out at any time by texting STOP."
• Support instruction: "For assistance, text HELP or visit our [Privacy Policy URL] and [Terms of Service URL]."

Website Contact Form Requirements (if collecting SMS consent via web form)

If your consent method includes a website form, the form must meet all of the following structural requirements. There is no flexibility on these requirements — partial compliance results in rejection.

Required website form consent language (customize bracketed fields):

By checking this box, I consent to receive [types of messages, e.g. conversational, customer care, appointment reminders, marketing] SMS from [Business Name]. Reply STOP to opt-out; Reply HELP for support; Message & data rates may apply; Messaging frequency may vary. Visit [privacy policy URL] to see our privacy policy and [Terms URL] for our Terms of Service.

Step 1.5 — Select Your Use Case with the TCR Use Case Selector

Navigate to the TCR Use Case Selector at mytcrplus.com/home/tcr-tools/. This interactive tool presents a decision tree that maps your messaging program description to the correct TCR use case category. Selecting the wrong use case is a primary cause of campaign rejection and drift violations.

RingCentral supports the following TCR use case categories. Each use case requires that all content submitted — sample messages, consent language, opt-in descriptions, and privacy policy language — consistently references that specific use case type.

Step 1.6 — Validate Sample Messages with the SMS Message Validator

RingCentral requires a minimum of two sample messages per campaign, and TCR reviewers evaluate them carefully against 12 compliance checkpoints. Navigate to the SMS Message Validator at mytcrplus.com/home/tcr-tools/ and enter each sample message you intend to submit. The tool returns a score from 0 to 100 per message with specific violation flags. A score of 85 or higher is required before submission.

The 12 validation checkpoints are:

• Brand identification: Your registered brand name or DBA name must appear in the message body.
• Opt-out language: At least one sample message must contain explicit opt-out instructions (e.g., 'Reply STOP to opt out').
• Prohibited content detection: No SHAFT content, cannabis/CBD references, get-rich-quick language, or RingCentral-prohibited categories.
• URL shortener detection: No public URL shorteners (bit.ly, tinyurl.com, etc.). Carriers block all publicly shared shortened URLs. Use full HTTPS URLs only.
• Message length: RingCentral sample messages must not exceed 160 characters. Multi-segment messages are not accepted as samples.
• Use case alignment: Message content must match the use case you are registering. A 2FA sample must contain authentication codes, not promotions.
• Consent language consistency: Message types referenced must match your consent language and Terms of Service.
• Carrier keyword conflicts: No reserved keywords used inappropriately (STOP, HELP, START, CANCEL, UNSUBSCRIBE, END).
• Phishing pattern detection: No urgent requests for personal data, account credentials, or sensitive financial information.
• Public URL verification: All URLs must be HTTPS, publicly accessible, and resolve without errors.
• Message/data rates disclosure: Include "Msg & data rates may apply" where appropriate for marketing and promotional campaigns.
• Brand name in opt-in confirmation message: If submitting an opt-in confirmation message, it must include the brand name.

Required sample message structure (adapt to your use case):

[Brand Name]: [Message content]. Reply STOP to opt out. Msg & data rates may apply.

Example for an appointment reminder use case:

Acme Dental: Reminder — your appointment is scheduled for Tuesday, March 4 at 10:00 AM. Reply STOP to opt out.

Example for a marketing use case:

City Outfitters: Members-only 20% off sale ends Sunday. Use code MEMBER20 at checkout: cityoutfitters.com/sale. Reply STOP to opt out. Msg & data rates may apply.

Step 1.7 — Run the RingCentral Provider Checklist

The Provider Checklist for RingCentral at mytcrplus.com/home/tcr-tools/ applies RingCentral-specific validation on top of standard TCR requirements. Complete this checklist after all previous steps and before accessing the Admin Portal.

RingCentral-specific requirements not present in the standard TCR framework:

• Privacy policy footer link: Must be linked from every page of the website, not only the privacy policy page or the contact form.
• Terms of Service with RingCentral-compatible language: Terms must use language that aligns with RingCentral's own content policy definitions, not just TCR's.
• Sample message 160-character limit: RingCentral does not accept multi-segment sample messages. Each sample must be 160 characters or fewer.
• Dedicated TCR support team: RingCentral routes TCR questions to a separate team from general customer support. Use 1-888-898-4591 → Option 3 → Option 1.

Section 4: Brand Registration in the RingCentral Admin Portal

Brand Registration is the first of two submission stages in the RingCentral TCR process. It establishes your organization as a verified business entity within the TCR ecosystem. All campaigns registered under your brand share the trust score assigned during this stage. A single brand registration covers all subsequent campaigns from the same legal entity.

Step 2.1 — Access the Registration Portal

Brand Registration is completed through the RingCentral Admin Portal. You must be logged in as a Super Admin or a user with SMS Registration permissions.

• Navigate to service.ringcentral.com and sign in with your administrator credentials.
• Select Admin Portal from the navigation menu.
• Navigate to Phone System > Phone Numbers > Enhanced Business SMS.
• Click SMS Registration to access the TCR registration form.
• Alternatively, access the registration form directly at service.ringcentral.com/application/company/enhancedBusinessSMS/smsTcrRegistration.

Step 2.2 — Complete the Brand Registration Form

The brand registration form collects the business identity information that RingCentral submits to TCR for vetting. Enter all fields using the exact documentation you validated in Phase 1. Any deviation from IRS records, even minor formatting differences, can reduce your trust score or trigger a failed vetting status.

Step 2.3 — Monitor Brand Registration Status

After submission, RingCentral forwards your brand information to TCR for processing. Monitor status in the Admin Portal under Phone System > Phone Numbers > Enhanced Business SMS > SMS Registration. Brand vetting typically completes within 1–3 business days, though external vetting (triggered by low trust signals) can extend to 5–7 business days.

Brand registration status definitions and required actions:

Section 5: Campaign Registration

Campaign Registration defines the specific messaging program you intend to operate under your verified brand. Each distinct use case requires a separate campaign registration. Campaign vetting is use-case-specific and is where the majority of rejections occur — TCR reviewers examine sample messages, consent methodology, keyword responses, and the consistency of all submitted information against your declared use case.

Step 3.1 — Determine Campaign Count and Structure

Register one campaign per distinct messaging use case. Do not combine incompatible use cases in a single campaign. The following examples illustrate correct campaign structuring:

Step 3.2 — Complete the Campaign Registration Form

In the Admin Portal under SMS Registration, click Create Campaign and link it to your VERIFIED brand. Complete all required fields using the validated materials from Phase 1.

Campaign Description

The campaign description is the field that TCR reviewers read most carefully. It must clearly explain who sends messages, to whom, for what purpose, and how consent is obtained. Vague or incomplete descriptions trigger rejection code 2002. Use the following formula as your foundation:

[Business Name] sends [specific message types] to [audience description] who have [opted in via specific method] to receive [purpose of messages]. Messages include [content description matching sample messages].

Example for an appointment reminder campaign at a dental practice:

Smile Dental sends appointment reminders, confirmations, and follow-up care instructions to patients who have provided written consent via intake forms at our office to receive SMS communications. Messages include appointment date/time reminders, cancellation confirmations, and post-procedure care instructions.

Example for a marketing campaign at a retail brand:

City Outfitters sends promotional offers, seasonal sales announcements, and loyalty program updates to customers who have opted in via an unchecked checkbox on our website contact form at cityoutfitters.com/contact. Messages include sale announcements, member-exclusive discount codes, and new product launches.

Campaign Attributes

The following campaign attributes must be set correctly. Incorrect attribute settings are a leading cause of rejection:

Sample Messages

Enter 2–5 sample messages. These must be identical to the messages you validated in Step 1.6 using the SMS Message Validator (score 85+). Enter each message exactly as validated — do not modify content after validation.

Consent (Call-to-Action) Documentation

The consent section of the campaign form is where you document how you obtain subscriber permission to send messages. You must select all methods that apply to your program and provide the required documentation for each. Incomplete, vague, or non-compliant CTA documentation generates codes 9103, 9104, 9607, and the 2100-series errors.

Keyword Response Messages

Enter your opt-in confirmation message, STOP/opt-out response, and HELP response. These are evaluated against strict format requirements. Missing elements are flagged by error codes 6002 through 6014 and 9606.

Opt-in/Start confirmation message requirements and example:

• Must include: brand name, message frequency disclosure, message/data rates disclosure, opt-out instructions, HELP instructions, privacy policy URL.

Thank you for opting into SMS messaging from [Brand Name]. Messaging frequency may vary. To opt out, reply STOP. For assistance, reply HELP or visit [website URL]. Privacy policy: [privacy policy URL]. Message & data rates may apply.

STOP/opt-out response requirements and example:

• Must include: brand name, confirmation of unsubscription, statement that no further messages will be sent, instructions for opting back in.

You have been unsubscribed from [Brand Name] SMS messages and will receive no further messages. To opt back in at any time, reply START.

HELP response requirements and example:

• Must include: brand name, website, email address, or phone number where recipient can reach support.

Thank you for contacting [Brand Name]. For support, visit [website URL], email [support@yourdomain.com], or call [phone number].

Step 3.3 — Submit and Monitor Campaign Status

After completing all campaign form fields, review each section for accuracy, then submit. TCR processes standard use cases within 7–10 business days. Campaigns requiring manual review (trust scores below 50, high-risk verticals, specialty use cases) take longer. Carrier-specific approvals from AT&T, T-Mobile, and Verizon are issued separately; full U.S. delivery requires all three carriers to show APPROVED status.

Monitor campaign status in the Admin Portal under SMS Registration. Campaign status definitions:

Section 6: Number Assignment and Campaign Activation

After your campaign status shows APPROVED in the Admin Portal, you must assign your RingCentral local phone numbers to the campaign. Numbers are not automatically linked to approved campaigns — this is a manual step. Sending messages from numbers not assigned to an approved campaign results in blocked delivery.

Step 4.1 — Assign Numbers to Your Campaign

• Access the Admin Portal: Navigate to service.ringcentral.com and sign in as administrator.
• Open SMS Registration: Go to Phone System > Phone Numbers > Enhanced Business SMS > SMS Registration.
• Locate the approved campaign: Find your APPROVED campaign in the campaign list and click to open its detail view.
• Assign numbers: Click Assign Numbers or Add Numbers. Select the local phone numbers you want to associate with this campaign. Numbers must already exist on your RingCentral account.
• Confirm assignment: Click Save or Confirm. Numbers are now linked to the campaign and submitted for carrier-side activation.

Step 4.2 — Carrier Activation Timelines

After you assign numbers to an approved campaign in the Admin Portal, each carrier independently activates the number-to-campaign linkage on their network. Sending messages before carrier activation completes results in blocked delivery on that carrier's network even though the campaign is marked APPROVED.

Step 4.3 — Pre-Launch Compliance Verification

Before sending any messages, verify every item in the following checklist. Run the RingCentral Provider Checklist on MyTCRPlus a second time after number assignment to confirm all configuration is correct.

Send a test message from each assigned number to your own mobile device before sending to any subscriber. Verify delivery status in the Admin Portal under Phone System > Phone Numbers > Messages. A status of Delivered confirms carrier activation is complete for that number.

Section 7: Rejection Remediation

Industry-wide first-submission rejection rates for TCR campaign registrations exceed 40%. A campaign rejection does not mean permanent disqualification — it means specific elements of your submission do not meet requirements. Systematic remediation before resubmission is required. Each resubmission triggers a new vetting process through RingCentral.

Step 5.1 — Identify and Document All Rejection Codes

Log into the Admin Portal and navigate to SMS Registration. Open the FAILED campaign and locate the rejection reason and error codes in the Status History or campaign detail view. Record all error codes before beginning remediation. Multiple codes may appear simultaneously — all must be resolved before resubmitting. Addressing one code while leaving others unresolved wastes a submission attempt.

If no specific error code is shown in the Admin Portal, contact RingCentral TCR support at 1-888-898-4591 (Option 3, Option 1) and request the raw TCR rejection response for your campaign. Provide your account number and the date of the rejection.

Step 5.2 — Use the MyTCRPlus Rejection Remediation Tool

Navigate to the Rejection Remediation Tool at mytcrplus.com/home/tcr-tools/. Enter each rejection code. The tool returns root cause analysis, step-by-step remediation instructions, and a list of required documentation for each code. Complete all remediation across all codes before proceeding to Step 5.3.

Step 5.3 — RingCentral TCR Rejection Code Reference

The following tables organize the most common RingCentral TCR rejection codes by category. Use this reference in conjunction with the MyTCRPlus Rejection Remediation Tool.

Privacy Policy and Terms of Service Codes

Consent and Opt-In Method Codes

Keyword Response Message Codes

Sample Message Codes

Website and Brand Identity Codes

Use Case Mismatch Codes

Consent Form Language Codes (2110–2121 Series)

The 2110–2121 series codes indicate that website form consent language is missing specific required elements. All codes in this series are resolved by updating the website form consent text to include the full standardized disclosure:

By checking this box, I consent to receive [message types] SMS from [Business Name]. Reply STOP to opt-out; Reply HELP for support; Message & data rates may apply; Messaging frequency may vary. Visit [privacy policy URL] to see our privacy policy and [Terms URL] for our Terms of Service.

Step 5.4 — Pre-Resubmission Validation Checklist

Before resubmitting to RingCentral, complete the following validation using MyTCRPlus tools. Do not resubmit until all checklist items show passing status. Resubmitting with unresolved issues wastes a submission attempt and compounds rejection history.

Step 5.5 — Submit the Resubmission

Navigate to the FAILED campaign in the Admin Portal under SMS Registration. Click Edit Campaign. Update all fields with the corrected information. Verify that every field containing previously rejected content has been updated. Click Submit/Resubmit to send to TCR for re-review. The resubmission enters the standard review queue and follows the same timelines as the original submission.

Section 8: Campaign Suspension and Revocation Recovery

Campaign revocation or suspension after approval is more serious than a pre-approval rejection because it indicates a violation occurred on live traffic. Suspended campaigns cannot send messages and continue to be billed until resolved. Do not attempt to route traffic through alternative numbers while a campaign is suspended — this is treated as circumvention and can result in account-level enforcement.

Step 6.1 — Immediate Response to Suspension

Upon discovering a campaign is suspended or revoked, take the following actions immediately and in sequence:

• Halt all sends: Stop all outbound messaging from numbers assigned to the suspended campaign. Do not reroute to other numbers.
• Document the suspension: Navigate to the suspended campaign in Admin Portal and capture the suspension reason, date, and any associated error codes from the Status History.
• Contact RingCentral Support: Call 1-888-898-4591 (Option 3, Option 1) or submit a support case at support.ringcentral.com/new-case.html. Request the specific suspension reason and any carrier-level enforcement details.
• Run the Rejection Remediation Tool: Enter suspension codes or descriptions at mytcrplus.com/home/tcr-tools/. Identify all root causes before taking any corrective action.

Step 6.2 — Common Suspension Triggers and Remediation

Campaign suspensions originate from three sources: TCR violation flags, carrier-level enforcement (typically from complaint rate thresholds or behavioral analysis), and TCPA legal demand escalation. The following are the most common triggers and their remediation paths:

Step 6.3 — Reinstatement Request Process

• Remediate all identified issues: Complete every corrective action identified in Steps 6.1 and 6.2. Document each action taken.
• Submit a support case to RingCentral: At support.ringcentral.com/new-case.html, include: Account number, Campaign SID or identifier, Suspension date and reason, Detailed description of corrective actions completed, Supporting documentation (updated consent records, revised templates, privacy policy updates).
• Allow 5–15 business days for review: Reinstatement decisions involve coordination between RingCentral, TCR, and the triggering carrier. Do not follow up within the first 5 business days.

Section 9: Ongoing Campaign Administration

TCR registration is not a one-time event. Approved campaigns require ongoing maintenance to remain compliant with carrier policies, TCR requirements, and TCPA obligations. The following administrative procedures are required on a scheduled basis and must be embedded in your operational calendar.

9.1 Consent Record Management

TCPA litigation carries a 4-year statute of limitations. All consent records must be retained for a minimum of 4 years from the date consent was obtained. Consent records must capture the following fields at a minimum:

• Phone number (in E.164 format: +1XXXXXXXXXX)
• Opt-in timestamp with timezone (ISO 8601 format)
• Opt-in source (website form URL, verbal script version, email script, paper form ID)
• IP address at time of consent (for web-based opt-in)
• Exact consent language version presented (verbatim text, not a reference to it)
• Affirmative action taken (checkbox checked, verbal agreement recorded, email reply documented)
• Opt-out timestamp and method (when applicable)

Revocation of consent must be processed immediately. RingCentral's opt-out management system tracks STOP keywords received on registered numbers. Review the opt-out management documentation at support.ringcentral.com/article-v2/Understanding-SMS-opt-out-management.html to confirm your account is correctly logging all opt-outs.

9.2 Monthly Message Content Audit (Campaign Drift Prevention)

Sending messages materially different from registered samples is a TCR violation called campaign drift. T-Mobile enforces this violation through a formal escalation process with fines beginning at $500 per Severity-0 violation. Conduct the following audit monthly using the MyTCRPlus SMS Message Validator:

• Export current message templates: Pull all active message templates from your messaging platform or CRM.
• Run each template through SMS Message Validator: Flag any template that scores below 85 or shows use case misalignment.
• Compare against registered samples: Verify that the core content type, message structure, and brand identification are consistent with what was submitted to TCR.
• Flag material changes: New content categories, new URL domains, significant frequency changes, or changes to message purpose all constitute material changes.
• Update campaign registration before continuing sends: If material changes are identified, navigate to Admin Portal > SMS Registration, edit the campaign, update sample messages, and submit for re-review before sending the new content.

Material changes requiring campaign re-registration before sending:

• Sending promotional content on a campaign registered for transactional use
• Adding URLs from domains not referenced in the registered samples
• Doubling or tripling message frequency from the registered baseline
• Adding new content categories (e.g., adding 2FA codes to a marketing campaign)

9.3 Quarterly Consent Record Audit

Conduct a quarterly audit of subscriber consent records to identify and remediate compliance gaps before they result in complaints or TCPA exposure:

• Pull 100-record sample: Select a random sample of 100 active subscribers.
• Verify consent record completeness: Each record must contain all required fields from Section 9.1.
• Check consent age: Consent records older than 4 years require documented re-consent before continued messaging.
• Audit suppression list: Verify that all STOP requests logged in RingCentral's opt-out management system have been honored. No suppressed number should appear in active subscriber lists.
• Document audit completion: Record audit date, sample size, issues found, and corrective actions taken. Retain documentation for at least 4 years.

9.4 Carrier Policy Monitoring

Carrier policies governing 10DLC content, fees, and enforcement change frequently. Subscribe to the MyTCRPlus Carrier Policy Updates feed at mytcrplus.com/home/tcr-resources/carrier-policy-updates/ to receive monthly summaries of T-Mobile, AT&T, and Verizon policy changes that affect RingCentral campaigns.

When a policy change affects your campaigns, assess impact and complete updates before the effective date:

• Identify affected campaigns: Review all active campaigns against the changed policy.
• Assess template violations: Run affected templates through SMS Message Validator to flag non-compliant content.
• Update before effective date: Implement template updates and, if required, update campaign registration in Admin Portal.
• Re-register if required: Some policy changes require campaign re-submission. Monitor RingCentral communications and MyTCRPlus carrier policy updates for registration requirements.

9.5 Modifying and Deleting Campaigns

RingCentral allows modification of existing campaigns through the Admin Portal. For guidance on modifying or deleting TCR registrations, refer to the RingCentral documentation at support.ringcentral.com/article-v2/Modifying-or-deleting-TCR-registration.html.

Key rules for campaign modification:

• Use case changes require a new campaign registration, not modification of an existing one.
• Material changes to sample messages require updated campaign submission and re-review.
• Adding new numbers to an existing approved campaign does not require a new campaign — add numbers through the Admin Portal under the existing campaign.
• Deactivating a campaign stops billing and removes the campaign from carrier networks. Numbers previously assigned to the campaign must be assigned to a new campaign before messaging resumes.

9.6 Opt-Out Management Operations

RingCentral provides built-in opt-out management for registered campaigns. Access the opt-out management interface through the Admin Portal. Key operational requirements:

• Honor STOP, UNSUBSCRIBE, QUIT, CANCEL, END, and STOP ALL keywords from any number registered on any of your campaigns.
• Send the STOP confirmation response immediately upon receipt — do not batch process opt-outs.
• Do not send further messages from any number associated with the campaign to opted-out subscribers.
• If a subscriber sends START, YES, or SUBSCRIBE after opting out, re-add them to the active subscriber list and send the opt-in confirmation message.
• Log every opt-in and opt-out event with timestamp, keyword received, and number. Retain logs for 4+ years.

Section 10: Troubleshooting Decision Trees

10.1 Messages Not Delivering After Campaign Approval

Work through the following decision tree in order. Stop at the first confirmed cause and apply the stated resolution.

10.2 Campaign Stuck in PENDING for More Than 7 Business Days

• Verify brand status first: Navigate to Admin Portal > SMS Registration > Brand Registration. If brand status is not VERIFIED, the campaign cannot enter active review. Resolve brand issues first.
• Check for missed rejection notification: Sometimes rejection notifications are delayed. Look in Status History for any rejection codes or status changes.
• Contact RingCentral TCR Support: Call 1-888-898-4591 (Option 3, Option 1). Provide your account number, campaign identifier, and submission date. Request an escalation of TCR status. Reference the support documentation for setting up TCR registration at support.ringcentral.com/article-v2/Setting-up-TCR-registration-assigning-numbers-to-SMS-campaigns.html.

10.3 Inbound SMS Working but Outbound SMS Blocked

This is a known RingCentral configuration pattern when outbound SMS is blocked due to an unregistered or rejected campaign while inbound processing remains active. Causes include: campaign registration not completed before sending began, campaign expired without renewal, or carrier-level outbound block triggered by complaint volume.

• Confirm campaign registration status: A campaign status of FAILED, PENDING, or REVOKED blocks outbound but may leave inbound active.
• Check if 10DLC registration deadline was missed: Accounts that did not complete registration before the carrier enforcement dates have outbound blocked. Complete registration to restore outbound.
• Contact RingCentral Support for carrier-level block details: If campaign shows APPROVED but outbound is still blocked, there may be a carrier-level enforcement flag on specific numbers. TCR support can request a carrier trace.

10.4 Trust Score Lower Than Expected

• Verify EIN/name alignment: Confirm submitted EIN matches IRS CP 575 exactly. Run Brand Consistency Checker.
• Confirm DUNS number: If no DUNS was provided, obtain from dnb.com and contact RingCentral Support to request a brand score update with DUNS documentation.
• Check domain age: Domains under 6 months are flagged as higher risk. Start with low-risk use cases to build history.
• Review online presence: Search your business name in Google. Negative reviews, no reviews, or no listing can depress trust scores.
• Request manual score review: Contact RingCentral TCR support and request a manual brand score review. Submit supporting documentation: business license, recent tax filing, bank statement showing active business operations, and any public business directory listings.

Section 11: Quick Reference

11.1 RingCentral Key Limits and Timelines

11.2 Required Documentation Checklist

11.3 RingCentral Support Contacts

11.4 MyTCRPlus Tool Access Points

11.5 Master Process Summary