Bandwidth A2P 10DLC Guide v1

A2P 10DLC Registration &

Campaign Administration

Using Bandwidth as Your CSP

with MyTCRPlus Diagnostic Tools

This document is produced by MyTCRPlus.com. All compliance determinations, carrier approvals, and regulatory outcomes are subject to Bandwidth, TCR, and carrier discretion. This documentation does not constitute legal advice.

Table of Contents

1. Document Overview & How to Use This Guide 4
2. Regulatory Framework: A2P, 10DLC, and TCR 5
3. Bandwidth as Your Campaign Service Provider (CSP) 7
4. Pre-Registration Preparation 9
5. Phase 1: Brand Registration via Bandwidth 13
6. Phase 2: Campaign Registration via Bandwidth 18
7. Phase 3: Phone Number Assignment 24
8. Phase 4: Post-Approval Validation & Launch 26
9. Ongoing Campaign Administration 29
10. Rejection Remediation Workflow 34
11. Trust Score Management 38
12. Compliance Monitoring & Audit Readiness 41
13. MyTCRPlus Tool Integration Reference 44
14. Bandwidth-Specific Troubleshooting Matrix 48
15. Regulatory Reference & Glossary 52

1. Document Overview & How to Use This Guide

1.1 Purpose

This guide provides Bandwidth customers with a complete procedural reference for Application-to-Person (A2P) 10-Digit Long Code (10DLC) registration, campaign management, and ongoing SMS compliance administration. Every step integrates MyTCRPlus.com diagnostic tools to reduce rejection risk, optimize trust scores, and maintain audit-ready compliance documentation.

Bandwidth operates as your Campaign Service Provider (CSP) — the entity that submits your brand and campaign registrations to The Campaign Registry (TCR) on your behalf. This documentation covers all customer-facing actions required within Bandwidth's portal, supplemented by pre-submission validation workflows using MyTCRPlus tools.

1.2 What This Guide Covers

• Initial A2P 10DLC brand registration through the Bandwidth portal
• Campaign registration including use case selection, sample messages, and consent documentation
• Phone number association and sender ID configuration
• Post-approval validation and campaign launch procedures
• Ongoing administration: modifications, renewals, number management, throughput monitoring
• Rejection remediation workflows with TCR error code resolution
• Trust score optimization strategies
• Compliance monitoring, audit preparation, and record-keeping

1.3 How to Use This Guide

Sequential execution is required for first-time registrations. Sections 4 through 8 must be completed in order. Sections 9 through 12 apply to ongoing administration after initial approval. Section 13 maps MyTCRPlus tool usage to each workflow stage. Section 14 provides troubleshooting for Bandwidth-specific errors. Section 15 serves as a standing reference for regulatory terminology.

1.4 Prerequisites

Before beginning registration, confirm the following:

• Active Bandwidth account with A2P SMS messaging enabled
• EIN (Employer Identification Number) issued by the IRS — format XX-XXXXXXX
• Legal business name exactly matching IRS/Secretary of State records
• Active business website with published Privacy Policy and Terms of Service
• Business domain email address (not Gmail, Yahoo, or Hotmail)
• DUNS number (optional but significantly improves TCR trust score — recommended)
• Completed consent collection mechanism on your website or point of sale
• Three or more sample SMS messages representing actual campaign content
• MyTCRPlus.com account (Standard or Plus tier recommended for full tool access)

2. Regulatory Framework: A2P, 10DLC, and TCR

2.1 The A2P 10DLC Mandate

Application-to-Person (A2P) messaging refers to automated or bulk text messages sent from business software platforms to consumer mobile devices. The Cellular Telecommunications Industry Association (CTIA) mandated 10-Digit Long Code (10DLC) registration in 2021 to address spam, phishing, and consumer protection failures in unregulated business SMS traffic.

All major U.S. carriers — T-Mobile, AT&T, and Verizon — enforce 10DLC requirements through traffic filtering systems. Messages transmitted from unregistered 10DLC senders are subject to blocking, throughput throttling, and sender suspension. Effective February 2025, carriers block all unregistered A2P traffic as a default action.

2.2 Registration Architecture

The 10DLC framework operates on a two-layer registration model:

2.3 The Campaign Registry (TCR)

The Campaign Registry (TCR) is the CTIA-authorized central authority managing 10DLC brand vetting and campaign approval. TCR assigns trust scores (0–100 scale) based on brand verification signals including EIN match, DUNS verification, domain age, and business reputation data.

Bandwidth submits your registration data to TCR as your Campaign Service Provider. TCR's evaluation is independent — Bandwidth cannot override TCR approval decisions, and MyTCRPlus cannot guarantee outcomes. The tools in this guide are designed to maximize first-submission approval probability.

2.4 TCPA Compliance Obligations

The Telephone Consumer Protection Act (TCPA), 47 U.S.C. § 227, governs automated text message communications. TCPA compliance is the customer's legal responsibility — Bandwidth's technical registration does not satisfy TCPA consent requirements. Both must be addressed independently.

TCPA requires express written consent before sending marketing messages. Consent must be specific to the sender, document the message purpose, disclose message frequency, provide an opt-out mechanism, and be stored with timestamp, IP address, and exact consent language. Statutory damages range from $500 per violation to $1,500 per willful violation.

2.5 CTIA Content Restrictions

The CTIA Messaging Principles define content categories that carriers will block regardless of registration status. These restrictions apply universally across all 10DLC campaigns:

• SHAFT — Prohibited Absolutely: Sex (adult/escort content), Hate (discriminatory messaging), Alcohol (promotional), Firearms (weapons promotion), Tobacco and vaping products
• Extended Prohibitions: Cannabis/CBD, payday loans, debt relief schemes, get-rich-quick content, cryptocurrency/NFT promotions
• Heightened Scrutiny: Debt collection, credit repair, lead generation, affiliate marketing, high-risk financial services

3. Bandwidth as Your Campaign Service Provider (CSP)

3.1 Bandwidth's Role in the Registration Chain

Bandwidth acts as your Campaign Service Provider (CSP) — the intermediary between your business and The Campaign Registry (TCR). When you register a brand or campaign through Bandwidth's portal, Bandwidth submits that data to TCR for vetting and routes approved traffic to T-Mobile, AT&T, and Verizon's network filtering systems.

This intermediary role means your registration data must satisfy two sets of requirements: Bandwidth's portal validation rules AND TCR's approval criteria. MyTCRPlus diagnostic tools address TCR-level requirements. Bandwidth-specific portal requirements are documented in Sections 5 and 6.

3.2 Bandwidth-Specific Registration Characteristics

Bandwidth's A2P 10DLC implementation differs from other CSPs in several operationally significant ways:

• Separate Local vs. Toll-Free Workflows: Bandwidth maintains distinct registration pathways for local 10DLC numbers and toll-free numbers (TFNs). This guide covers the 10DLC local number workflow. Toll-free numbers require a separate TFN verification process not covered here.
• Location-Based Compliance Documentation: Bandwidth requires documentation confirming compliance with state-specific messaging regulations for campaigns targeting recipients in California (CCPA), Florida, Oklahoma, and Washington. This applies particularly to high-volume marketing campaigns.
• Conservative Volume Estimates: Bandwidth's review process flags volume estimates that appear inflated relative to brand size, domain age, or business type. Submit conservative, defensible volume projections — underestimating is recoverable; overestimating can trigger manual review and carrier scrutiny.
• Enterprise Account Dedicated Contact: Organizations sending more than 500,000 messages per month should request a dedicated Bandwidth support contact before submitting registration. Ad hoc support for enterprise-scale accounts frequently extends review timelines.
• Brand-Campaign Linking Requirement: Every campaign must be explicitly linked to an approved brand within Bandwidth's portal. Orphaned campaign submissions (submitted without confirmed brand approval) will be rejected at the portal level before reaching TCR.
• Fallback Messaging Plan: Bandwidth requires documentation of a fallback plan for message delivery failures on unregistered or temporarily suspended numbers. This documentation should be prepared before campaign submission.

3.3 Bandwidth Portal Access

All registration and administration activities occur within Bandwidth's customer portal. Access the portal at:

https://dashboard.Bandwidth.com

Navigate to the Messaging section in the left sidebar to access A2P SMS registration functions. The primary navigation paths used throughout this guide are:

3.4 Bandwidth TCR Fee Structure

Bandwidth passes TCR registration fees through to customers in addition to platform usage charges. These are industry-standard fees set by TCR — not Bandwidth markup. MyTCRPlus platform subscription fees are separate from these carrier/TCR passthrough costs.

4. Pre-Registration Preparation

4.1 Overview

Preparation is the highest-leverage phase of the 10DLC registration process. Incomplete or inconsistent documentation submitted to Bandwidth and TCR is the leading cause of registration rejection and manual review delays. Completing this section before accessing the Bandwidth portal reduces first-submission rejection risk by addressing the four most common rejection triggers: EIN/business name mismatch, inadequate sample messages, undocumented consent collection, and use case misclassification.

4.2 Document Assembly Checklist

Assemble all of the following before initiating Bandwidth portal registration:

4.3 Brand Consistency Verification

TCR rejects registrations when submitted data contains inconsistencies across EIN records, business name, domain, and website content. These mismatches are the single leading cause of preventable rejections. Run this verification before portal submission.

Manual verification procedure (if not using the automated tool):

• EIN Match: Confirm the legal business name on your IRS EIN letter matches exactly: the Bandwidth account registration, the website "About" or footer section, and the TCR brand submission form.
• Domain Age: Verify your business domain is registered for at least 6 months. New domains (under 90 days) consistently score lower on TCR trust assessment. Check via whois lookup.
• Privacy Policy SMS Disclosure: Confirm your Privacy Policy contains the following language elements: (1) business name, (2) types of messages you send, (3) message frequency or "message frequency varies", (4) "Reply STOP to unsubscribe", (5) "Message and data rates may apply".
• Website-EIN Name Alignment: The name appearing most prominently on your homepage must match the legal name in your EIN letter. Discrepancies between brand names, DBAs, and legal names require explicit explanation in the campaign description.

4.4 Sample Message Preparation

Sample messages are evaluated by TCR reviewers against 12 carrier-level criteria. Three unique sample messages are required. Each message must represent actual content your subscribers will receive — generic or placeholder text is a rejection trigger.

4.4.1 Required Message Elements

Every sample message must contain all of the following elements:

• Business Name Identification: The message must identify your business by name. Recipients must know who is contacting them. Format: "[BusinessName]: " at the start, or "[BusinessName]" embedded naturally in message body.
• Message Content Aligned to Use Case: The message content must match the use case category you select during campaign registration. Marketing messages submitted under a "Notifications" use case will be rejected.
• Opt-Out Instruction: Include "Reply STOP to unsubscribe" or an equivalent opt-out instruction. This is carrier-mandatory for all marketing and mixed-use campaigns. Informational use cases (2FA, order confirmations) may have flexibility — confirm with your specific use case.
• No Prohibited Content: Messages must not contain SHAFT content, prohibited URLs, shortened URLs (bit.ly, tinyurl without whitelisting), or deceptive language.

4.4.2 Sample Message Examples by Use Case

4.5 Use Case Selection

Selecting the correct use case category is one of the highest-impact decisions in the registration process. Use case misalignment between declared category and actual message content causes 40% of campaign rejections. TCR reviewers compare your sample messages to the selected category and reject submissions where the content does not match the declared purpose.

4.6 Consent Documentation Preparation

Your opt-in documentation must describe exactly how subscribers consent to receive messages from your business. TCR reviewers assess whether your consent collection method produces valid, specific, and auditable consent records. Vague or non-specific consent descriptions are a significant rejection trigger.

4.6.1 Acceptable Opt-In Methods

• Web Form Opt-In: Customer submits a form with a checkbox explicitly consenting to SMS messages. Checkbox cannot be pre-checked. Consent language must name your business and describe message type.
• Keyword Opt-In (SMS): Customer texts a keyword (e.g., JOIN, YES, SUBSCRIBE) to your number after seeing opt-in instructions in advertising or signage.
• Point of Sale Opt-In: Written consent collected at checkout or during service signup, with explicit SMS disclosure.
• Double Opt-In: Customer provides phone number, receives confirmation text, replies to confirm — strongest consent documentation for marketing use cases.
• Paper Form Opt-In: Written consent form with signature, photographed or scanned for records.

4.6.2 Consent Documentation Format for TCR Submission

Prepare a written consent description covering the following elements. This language goes into the "Opt-in Description" field during campaign registration:

5. Phase 1: Brand Registration via Bandwidth

5.1 Overview

Brand registration establishes your verified business identity with TCR. This is the first required step and must be approved before campaign registration can begin. Bandwidth submits brand data to TCR for external verification against business registries, domain records, and reputation signals. Typical approval time is 1–3 business days for standard registrations; manual review for scores below 50 extends to 7–10 business days.

5.2 Brand Registration Procedure

5.3 Brand Review Timeline and Status Monitoring

After submission, monitor your brand status in the Bandwidth portal under Messaging → 10DLC Brands. Status values and their meanings:

6. Phase 2: Campaign Registration via Bandwidth

6.1 Overview

Campaign registration defines the specific messaging use case associated with your approved brand. TCR evaluates the consistency between your declared use case, sample messages, consent collection method, and supporting URLs. This phase has the highest rejection rate of any registration step — primarily due to content/use case misalignment and insufficient opt-in documentation.

You must have a VERIFIED or SELF_DECLARED brand status before submitting a campaign. Bandwidth will reject campaign submissions against a PENDING or FAILED brand status.

6.2 Campaign Registration Procedure

6.3 Campaign Status Values

7. Phase 3: Phone Number Assignment

7.1 Overview

Phone numbers must be explicitly associated with an ACTIVE campaign before they can send compliant A2P traffic. Numbers not associated with an approved campaign will transmit as unregistered traffic and are subject to filtering, throttling, and suspension. This step must be completed before message sending begins.

7.2 Number Assignment Procedure

7.3 Number Provisioning for New Numbers

If you need to acquire new local 10DLC phone numbers for your campaign:

• Navigate to Numbers → Available Numbers in the Bandwidth portal.
• Search by area code, state, or numeric pattern.
• Select desired numbers and click Provision.
• Confirm the numbers appear in My Numbers with ACTIVE status.
• Proceed with campaign association as described in Section 7.2.

7.4 Number Porting into Bandwidth for Campaign Use

If porting an existing number from another carrier for use in an A2P campaign, the porting process must be completed before campaign association is possible. Ported numbers require 24–72 hours after transfer completion before A2P registration and association can proceed. Do not attempt campaign association while a port is in progress.

8. Phase 4: Post-Approval Validation & Launch

8.1 Pre-Launch Validation Checklist

Complete all validation steps before initiating any message traffic. Sending traffic before validation is complete creates compliance risk and may invalidate clean delivery history.

8.2 Message Delivery Testing Protocol

Test delivery across all three major carrier networks before initiating production traffic. Delivery failures on a specific carrier indicate a carrier-level filtering issue that should be resolved before scaling volume.

• Send a test message from each sending number to a T-Mobile device.
• Send the same test message to an AT&T device.
• Send the same test message to a Verizon device.
• Verify: Message delivered within 30 seconds; content displays correctly; no [SPAM] or [SUSPICIOUS] labels in carrier delivery.
• If any carrier fails delivery: check Bandwidth Analytics for error codes before escalating to Bandwidth support.

8.3 Volume Ramp Schedule

A gradual volume ramp during the first 30–90 days of operation builds positive delivery history with carrier filtering systems. Launching at full volume immediately — especially for new brands with lower trust scores — increases complaint rates and triggers carrier scrutiny.

9. Ongoing Campaign Administration

9.1 Overview

Ongoing administration encompasses all post-launch activities required to maintain campaign compliance, manage subscription lifecycle, monitor delivery performance, and respond to regulatory changes. Active campaigns require periodic review — compliance obligations do not end at approval.

9.2 Campaign Subscription Renewal

Campaign registrations require monthly renewal through continued Bandwidth billing. Campaigns with lapsed subscriptions (EXPIRED status) cannot send traffic. Bandwidth sends billing failure notifications via email — ensure your payment method remains current.

• Billing Monitoring: Review Bandwidth billing statements monthly under Account → Billing → Invoice History. Verify campaign subscription line items appear for all active campaigns.
• Payment Method Updates: Update payment methods under Account → Billing → Payment Methods before existing card expiration. Automatic renewal failures result in immediate EXPIRED campaign status.
• Campaign Reinstatement after Expiration: Navigate to Messaging → 10DLC Campaigns → [Expired Campaign] → Renew. Reactivation typically processes within 24 hours. Number associations are preserved during reinstatement.

9.3 Campaign Modification Procedures

Campaign modifications are subject to TCR re-review for changes that affect core registration attributes. Minor administrative changes (contact info updates) typically do not require re-vetting. Material changes to sample messages, use case description, or opt-in method trigger re-review.

9.4 Number Pool Management

Organizations using number pools (multiple sending numbers per campaign) must manage pool composition actively. Inactive numbers left in pools degrade delivery metrics. Numbers with complaint or opt-out spikes should be rotated out promptly.

• Adding Numbers to a Pool: Navigate to Campaign → Associated Numbers → Add Numbers. Select numbers from inventory. Association processes within 15–60 minutes.
• Removing Numbers from a Pool: Navigate to Campaign → Associated Numbers → Select Number → Disassociate. Numbers revert to unassigned status and can be associated with other campaigns or deprovisioned.
• Pool Size Guidance: Maintain no more than 20% inactive numbers in any pool. Numbers not sending traffic within 30 days of association should be evaluated for removal or reassignment.

9.5 Opt-Out Management Obligations

Processing opt-out requests is a legal obligation under TCPA and a carrier compliance requirement. Failures to process opt-outs are among the most common triggers for campaign suspension and TCPA litigation.

9.5.1 STOP Keyword Requirements

• Mandatory STOP Response: Your platform must send an automatic confirmation reply when a subscriber texts STOP. The confirmation must include your business name and confirm their opt-out.
• Required Response Format: "You have been unsubscribed from [BusinessName] messages. No further messages will be sent. Reply START to resubscribe."
• Processing Timeline: Opt-outs must be processed within 24 hours of receipt. Bandwidth's platform processes STOP keywords automatically if configured — verify your platform's STOP handling is active.
• Suppression List Management: Maintain a persistent suppression list of opted-out numbers. This list must be applied before every send — including to new number purchases and across all campaigns under the same brand.

9.5.2 HELP Keyword Requirements

• Mandatory HELP Response: Texts containing HELP must receive an automatic reply with: (1) business name, (2) message frequency disclosure, (3) support contact information, (4) opt-out instructions.
• Required Response Format: "[BusinessName] alerts: Msg freq varies. Help: [support@businessname.com] or 1-800-XXX-XXXX. Msg&Data rates may apply. Reply STOP to cancel."

9.6 Performance Monitoring

Access delivery analytics in the Bandwidth portal under Messaging → Analytics. Monitor the following metrics weekly during the first 90 days, monthly thereafter:

9.7 TCPA Consent Record Maintenance

Consent records must be retained for a minimum of 4 years from date of collection to cover the TCPA statute of limitations. Records must be retrievable on demand for legal discovery, carrier audit, or TCR investigation requests.

9.7.1 Required Record Elements per Subscriber

• Timestamp: Date, time, and timezone of consent collection.
• IP Address: IP address of the device used to provide consent (for web-based opt-ins).
• Consent Language: Exact text of the disclosure presented to the subscriber at point of consent.
• Mechanism: How consent was provided (checkbox, keyword, signature).
• Channel: Website URL, physical form reference, or inbound keyword number.
• Subscriber Identifier: Phone number and name as provided during opt-in.

10. Rejection Remediation Workflow

10.1 Overview

TCR rejections are recoverable in most cases. The critical requirement is identifying the specific root cause from the rejection code before resubmitting. Resubmitting without addressing the documented deficiency results in a second rejection at a higher manual review probability, extending timelines by 7–10 additional business days.

10.2 Rejection Response Protocol

• Locate the rejection code in the Bandwidth portal under the rejected brand or campaign record.
• Document the rejection code, timestamp, and any supplemental message text before taking any action.
• Look up the rejection code using the MyTCRPlus Rejection Remediation Tool.
• Complete all remediation actions for that specific code — partial remediation causes re-rejection.
• Re-run the MyTCRPlus Brand Consistency Checker and SMS Message Validator after remediation.
• Wait at minimum 48 hours after addressing root causes before resubmitting.
• Resubmit via the Bandwidth portal following the same procedures as the initial submission.
• Log the rejection code, root cause, remediation actions, and resubmission date in your compliance records.

10.3 Common Rejection Codes and Remediation

10.4 Bandwidth-Specific Rejection Escalation

If a rejection code is not listed in the Bandwidth portal, appears to be a portal-level rejection (before reaching TCR), or if remediation steps do not resolve the issue after two resubmission attempts, escalate to Bandwidth's A2P support team directly:

• Bandwidth Support Portal: support.bandwidth.com — submit a ticket under the A2P/10DLC category
• Enterprise Accounts: Contact your dedicated Bandwidth account representative directly
• Required Information for Escalation: Brand ID, Campaign ID (if applicable), rejection code, timestamp of rejection, remediation steps already attempted, and current portal status values

11. Trust Score Management

11.1 Overview

TCR's trust score (0–100) directly determines throughput limits and approval speed. Scores are assigned at brand registration and can be improved over time through external vetting, reputation building, and business credential strengthening. Trust scores are not updated automatically — proactive action is required to improve a low initial score.

11.2 Trust Score Factors

11.3 Requesting Enhanced Vetting

Enhanced vetting involves third-party verification of your business identity and is the single most impactful trust score improvement available post-registration. Bandwidth coordinates enhanced vetting through TCR's authorized vetting partners.

• Navigate to Messaging → 10DLC Brands → [Your Brand] → Request Enhanced Vetting.
• Select your vetting partner from the available options ($40–$95 fee applies).
• Complete the vetting partner's verification form — this typically requires business documentation, officer verification, and acknowledgment of messaging policies.
• Processing time: 2–5 business days.
• Upon completion, your brand record will reflect the updated trust score in the Bandwidth portal.

12. Compliance Monitoring & Audit Readiness

12.1 Ongoing Monitoring Requirements

Compliance obligations are continuous, not point-in-time. Carrier policies change, TCR updates content guidelines, and TCPA case law evolves through litigation. An approved campaign today may become non-compliant without proactive monitoring.

12.2 Monthly Compliance Review Checklist

12.3 Quarterly Audit Preparation

Conduct a full compliance audit quarterly to prepare for potential carrier audits, TCR reviews, and legal discovery requests. Organize the following records into a compliance package accessible on 5-business-day notice:

• Brand Registration Package: Brand registration confirmation, TCR brand ID, trust score history, EIN documentation.
• Campaign Registration Package: Campaign approval confirmation, TCR campaign ID, use case documentation, sample messages as approved.
• Consent Record Archive: All subscriber consent records from the prior 4 years with timestamps, IP addresses, and consent language.
• Opt-Out Processing Log: Record of all STOP requests received, processing timestamps, and confirmation that subscribers were removed from send lists.
• Delivery Performance History: Monthly delivery rate, opt-out rate, and complaint rate reports from Bandwidth Analytics.
• Policy Compliance Review Log: Documentation of monthly compliance reviews with dates, reviewer names, and any corrective actions taken.

13. MyTCRPlus Tool Integration Reference

13.1 Tool Usage Map by Workflow Stage

13.2 Tool Access by MyTCRPlus Subscription Tier

14. Bandwidth-Specific Troubleshooting Matrix

14.1 Portal and Submission Issues

14.2 Delivery and Performance Issues

15. Regulatory Reference & Glossary

15.1 Regulatory Quick Reference

15.2 Regulatory Disclaimer

15.3 Key Regulatory Contacts and Resources

• Bandwidth A2P Support: support.bandwidth.com — A2P/10DLC category ticket submission
• The Campaign Registry: campaignregistry.com — Brand and campaign status lookup portal
• CTIA Messaging Principles: ctia.org/the-wireless-industry/industry-commitments/messaging-principles-and-best-practices
• Dun & Bradstreet DUNS Registration: dnb.com — Free DUNS number registration
• IRS EIN Verification: irs.gov — Retrieve EIN confirmation letter (CP 575 or 147-C)
• MyTCRPlus Tool Suite: mytcrplus.com/tools/ — Full diagnostic tool library
• MyTCRPlus Documentation Hub: mytcrplus.com/guides/ — Compliance guides and regulatory updates
• MyTCRPlus Support: support@mytcrplus.com — Technical and compliance support

MyTCRPlus.com

A2P 10DLC Compliance Infrastructure

Native Chaos Holdings LLC | Henderson, Nevada | mytcrplus.com

© 2026 MyTCRPlus.com. All rights reserved. | v1.0 March 2026