MyTCRPlus.com Vonage SMS Compliance Operations Guide A2P 10DLC Registration, Campaign Administration & Ongoing SMS Compliance Prepared for Vonage Customers Version 1.0 | March 2026 mytcrplus.com | support@mytcrplus.com
Overview This guide provides step-by-step procedures for Vonage customers to use MyTCRPlus.com tools throughout the complete lifecycle of Application-to-Person (A2P) SMS operations—from initial 10-Digit Long Code (10DLC) brand and campaign registration through The Campaign Registry (TCR), to ongoing campaign administration, rejection remediation, and long-term compliance maintenance.
Vonage routes all outbound A2P SMS traffic through The Campaign Registry (TCR), the CTIA-authorized entity that vets brand identity and approves campaign use cases before carriers will deliver messages at commercial throughput. Without approved brand and campaign registration, Vonage local numbers are throttled to rates that make business messaging operationally non-viable.
Scope of This Document This guide covers: pre-submission preparation using MyTCRPlus diagnostic tools, brand registration submission in the Vonage dashboard, campaign registration including use case selection and sample message preparation, number linking, post-approval administration, rejection remediation workflows, and ongoing compliance monitoring. All Vonage SMS-capable products are addressed including Vonage API (Messages API), Vonage Business Communications, Vonage Contact Center, and Vonage Engage omnichannel solutions.
Regulatory Notice This document provides operational guidance based on established carrier requirements and industry best practices as of March 2026. It does not constitute legal advice. Organizations should consult qualified legal counsel for guidance specific to their messaging programs, industry vertical, and jurisdiction. Final carrier approval is subject to TCR vetting and individual carrier review discretion.
Section 1: Foundational Concepts 1.1 The Regulatory Framework A2P SMS messaging in the United States operates under a layered regulatory structure. The Telephone Consumer Protection Act (TCPA), 47 U.S.C. § 227, governs consent requirements and carries statutory damages of $500 per violation, rising to $1,500 per willful or knowing violation. The Cellular Telecommunications Industry Association (CTIA) publishes messaging best practices that T-Mobile, AT&T, and Verizon enforce through traffic filtering and throughput controls. TCR operates as the CTIA-authorized registry that processes brand vetting and campaign approval on behalf of the carrier ecosystem.
Vonage acts as a Campaign Service Provider (CSP) in the TCR ecosystem. When you submit a registration through the Vonage dashboard, Vonage submits that data to TCR on your behalf. TCR assigns a trust score (0–100 scale) based on business verification signals and routes campaign applications to carrier review queues. Final throughput limits and approval status are determined by TCR and individual carrier policies, not by Vonage or MyTCRPlus.
1.2 TCR Trust Score Impact on Vonage Performance Your TCR trust score directly determines the message throughput your Vonage numbers can sustain and the speed at which TCR processes your campaign applications. The following table defines the operational consequences of each score band:
| Score Range | Approval Likelihood | Throughput Limit | Review Type | Timeline |
|---|---|---|---|---|
| 75–100 | >95% | Up to 4,500 msg/min (Class A/B) | Automated | 1–3 days |
| 50–74 | 70–90% | Up to 2,400 msg/min | Automated + spot checks | 3–7 days |
| 25–49 | 40–60% | Up to 240 msg/min | Manual review required | 7–10 days |
| 0–24 | <30% | Blocked pending remediation | Manual + carrier escalation | 10+ days |
MyTCRPlus Tool: Trust Score Preflight Simulator Before submitting any brand registration in Vonage, use the Trust Score Preflight Simulator at mytcrplus.com/tcr-trust-score-preflight-simulator/ to estimate your likely TCR score. The simulator models five scoring dimensions: Business Verification (30 points), Brand Reputation (25 points), Messaging History (20 points), Use Case Alignment (15 points), and Documentation completeness (10 points). Running this simulation before submission enables you to address score-suppressing gaps before incurring TCR registration fees.
1.3 Vonage SMS Products Covered This guide addresses all Vonage products that support A2P SMS operations requiring TCR registration:
| Product | SMS Capability | TCR Registration Scope |
|---|---|---|
| Vonage API / Messages API | Programmable SMS/MMS on local numbers; high-volume API-driven traffic | Brand + Campaign registration required for all 10DLC numbers used in A2P messaging |
| Vonage Business Communications | Business SMS on local and virtual numbers | Brand + Campaign required for all local numbers used in A2P messaging |
| Vonage Contact Center | High-volume inbound/outbound SMS for contact center queues; supports number pools | Brand + Campaign required; Number Pool registration for pools exceeding standard limits |
| Vonage Engage | Omnichannel messaging including SMS; customer care conversation management | Brand + Campaign required; Customer Care use case classification typical |
Regional Availability TCR registration applies exclusively to U.S. local numbers. Toll-free numbers support outbound and inbound SMS but require a separate Toll-Free Verification process, not 10DLC/TCR registration. International SMS requires the international calling option to be enabled on your Vonage plan.
Section 2: Pre-Submission Preparation Using MyTCRPlus Tools TCR charges non-refundable registration fees for every submission: approximately $4.50 one-time for brand registration, and $10–$60 per month per campaign depending on use case. Rejection and resubmission compounds these costs. The MyTCRPlus pre-submission workflow eliminates preventable rejections before fees are incurred.
The recommended preparation sequence uses four MyTCRPlus tools in order. Complete all four before opening the Vonage dashboard registration form.
Step 1: Run the Trust Score Preflight Simulator Purpose Estimate your brand’s likely TCR trust score before submission. Trust scores below 50 trigger manual review queues, extending approval timelines by 4–7 additional business days and reducing approval probability significantly.
Access Navigate to: mytcrplus.com/tcr-trust-score-preflight-simulator/
Procedure Open the Trust Score Preflight Simulator. Complete the Business Verification section (30-point category). Enter your business formation date, EIN availability, DUNS number status, and domain age. Businesses formed less than 1 year ago or with domains under 6 months old will see score penalties in this category. Complete the Brand Reputation section (25-point category). Enter your Google Business Profile rating, number of reviews, Better Business Bureau listing status, and social media presence. A minimum 4-star average with 20+ reviews substantially improves scores. Complete the Messaging History section (20-point category). Indicate whether your business has previously registered campaigns, the volume of compliant messages sent, and whether you have documented opt-out compliance history. Complete the Use Case Alignment section (15-point category). Indicate your intended message category. Low-risk use cases (2FA/One-Time Passcodes, Account Notifications) score higher than marketing or lead generation. Complete the Documentation section (10-point category). Confirm availability of: accessible website, compliant privacy policy with SMS data sharing clause, opt-in consent mechanism, and sample messages prepared. Review the estimated score and the Improvement Opportunities list generated by the simulator. For each flagged gap, implement the remediation before proceeding to brand registration. Common remediations: obtain DUNS number before submission (+10–15 points), build Google review presence to 4+ stars, age the business domain to 6+ months if feasible, start with a lower-risk use case.
Critical: DUNS Number Impact Obtaining a DUNS number from Dun & Bradstreet before TCR brand registration is one of the highest-impact single actions available, adding an estimated 10–15 points to trust score. DUNS verification typically takes 5–30 business days. Plan accordingly if your brand registration timeline is not urgent.
Step 2: Run the Brand Consistency Checker Purpose TCR cross-references your submitted brand information against public business registrations, domain WHOIS records, Secretary of State filings, and Google Business Profile data. Inconsistencies between any of these sources and your submission generate rejection codes. The Brand Consistency Checker identifies these discrepancies before submission.
Access Navigate to: mytcrplus.com/tcr-brand-consistency-checker/
Procedure Enter your Legal Company Name exactly as it appears on your EIN/Tax ID documentation. Enter your registered business address including ZIP code. Enter your business website URL. Enter your Employer Identification Number (EIN) or Tax ID. Enter your business phone number as it appears on public listings. The checker compares these inputs against public record signals and identifies discrepancies. Common failures: DBA name submitted instead of legal entity name, address on file differs from Secretary of State records, website domain does not match entity documentation. Resolve all flagged inconsistencies before submission. Ensure the exact same legal name, address, and EIN you enter in the Vonage dashboard matches your public business registrations. If you operate under a DBA, register your legal entity name as the brand and note the DBA in the brand description field.
Vonage-Specific Requirement Vonage’s TCR submission process requires that your brand website URL is active, accessible without login, and includes business-identifying information including physical address, contact information, and description of products or services offered. The Brand Consistency Checker validates website accessibility as part of its analysis. A website that returns errors or lacks business information triggers rejection.
Step 3: Select Your TCR Use Case Purpose Use case selection is a permanent decision for each campaign. Vonage’s registration system does not allow use case changes after campaign approval. Selecting the wrong use case requires canceling the campaign, registering a new one, and paying additional fees. The TCR Use Case Selector guides you through a decision tree to identify the correct classification based on your actual message content and business operations.
Access Navigate to: mytcrplus.com/home/tcr-tools/use-case-selector/
Procedure Launch the TCR Use Case Selector tool. Answer the initial screening questions about your business type and message content. The tool presents a decision tree with branch points. Key decision nodes: Does your message request user action (purchase, click, sign-up)? Is your message triggered by a user action (appointment booked, order placed)? Is the message recipient already a customer? Does the message include promotional pricing or offers? The tool generates a use case recommendation with supporting rationale and approval probability estimate. Common use case categories for Vonage customers are defined below. Note the recommended use case and its TCR category code. You will enter this in the Vonage registration form.
The following table maps common Vonage business scenarios to TCR use case categories with their associated monthly fees and throughput expectations:
| Use Case | Typical Business Scenarios | Sample Content Types | Monthly Fee | Max Throughput |
|---|---|---|---|---|
| Two-Factor Authentication (2FA) | Login verification, account security, password reset | OTP codes, security alerts | $10/mo | Automated (high) |
| Account Notifications | Order status, shipping updates, billing alerts, system notifications | Transactional updates triggered by customer action | $10/mo | Automated |
| Customer Care | Support conversations, issue resolution, customer service follow-up | Two-way conversational messages | $10/mo | Conversational |
| Delivery Notifications | Package status, courier updates, logistics tracking | Real-time delivery status | $10/mo | Automated |
| Marketing | Promotional offers, sales campaigns, event announcements | Promotional content requiring written consent | $10/mo | Standard |
| Mixed / Marketing | Combined transactional + promotional in same program | Varied content types | $15/mo | Standard |
Prohibited Content Categories Regardless of use case selection, the following content categories are prohibited across all Vonage TCR campaigns and will result in immediate rejection or campaign revocation: cannabis/CBD/hemp products, payday loans, high-risk financial services (crypto, NFTs, hedge fund promotions), debt consolidation/relief, get-rich-quick schemes, SHAFT content (Sex, Hate, Alcohol, Firearms, Tobacco—alcohol and firearms require age-gating and prior approval), escort services, and phishing simulation without pre-authorization. Campaigns rejected for prohibited content carry no appeals process.
Step 4: Validate Your Sample Messages Purpose TCR requires a minimum of 2–3 unique sample messages per campaign (minimum 2 for most use cases, at least one per sub-use case). These messages must reflect actual messages you intend to send, comply with carrier content policies, include required opt-out language, and align with Vonage submission rules. Sample message violations are among the most common rejection triggers. The SMS Message Validator scores messages against 12 compliance dimensions before submission.
Access Navigate to: mytcrplus.com/home/tcr-tools/sample-message-validator/
Procedure Open the SMS Message Validator. Enter your first sample message in the text field. Review the compliance score (0–100) and violation flags. The validator checks: opt-out language presence (STOP keyword), sender identification (brand name in message), message frequency disclosure where required, prohibited keyword detection, character count, URL format compliance (no public URL shorteners; use branded or full URLs), and SHAFT content screening. Revise the message to address all flagged violations. Target a compliance score of 85 or higher. Historical data indicates messages scoring 85+ correlate with 90% carrier approval rates. Repeat for all sample messages. You need a minimum of 2–3 unique messages; 5 is recommended for complex use cases. Ensure each sample message is substantively different in content and structure. TCR reviewers reject near-duplicate samples.
Required elements for compliant Vonage sample messages by message category:
| Message Type | Required Elements | Example (Condensed) |
|---|---|---|
| Conversational | Brand name; reply instruction; opt-out method | Hi from Acme Support. How can we help? Reply STOP to opt out. |
| Customer Care | Brand name; context of message; opt-out method | Acme Support: Your ticket #1234 has been resolved. Reply STOP to opt out. |
| Marketing / Promotional | Brand name; offer detail; opt-out method; message frequency disclosure | Acme: Save 20% this weekend only. Msg freq varies. Reply STOP to opt out or HELP for info. |
| Account Notifications | Brand name; specific notification content; opt-out method | Acme: Your order #5678 has shipped. Expected delivery: Mar 28. Reply STOP to opt out. |
| 2FA / OTP | Brand name; code; expiry if applicable | Acme verification code: 847291. Expires in 10 minutes. Do not share this code. |
Vonage-Specific Character Limit Vonage’s TCR submission system requires sample messages to reflect actual intended content. Validate character count and compliance in the SMS Message Validator before submission.
Section 3: Brand Registration in Vonage Dashboard 3.1 Prerequisites Verification Confirm all of the following conditions are met before opening the Vonage registration form. Initiating registration with incomplete information produces rejections requiring paid resubmission.
- Trust Score Preflight Simulator completed; all flagged gaps remediated or accepted
- Brand Consistency Checker run; discrepancies resolved
- Active business website accessible without login; includes physical address, contact info, product/service description
- Privacy policy published and linked from every page footer; contains explicit SMS data non-sharing clause (see Section 4.3)
- EIN (Employer Identification Number) or Tax ID available exactly as registered with IRS
- Legal company name confirmed against IRS EIN documentation (not DBA)
- Business email using company domain (not @gmail.com or @yahoo.com)
- DUNS number obtained if available (strongly recommended; omission reduces trust score)
- Vonage account with appropriate permissions
- Authentication+ 2.0 email verification readiness (public profit brands)
Entity Type Restriction Sole proprietors are eligible only through the dedicated sole proprietor pathway in TCR (with OTP phone verification). Sole proprietors must use the Sole Proprietor TCR pathway available through MyTCRPlus (mytcrplus.com/sole-proprietor) which involves different documentation requirements and lower throughput limits. If you operate as a sole proprietor, do not attempt to register as an LLC or Corporation—misrepresentation of entity type causes immediate rejection and potential account suspension.
3.2 Accessing the Registration Form Sign in to the Vonage dashboard at https://dashboard.nexmo.com/. Navigate to: Brands and Campaigns. Click Register a new brand. The registration form opens with Brand Information fields. Complete Brand Information first.
3.3 Completing Brand Information Fields The Brand Information section establishes your company’s identity in the TCR system. This data is vetted against public records and undergoes Authentication+ 2.0 for public profit brands. Enter every field exactly as it appears in your official business documentation.
| Field | Data to Enter | Critical Notes |
|---|---|---|
| Legal Company Name | Exact name on EIN documentation | Do not use DBA, abbreviations, or trade names. If your EIN shows ‘Smith Enterprises LLC’ enter that exactly. |
| DBA / Brand Name | Operating name if different from legal entity | Optional but recommended for consumer-facing recognition. Must match website branding. |
| Entity Type | LLC, Corporation, Partnership, Government, Non-profit, Sole Proprietor | Select the actual legal structure. Mismatches against Secretary of State records cause rejection. |
| EIN / Tax ID | 9-digit IRS-assigned number (no dashes) | Enter without formatting dashes. TCR verifies against IRS Business Master File. Sole proprietors leave blank or follow OTP path. |
| Industry Vertical | Select closest matching category | 15+ verticals available. Choose the primary business activity. Misclassification affects use case eligibility. |
| Brand Website URL | Full URL including https:// | Must be active at time of submission. Must not require login. Must include business information. |
| Stock Symbol (public co.) | Exchange:TICKER format | Public companies: enter stock symbol. Private companies leave blank. Public company status provides significant trust score lift and triggers Authentication+ verification email. |
| Business Address | Physical street address; no P.O. Boxes | Must match public business registration records. Suite/unit numbers must match Secretary of State filing. |
| Business Phone | 10-digit US number | Should match number on Google Business Profile and public listings. |
| Business Email | Company domain email | Cannot be generic email provider. Must use business domain matching website URL. For Authentication+ 2.0, provide verification email. |
| DUNS Number | 9-digit D&B number if obtained | Optional but adds significant trust score improvement. Obtain from dnb.com before submission if possible. |
3.4 Submitting Brand Registration Review all fields against your IRS EIN documentation and business registration records before submitting. Click Submit. Vonage transmits your brand information to TCR. Brand review timeline: Standard vetting 1–3 business days; Authentication+ 2.0 email verification required for public profit brands; External vetting (high-risk industries or discrepancy flags) 5–7 business days. Monitor the registration status in the dashboard under Brands and Campaigns. Upon brand approval, TCR assigns a Brand ID and trust score. Proceed to Campaign Registration. If brand registration is rejected, review Section 6 (Rejection Remediation) before resubmitting. Each resubmission incurs the $4.50 brand fee.
Section 4: Campaign Registration 4.1 Campaign Registration Prerequisites Brand registration must be approved (and Authentication+ 2.0 completed where required) before campaign registration can be completed. Confirm your Brand ID is visible in the dashboard. Each campaign is a separate registration requiring its own fee, use case, sample messages, and number assignments.
A single brand can support multiple campaigns for different use cases. If your business sends both customer service messages and promotional messages, these require separate campaigns. Numbers assigned to one campaign cannot be assigned to another.
4.2 Completing Campaign Information Fields
| Field | Data to Enter | Critical Notes |
|---|---|---|
| Campaign Use Case | Select from dropdown | Use the classification identified by the MyTCRPlus TCR Use Case Selector. Permanent selection—cannot change after approval. Dashboard restricts selection based on brand vetting. |
| Campaign Name | Descriptive internal name | Alphanumeric. Not consumer-facing. Name your campaign to reflect use case and program (e.g., ‘Acme Customer Support 2026’). |
| Campaign Description | Detailed description of messaging program | Minimum 40 characters describing: who receives messages, what triggers messages, what value messages deliver, how recipients opted in. Vague descriptions are the most common rejection trigger. |
| Message Flow / Consent Description | How recipients will opt in | Describe the specific consent mechanism: web form with unchecked checkbox, verbal consent with documentation, consumer-initiated text, keyword opt-in. Reference your privacy policy URL. Provide links/screenshots. |
| Sample Messages (minimum 2–3) | Actual messages you will send | Enter 2–5 distinct messages validated by MyTCRPlus SMS Message Validator. Each must contain opt-out language, brand name, and reflect actual use case content. At least one per sub-use case. |
| Embedded Links | Check if messages contain URLs | Check this box if any sample messages contain URLs. Do not use public URL shorteners (bit.ly, tinyurl). Use full URLs or branded short domains. |
| Embedded Phone Numbers | Check if messages contain phone numbers | Check if sample messages include a callback number. |
| Age-Gated Content | Check if content is age-restricted | Required for alcohol and firearms content. Carriers require documented age verification process. |
| Direct Lending / Financial Services | Check if applicable | Check for mortgage, auto loan, and credit-related content. Triggers enhanced carrier review. |
4.3 Writing a Compliant Campaign Description The campaign description field is the single most common source of rejection for Vonage customers. TCR reviewers evaluate whether the description clearly establishes a legitimate, specific business messaging program. Generic language such as ‘we send business messages to customers’ produces rejection codes.
A compliant campaign description answers five questions: (1) Who is the business and what does it do? (2) Who are the message recipients and what is their relationship to the business? (3) What specific information do messages convey? (4) What action or event triggers each message? (5) How did recipients consent to receive messages?
Non-Compliant Description (Will Be Rejected) Acme Corporation sends business SMS messages to our customers regarding our services and products. We follow all applicable regulations.
Compliant Description (Meets TCR Standards) Acme Corporation (licensed HVAC contractor, Texas) sends transactional SMS to existing customers who have booked service appointments. Messages confirm scheduled appointments, notify customers when technicians are en route (including technician name and ETA), and request post-service satisfaction ratings. All recipients provided express written consent via our website booking form at acmehvac.com/book, which includes an unchecked SMS consent checkbox. We send 2–4 messages per service event. Message flow: Customer books appointment online > system sends confirmation SMS > day-of reminder SMS > technician dispatch notification SMS > post-service review request SMS.
4.4 Constructing the Opt-In / Message Flow Description The Message Flow field describes your consent collection process in verifiable detail. This field is submitted to carrier compliance teams and must withstand audit scrutiny. Provide the specific URL, form location, or other mechanism through which each recipient consented.
Acceptable consent mechanisms for Vonage TCR registration:
- Web form with unchecked SMS consent checkbox and compliant disclosure language
- Consumer-initiated text message to your Vonage number (keyword opt-in)
- Verbal consent with documented call recording and logging process
- Email opt-in with explicit SMS consent language (separate from email consent)
- Paper form with SMS consent section (requires digital log of paper records)
Invalid Consent Mechanisms The following consent methods will result in campaign rejection: pre-checked opt-in boxes, implied consent from existing business relationship alone (without affirmative opt-in action), purchase-conditioned consent (‘by buying you consent to texts’), third-party list purchases, and lead generation forms where SMS consent is not explicitly disclosed before submission.
4.5 Privacy Policy Requirements Vonage’s TCR submission process requires that your privacy policy be publicly accessible and contain specific SMS-related language. The policy must be linked from every page of your website footer and contain all of the following elements to avoid rejection codes and privacy-related denials:
- Explicit statement that SMS opt-in data and phone numbers are not sold, rented, or shared with third parties for marketing purposes
- Description of what types of SMS messages the business sends
- Description of message frequency (either fixed frequency or ‘message frequency may vary’)
- Statement that message and data rates may apply
- Instructions for opting out (reply STOP) and getting help (reply HELP or contact information)
- Contact information for privacy inquiries
MyTCRPlus Resource MyTCRPlus provides a customizable privacy policy template at mytcrplus.com/10dlc-privacy-policy-template/ that includes all required SMS-specific clauses. The template is updated as carrier requirements evolve. Download and have your legal counsel review before publication.
4.6 Submitting the Campaign Review all campaign fields against the MyTCRPlus pre-submission checklist. Confirm sample messages have been validated in the SMS Message Validator and score 85+. Click Submit Campaign. Vonage transmits to TCR. Campaign review timeline: 1–3 business days for standard use cases with trust scores above 50; 7–10 business days for low trust scores or manual review use cases; additional 1–3 business days for carrier-specific review on T-Mobile (MNO review for certain use cases). Monitor status at dashboard > Brands and Campaigns. Upon approval, proceed to number linking (Section 5).
Section 5: Number Assignment and Campaign Administration 5.1 Assigning Numbers to Approved Campaigns An approved campaign does not activate message delivery until phone numbers are linked to it. Each phone number can only belong to one campaign. Numbers assigned to Campaign A cannot simultaneously be assigned to Campaign B.
Standard Number Linking In the dashboard, navigate to Brands and Campaigns. Select the approved campaign from the campaign list. Click Link Numbers or Assign Numbers. Select the local phone numbers to assign from your available number inventory. You can assign multiple numbers in a single operation. Click Confirm Assignment. SMS activation on newly linked numbers takes 15 minutes to 72 hours depending on carrier provisioning queues. Numbers ported from other carriers require an additional 72 hours to 5 business days after port completion.
Number Pool Registration for High-Volume Operations Contact center environments or organizations requiring more than standard number volumes can access Vonage’s Number Pool program. T-Mobile enforces a maximum of 49 numbers per campaign; number pools enable larger allocations through a separate registration pathway. Contact Vonage support for the Number Pool request form. Number Pool requests require Vonage support review and carrier approval. Timeline: 5–15 business days. Number Pool campaigns carry higher monthly fees. Contact Vonage sales for current pricing.
5.2 Carrier-Specific Throughput Management Throughput limits are carrier-specific and determined by your trust score. Understanding per-carrier behavior enables accurate capacity planning for your Vonage campaigns:
| Trust Score | T-Mobile Daily Cap (brand-level) | AT&T Throughput (per campaign) | Verizon |
|---|---|---|---|
| 75–100 (TOP Tier) | 200,000 msgs/day brand-level | 4,500 msgs/min (Class A/B) | Proportional to trust score |
| 50–74 (High Mid) | 40,000 msgs/day brand-level | 2,400 msgs/min (Class C/D) | Proportional to trust score |
| 25–49 (Low Mid) | 10,000 msgs/day brand-level | 240 msgs/min (Class E/F) | Proportional to trust score |
| 1–24 (Low) | 2,000 msgs/day brand-level | Minimal | Minimal |
T-Mobile Brand-Level Daily Cap T-Mobile enforces a shared daily message cap across ALL campaigns registered under the same EIN. If you run multiple campaigns, the combined daily volume across all campaigns must not exceed your tier’s daily cap. Exceeding this limit triggers traffic throttling that affects all campaigns under the brand. Plan message scheduling across campaigns to stay within limits.
5.3 Modifying Active Campaigns Approved Vonage campaigns support limited modifications without resubmission. The following table defines what can and cannot be changed on an active campaign:
| Campaign Element | Modifiable? | Notes |
|---|---|---|
| Phone number assignments (add/remove) | Yes | Add or remove numbers; 15-minute to 72-hour activation window for additions |
| Campaign Name | Yes | Internal use only; does not affect TCR record |
| Sample Messages | Limited | Contact Vonage support to update sample messages; requires carrier review |
| Campaign Description | Limited | Minor updates may be possible through support; major changes require new campaign |
| Use Case / Campaign Type | No | Use case is permanent. Requires new campaign registration with new fees. |
| Brand Legal Name, EIN, Entity Type | No | Brand-level data cannot be modified when active campaigns exist. Requires brand re-registration. |
To modify a campaign, navigate to dashboard > Brands and Campaigns > [Campaign Name] > Edit. For changes that require Vonage support assistance, contact support via the dashboard ticket system.
5.4 Campaign Renewal and Cancellation All TCR campaigns registered through Vonage carry a minimum 3-month commitment (Political campaigns operate month-to-month). Campaigns auto-renew by default at the end of each commitment period. Monthly fees range from $1.50 for Low Volume use cases to $30 for Agents & Franchises.
Managing Auto-Renewal Navigate to dashboard > Brands and Campaigns > [Campaign Name] > Billing. Toggle Auto-Renew to Off to prevent automatic renewal at commitment end. Submit cancellation request before the renewal date; same-day cancellations after renewal processing are not eligible for refunds.
T-Mobile Dormant Campaign Fee T-Mobile assesses a $250 per month fee on campaigns that have no assigned numbers AND no message traffic within a 60-day window. Campaigns should be actively deactivated (numbers removed and cancellation submitted) rather than left dormant. Use the MyTCRPlus Rejection Remediation Tool to identify dormant campaigns that may be generating unnecessary carrier fees.
5.5 Opt-Out Management in Vonage Vonage automatically processes STOP keywords received on registered campaign numbers, removing the sender from that number’s outbound list. Understand the following operational implications:
- STOP processing is automatic at the Vonage platform level; no manual intervention is required for standard opt-outs
- Variations of STOP (STOPALL, UNSUBSCRIBE, QUIT, CANCEL, END) are all processed as opt-out requests per CTIA standards
- After a recipient opts out, sending further messages to that number from the same campaign number violates TCPA and triggers carrier action
- Opt-out records must be maintained for a minimum of 4 years per TCPA statute of limitations coverage
- If a recipient who previously opted out texts START or YES to your number, they re-subscribe; this action must be logged with timestamp and IP/device identifier where technically feasible
Review the Vonage opt-out management documentation in the dashboard support section.
SMS Consent and Opt-Out Log Requirements TCPA audit readiness requires maintaining consent records that include: timestamp with timezone, IP address or device identifier at time of consent, exact consent language presented, user’s affirmative action (checkbox state, keyword reply, button click), and opt-out events with timestamps. Vonage’s platform logs opt-out events natively; however, initial consent records must be maintained by your organization in your CRM or consent management system. MyTCRPlus provides consent logging templates at mytcrplus.com/consent.
Section 6: Rejection Remediation 6.1 Interpreting Rejection Notifications When TCR or carrier review rejects a brand or campaign submission, Vonage delivers a rejection notification to the account’s Admin email address and updates the registration status in the dashboard. The notification includes one or more rejection codes. Each code corresponds to a specific deficiency requiring remediation before resubmission.
First-time rejection is common: over 40% of initial TCR submissions require at least one resubmission. The goal of the MyTCRPlus Rejection Remediation workflow is to identify the complete set of violations across all rejection codes, correct them systematically, and resubmit with the highest possible confidence in approval.
MyTCRPlus Tool: Rejection Remediation Tool Access the Rejection Remediation Tool at mytcrplus.com/rejection-remediation-tool/ to look up any rejection code, understand the root cause, and receive step-by-step remediation guidance. The tool covers 179 error codes including all codes documented in the Vonage rejection guide. Each code entry includes: cause analysis, required documentation changes, estimated success probability for resubmission, and timeline expectations.
6.2 Rejection Code Reference: Brand-Level
| Code | Issue Category | Remediation Summary |
|---|---|---|
| 807 | Inauthentic website | Website must display physical address, contact info, product/service description, and all links must be functional. Test every link before resubmission. |
| 1003 | Website inaccessible | Verify website URL is correct and publicly accessible. Check for geo-blocking, firewall rules, or maintenance modes that could block TCR review. |
| 1004 | Website not in English | Website must be accessible and reviewable in English. Multi-language sites must include English version. |
| 1100 | Brand inconsistency: missing URL | Provide active website URL in brand submission. URL must resolve to business website. |
| 1101 | Brand inconsistency: domain not found | Confirm URL is correct and DNS resolves. Ensure no www prefix issues or HTTP/HTTPS mismatches. |
| 9110 | Website URL missing or non-functional | Same as 1003. Verify URL accessibility from external network before resubmission. |
| Authentication+ failure | Verification email PIN not completed | Complete the 2FA email verification process sent by TCR for public profit brands. |
6.3 Rejection Code Reference: Campaign-Level
| Code | Issue Category | Remediation Summary |
|---|---|---|
| 9103 | Opt-in language missing from website form | Add SMS consent checkbox (unchecked by default, non-required) to website contact/booking forms with compliant disclosure language. |
| 9104 | Privacy policy missing SMS clause | Add explicit SMS data non-sharing clause to privacy policy. Must state phone numbers and SMS consent data are not shared with third parties for marketing. |
| 9106 | Opt-out language missing from sample messages | Add STOP opt-out instructions to all sample messages. Every message sent in a marketing or promotional context must include opt-out language. |
| 9108 | Consent checkbox pre-checked | Set SMS consent checkbox to unchecked (not the default). Pre-checked consent is explicitly prohibited. Also ensure checkbox is not marked required. |
| 9110 | Website URL missing or non-functional | Verify website is publicly accessible without login. Check from external network. |
| 9209 | Prohibited content: high-risk financial | Permanent rejection. Content involving crypto, NFTs, hedge funds, or high-risk financial services cannot be registered. Do not resubmit. |
| 9304 | Website insufficient or broken links | Fix all broken links. Add business information: address, phone, product/service description. Pages must load within 10 seconds. |
| 9501 | Duplicate campaign submission | A campaign with identical use case and description already exists under your brand. If multiple locations are needed, include location identifiers in campaign description. |
| 9503 | Insufficient unique sample messages | Provide at least 2–3 substantively distinct sample messages. Near-duplicates (same message with small variations) are counted as one. |
| 9604 | Consumer-initiated opt-in: insufficient proof | Provide website URL or verifiable proof (flyer, business card) showing where consumers can find your number and initiate contact. Include instructional language for consumer-initiated consent. |
| 9606 | Sample message missing required elements | Ensure all sample messages include: brand name, specific message content, opt-out instructions. Check against SMS Message Validator. |
| 9607 | Message flow description insufficient | Rewrite message flow with specific consent mechanism, URL of opt-in form, trigger events for each message type, and recipient relationship to business. |
| 9999 | Rejection per customer request | No action required unless you requested a rejection to update your campaign. Resubmit with updated information. |
6.4 The Five-Strike Rule Rejection code 808 is triggered when a campaign has been declined five or more times without sufficient updates between submissions. At the five-rejection threshold, TCR escalates the review and subsequent vetting fees apply regardless of changes made. Avoid this threshold by ensuring comprehensive remediation of all identified issues before each resubmission.
Use the following procedure for every resubmission to prevent accumulating rejections on the same deficiencies: Open the MyTCRPlus Rejection Remediation Tool and enter every rejection code received. Generate the full remediation list covering all codes. Address all items—not just the first or most obvious code. TCR reviewers often identify secondary violations only after primary violations are corrected. Document each remediation action taken with timestamp and description. Maintain this log in your internal compliance records. Run the Brand Consistency Checker and SMS Message Validator again on updated materials. Run the Trust Score Preflight Simulator to verify no new score-suppressing factors were introduced. Resubmit only after all flagged items are resolved.
6.5 Vonage-Specific Rejection Escalation For campaigns rejected more than twice without clear resolution guidance, or for rejections citing carrier-specific policies not covered in standard TCR documentation, contact Vonage’s dedicated TCR support team:
- Dashboard ticket system (create new case with ‘TCR Campaign Rejection’ as issue type)
- Include in all support communications: Brand ID, Campaign ID, all rejection codes received, list of remediation actions taken
Section 7: Ongoing Compliance and Campaign Maintenance 7.1 Carrier Policy Monitoring TCR carrier policies update periodically, with major changes typically announced 30–90 days in advance. Content that was compliant at the time of campaign approval may require updates if carrier policies evolve. Campaigns that continue sending content inconsistent with updated policies risk suspension without prior notice.
MyTCRPlus Carrier Policy Tracker Access the MyTCRPlus 2026 Carrier Policy Tracker at mytcrplus.com/2026-carrier-policy-tracker/ for current T-Mobile, AT&T, and Verizon SMS content policies, enforcement updates, and change timelines. This resource is updated as carriers issue new guidance.
Monitor the following carrier-specific policy areas that most frequently affect Vonage campaigns: T-Mobile Policy Updates T-Mobile enforces T-Mobile Severity-0 campaign fines of $500–$10,000 for campaigns where actual messages diverge significantly from registered sample messages. Maintain sample message alignment with actual message content. T-Mobile prohibits cannabis content without exception. T-Mobile’s brand-level daily message caps are enforced in aggregate across all campaigns under an EIN.
AT&T Policy Updates AT&T uses real-time machine learning-based spam detection. Volume spikes, keyword stuffing, and sending patterns inconsistent with registered use cases trigger graduated enforcement: warning, then throttling, then suspension, then permanent blocklist. AT&T prohibits cannabis/CBD/hemp and get-rich-quick schemes. Crypto/NFT content faces elevated scrutiny. Phishing simulation campaigns require AT&T pre-authorization before sending.
Verizon Policy Updates Verizon uses behavioral analysis algorithms monitoring volume spikes and keyword patterns. Subscriber complaints trigger immediate investigation. Verizon suspends campaigns immediately upon receiving TCPA legal demands. Ensure all opt-out requests are processed within 10 business days maximum. Debt collection and credit repair content receives heightened scrutiny.
7.2 Message Content Drift Prevention Campaign drift—where actual messages sent deviate from the registered sample messages in use case, content type, or consent basis—is a leading cause of post-approval campaign suspension. Establish an internal review process to periodically validate active message templates against registered samples.
Quarterly Content Audit Procedure Pull a sample of 20–50 messages sent during the quarter across each active campaign. Run each message through the MyTCRPlus SMS Message Validator. Compare flagged content against registered sample messages and campaign use case. Document any content categories appearing in actual messages that are not reflected in registered samples. For minor template updates, contact Vonage support to determine if sample message updates require carrier re-review. For significant content category additions, evaluate whether a new campaign is required.
7.3 Consent Record Maintenance Consent records must be retained for a minimum of 4 years to cover the TCPA statute of limitations. Each consent record must contain: timestamp with timezone, IP address or device identifier, exact consent language presented to the recipient, and the user’s affirmative opt-in action.
Establish a systematic process for consent record export and archival. Vonage’s platform logs opt-out events at the carrier level; however, initial opt-in consent records must be maintained in your CRM, marketing platform, or dedicated consent management system. Vonage does not retain initial opt-in consent records on your behalf.
TCPA Litigation Risk TCPA class-action litigation exposure is calculated per message, not per campaign or per recipient. A single campaign sending 50,000 non-consented messages represents potential statutory damages of $25,000,000 to $75,000,000. Consent documentation is your primary defense. Consult qualified legal counsel regarding your consent collection and retention practices.
7.4 Multi-Campaign Administration Organizations operating multiple Vonage campaigns under the same brand EIN must coordinate across campaigns to avoid throughput cap violations and to maintain compliance posture across different use cases. Recommended administrative practices:
- Maintain a campaign inventory document recording: Campaign ID, use case, assigned numbers, approval date, commitment end date, monthly fee, and current status for every campaign under your brand
- Schedule message volumes across campaigns to stay within T-Mobile’s brand-level daily cap
- Audit number assignments quarterly; remove numbers no longer in active use to avoid dormancy fees
- Track commitment end dates; submit cancellation requests before auto-renewal dates for campaigns being retired
- When adding new use cases, use the MyTCRPlus TCR Use Case Selector to verify the new use case requires a separate campaign rather than modifying an existing campaign
7.5 Adding New Numbers to Existing Campaigns As your organization adds new Vonage local numbers, those numbers must be linked to an approved campaign before A2P SMS is permitted. Sending from unregistered local numbers is blocked by carriers and may trigger account-level enforcement actions.
Provision the new local number in your Vonage account. Navigate to the approved campaign to which the number should be assigned. Click Assign Numbers and select the new number. Allow 15 minutes to 72 hours for carrier provisioning before testing outbound SMS from the new number. For newly ported numbers, wait 72 hours minimum after port completion before assigning to a campaign.
7.6 Annual Registration Health Review Conduct a comprehensive annual review of your TCR registration posture using the following MyTCRPlus tools and internal audit procedures:
| Review Area | MyTCRPlus Tool | Action |
|---|---|---|
| Trust Score Optimization | Trust Score Preflight Simulator | Re-simulate annual trust score with updated business signals. Target score improvements above current band threshold. |
| Brand Data Consistency | Brand Consistency Checker | Verify brand registration data still matches current business registrations, address, and website. |
| Message Content Compliance | SMS Message Validator | Validate current active message templates; flag outdated language patterns. |
| Use Case Alignment | TCR Use Case Selector | Confirm current messaging programs are covered by existing campaign registrations; identify gaps requiring new campaigns. |
| Rejection Posture | Rejection Remediation Tool | Review any rejection codes received during the year; confirm all remediations remain in place. |
| Carrier Policy Compliance | Carrier Policy Tracker | Review all carrier policy updates from the past 12 months; assess impact on active campaigns. |
Section 8: MyTCRPlus Products and Subscription Options 8.1 Available Tools and Access Tiers MyTCRPlus.com provides diagnostic, validation, and remediation tools designed specifically for the Vonage TCR registration workflow. Tools are available through individual subscriptions, bundle packages, and one-time diagnostic purchases:
| Tool / Product | Pricing | Primary Use Case for Vonage Customers |
|---|---|---|
| Trust Score Preflight Simulator | $29/mo | Pre-submission brand scoring; trust score band prediction; improvement roadmap generation |
| Brand Consistency Checker | $29/mo | Brand data cross-validation before Vonage dashboard submission; discrepancy identification |
| TCR Use Case Selector | $29/mo | Permanent use case selection guidance; campaign classification before submission |
| SMS Message Validator | $49/mo | Sample message compliance scoring against Vonage requirements and carrier content policies |
| TCR Rejection Remediation Tool | $79/mo | 179-code rejection lookup; step-by-step remediation; resubmission confidence scoring |
| Vonage Provider Checklist | Included in Standard+ | Vonage-specific pre-submission checklist covering dashboard workflow, privacy policy prominence, sample message rules |
Starter Bundle (3 tools) $99/mo Growth Bundle (6 tools) $149/mo SMB Lite (One-time) $79 one-time
8.2 Vonage-Specific Resources The following MyTCRPlus subdomain resources are optimized for Vonage customer scenarios:
- vonage-10dlc-brand-registration.mytcrplus.com — Brand registration walkthrough specific to Vonage dashboard
- vonage-tcr-rejection-guide.mytcrplus.com — Vonage-specific rejection code interpretation
- vonage-tcr-privacy-policy-template.mytcrplus.com — Privacy policy template meeting Vonage’s carrier-driven requirements
- vonage-tcr-optin-template.mytcrplus.com — Opt-in consent form templates validated for Vonage campaigns
- vonage-tcr-consent-form-generator.mytcrplus.com — Interactive consent language generator
- how-to-fix-vonage-tcr-rejection.mytcrplus.com — Consolidated rejection remediation for Vonage
- vonage-tcr-checklist-pdf.mytcrplus.com — Downloadable pre-submission checklist PDF
- vonage-sms-validator-tool.mytcrplus.com — SMS Validator configured for Vonage submission rules
Section 9: Troubleshooting Guide 9.1 Common Operational Issues
| Symptom | Probable Cause | Resolution Path |
|---|---|---|
| Outbound SMS blocked; inbound works | Number not linked to approved campaign; campaign use case mismatch causing carrier filter | Verify number is linked to an approved campaign in dashboard. Run MyTCRPlus Rejection Remediation Tool. |
| SMS delivery dropped suddenly | Campaign drift triggering carrier filter; carrier policy update; trust score degradation | Audit message content against registered samples. Check Carrier Policy Tracker for recent updates. Contact Vonage support. |
| Campaign approval taking longer than 10 days | Low trust score triggering manual review; special use case requiring MNO review; Authentication+ pending | Check trust score via Simulator. Complete any pending Authentication+ email verification. Contact Vonage support with Campaign ID. |
| Rejection code not in reference list | Carrier-specific code not in standard TCR documentation | Look up code in MyTCRPlus Rejection Remediation Tool (179 codes covered). If not found, contact Vonage support. |
| EIN mismatch rejection | Legal entity name submitted does not match IRS record associated with EIN | Pull IRS EIN confirmation letter. Enter legal name exactly as IRS has it on file. Common issue: abbreviated names, missing LLC/Inc designation. |
| Campaign revoked after approval | Actual message content diverged from registered use case; carrier complaint threshold exceeded | Stop sending immediately. Run content audit against registered samples. Contact Vonage support for reinstatement process. |
| New number not sending after linking | Carrier provisioning lag | Wait 72 hours. Test using Vonage API or console. If still blocked after 72 hours, contact Vonage support. |
| HELP reply not functioning | HELP auto-response not configured in Vonage account settings | Configure HELP auto-response in dashboard settings. HELP response must include brand name and support contact information. |
9.2 Vonage Support Contacts
| Support Type | Contact Method | When to Use |
|---|---|---|
| TCR-Specific Support | Dashboard ticket system (create case with ‘TCR Campaign Rejection’) | Campaign rejections, registration delays, number linking issues, campaign modifications requiring carrier involvement |
| General SMS Support | Dashboard support or 1-866-901-0242 (business hours) | SMS/MMS delivery issues not related to TCR registration, opt-out processing |
| Support Case (non-urgent) | dashboard support portal | Documentation requests, billing questions, account configuration |
| MyTCRPlus Support | support@mytcrplus.com | Tool-specific questions, remediation guidance, compliance documentation |
Section 10: Glossary
| Term | Definition |
|---|---|
| 10DLC | 10-Digit Long Code — the A2P SMS messaging framework mandating brand and campaign registration with TCR to verify sender identity and enable commercial throughput on standard U.S. local phone numbers. |
| A2P | Application-to-Person — messaging sent from a business application or platform to individual recipients, as opposed to Person-to-Person (P2P) conversational messaging. |
| Brand ID | The unique identifier assigned by TCR upon successful brand registration. Required before campaign registration can proceed. |
| Campaign ID | The unique identifier assigned by TCR to each approved campaign. Each campaign represents a specific use case and message program. |
| CNP | Campaign Network Provider — the carrier or aggregator that delivers messages in a TCR campaign. Vonage is the CNP for campaigns registered through its platform. |
| CSP | Campaign Service Provider — the platform (Vonage, in this context) through which businesses submit brand and campaign registrations to TCR. |
| CTIA | Cellular Telecommunications Industry Association — the industry trade association whose messaging best practices are enforced by T-Mobile, AT&T, and Verizon as filtering criteria. |
| DBA | Doing Business As — a trade name or operating name different from the legal entity name. Submit the legal entity name as the TCR brand; DBA may be noted in the brand description. |
| DUNS | Data Universal Numbering System — a 9-digit identifier issued by Dun & Bradstreet for business identification. Providing a DUNS number in TCR brand registration adds an estimated 10–15 points to trust score. |
| EIN | Employer Identification Number — the IRS-assigned 9-digit tax identification number for a business entity. Required for TCR brand registration. |
| MNO | Mobile Network Operator — the individual carrier (T-Mobile, AT&T, Verizon) that reviews and may apply carrier-specific approval requirements to certain TCR use cases. |
| Number Pool | A registration pathway for organizations requiring more numbers than standard per-campaign limits allow. |
| SHAFT | Industry acronym for prohibited content categories: Sex, Hate, Alcohol, Firearms, Tobacco. Cannabis/CBD, payday loans, and high-risk financial services are treated as equivalent restrictions. |
| TCR | The Campaign Registry — the CTIA-authorized entity that processes brand vetting, assigns trust scores, and manages campaign approval workflows for the U.S. A2P SMS ecosystem. |
| TCPA | Telephone Consumer Protection Act — federal statute (47 U.S.C. § 227) governing automated communications requiring express written consent for marketing, with statutory damages of $500–$1,500 per violation. |
| Trust Score | A 0–100 score assigned by TCR to each registered brand, reflecting the strength of business verification signals, online reputation, and registration completeness. Trust score determines throughput limits and review queue assignment. |
Legal Disclaimer This document provides operational guidance based on publicly documented carrier requirements, TCR registration procedures, and CTIA messaging best practices as of March 2026. It does not constitute legal advice. Compliance requirements vary based on business model, use case category, message content, recipient jurisdiction, and applicable federal and state law. Organizations should consult qualified legal counsel for guidance specific to their messaging programs.
mytcrplus.com is designed to help customers achieve 10DLC compliance and carrier policy adherence. Final carrier approval is subject to The Campaign Registry (TCR) review and use case specifics. Campaign throughput limits and trust scores are determined by TCR based on brand verification and reputation signals outside mytcrplus.com’s control. Customers remain responsible for obtaining appropriate legal counsel regarding TCPA compliance and consent management requirements.
Vonage is a registered trademark of Vonage Holdings Corp. MyTCRPlus is a service of Native Chaos Holdings LLC. This document is not published, endorsed, or authorized by Vonage or The Campaign Registry. Procedures described reflect the Vonage dashboard workflow as documented in publicly available Vonage support resources and may change as Vonage updates its registration systems.
Document Version: 1.0 | Date: March 2026 | mytcrplus.com | support@mytcrplus.com