Telnyx Integration Guide

Table of Contents

Part 1 — Understanding A2P 10DLC and Your Role as a Telnyx Customer

1.1 What Is A2P 10DLC and Why It Affects You

Application-to-Person (A2P) SMS describes any messaging sent programmatically from a business application to a consumer's mobile phone. As a Telnyx customer, every business text message you send — whether appointment reminders, promotional offers, order confirmations, or security codes — falls under the A2P framework.

10-Digit Long Code (10DLC) is the regulatory infrastructure that governs A2P messaging in the United States. All three major carriers — T-Mobile, AT&T, and Verizon — enforce mandatory registration of sending brands and message campaigns through The Campaign Registry (TCR) before traffic can flow at commercial volumes.

Without completed 10DLC registration, Telnyx cannot route your A2P traffic, and carriers will block or filter your messages. This guide walks you through every step required to achieve and maintain compliant operation.

1.2 How Telnyx Fits into the 10DLC Ecosystem

Telnyx operates as your Communication Service Provider (CSP). In the 10DLC ecosystem, Telnyx submits your brand and campaign registration data to TCR on your behalf, binds your registered campaigns to your 10DLC phone numbers, and routes your traffic to carriers after successful registration.

Your responsibilities as the brand owner include providing accurate business information, obtaining and documenting consumer consent, crafting compliant message content, and maintaining campaign information as your program evolves. MyTCRPlus.com tools help you complete each of these responsibilities with diagnostic guidance before, during, and after registration.

1.3 How MyTCRPlus.com Tools Support This Process

MyTCRPlus.com is a compliance intelligence platform purpose-built for 10DLC and A2P SMS registration. The platform's tools provide:

• Pre-registration diagnostics to identify gaps before you submit to TCR — preventing rejections before they occur.
• Step-by-step registration workflow guidance calibrated to your business type, use case, and industry vertical.
• Sample message generators and consent language templates that meet TCR reviewer standards.
• Rejection remediation workflows tied to specific TCR error codes — with documented fix steps and resubmission checklists.
• Ongoing compliance monitoring support for active campaigns.

Throughout this guide, you will see references to specific MyTCRPlus tools at each step where they add the most value.

Part 2 — Pre-Registration Readiness Checklist

2.1 Why Pre-Registration Preparation Matters

TCR reviewers evaluate your brand registration against a defined set of criteria. Submitting incomplete or inconsistent information generates rejection error codes that require remediation cycles — adding 3 to 7 business days per resubmission attempt. Completing the readiness checklist in this section before you open the Telnyx portal reduces first-submission rejection probability.

2.2 Business Identity and Legal Entity Requirements

TCR verifies your business identity through multiple signals. The information you submit must be consistent across all sources — your EIN filing, your website, and your domain registration. Inconsistency between these sources is the primary cause of brand-level registration rejections.

2.2.1 Required Business Information

2.2.2 DUNS Number — Recommended Before Registration

A DUNS (Data Universal Numbering System) number issued by Dun & Bradstreet is not strictly required for all registrations, but it can add 10 to 15 points to your TCR trust score. T-Mobile mandates DUNS verification for brands seeking higher throughput tiers. If your business does not have a DUNS number, apply at least 30 days before your target registration date — processing takes 30 business days for the free tier.

• Apply at: dnb.com/duns-number.html
• Use your legal business name exactly as filed with the IRS.
• DUNS number must be active and match your EIN-registered address.

2.3 Website Requirements

TCR reviewers check your business website as part of brand verification. Your site must meet all of the following criteria at the time of submission. A failed website check generates error codes 1003, 1004, 1100, 1101, or 1103, each requiring correction before resubmission.

2.4 Privacy Policy — SMS Communications Section

Carriers perform automated checks on your privacy policy URL during campaign review. Your privacy policy must include a dedicated SMS Communications section. Absence of this section generates error code 9108 and is among the top causes of campaign rejection.

Your SMS Communications section must contain all of the following elements:

• A statement that you collect mobile phone numbers and SMS consent.
• An explicit statement that SMS consent and phone numbers are NOT shared with third parties or affiliates for their marketing purposes. This exact language is required by T-Mobile and enforced across all major carriers.
• Your data retention period for consent records — minimum 4 years.
• User rights language explaining how subscribers can request access to or deletion of their consent record.
• Supported keyword definitions: STOP (unsubscribe), START/UNSTOP (resubscribe), HELP (support contact).

2.5 Consent Infrastructure Readiness

TCR requires you to document how you collect consumer consent before sending any text message. Consent collection method and documentation are reviewed at campaign registration and may be audited after approval. Prepare your consent infrastructure before registering any campaign.

2.5.1 Consent Collection Methods Accepted by TCR

2.5.2 Required Consent Language Elements (TCPA)

Every consent collection form or script must contain all five of the following elements. Missing any single element is grounds for campaign rejection under error codes 2100 through 2108.

• Brand identification — your exact legal business name or recognized DBA.
• Message type disclosure — state whether messages are promotional, transactional, or both, and give specific examples.
• Frequency statement — either a specific number ("up to 4 messages per month") or a variable statement ("message frequency varies").
• Rate disclosure — the exact phrase: "Msg & data rates may apply."
• Opt-out instruction — the exact phrase: "Reply STOP to opt out" or "Text STOP to unsubscribe."

2.5.3 Consent Record-Keeping Requirements

You must store a verifiable record of every consent event. TCR may request documentation during review, and TCPA litigation requires consent records retained for a minimum of 4 years. Your consent records must capture:

• Timestamp with timezone of the consent event.
• IP address or device identifier of the consenting individual.
• Exact verbatim text of the consent language presented at time of collection.
• User response — checkbox state, keyword reply, or verbal affirmation.
• URL where consent was collected (for web forms).

2.6 Trust Score Optimization Before Registration

Your TCR trust score determines your campaign approval probability and your message throughput limits after approval. The score is calculated from signals that take time to accumulate. Address these items before you register — not after a rejection.

Part 3 — Brand Registration via Telnyx

3.1 Overview of Brand Registration

Brand registration is the first step of the two-part TCR registration process. You register your business entity as a brand, and TCR verifies it against third-party data sources including Dun & Bradstreet, credit bureaus, and public business registries. Brand registration is a one-time process per legal business entity. Cost: $4 one-time, non-refundable.

Expected timeline: 1 to 3 business days for standard verification. Businesses with DUNS numbers and strong digital footprints typically process faster.

3.2 Accessing Brand Registration in the Telnyx Portal

• Log in to your Telnyx account at portal.telnyx.com.
• Navigate to: Messaging > 10DLC > Brands.
• Select 'Register Brand.'
• Complete all required fields as detailed in Section 3.3.
• Submit registration and retain your Brand ID — you will need it for campaign registration.

3.3 Brand Registration Field Reference

Complete every field exactly as your business is registered with the IRS. Inconsistency between any field and your EIN filing is the primary cause of brand verification failure.

3.4 After Brand Submission

After submitting your brand registration through Telnyx, TCR processes the verification in the background. You will receive status updates via the Telnyx portal and email notifications. During this period:

• Do not submit campaign registrations until your brand status shows VERIFIED.
• Do not modify your business website in ways that could affect domain-to-brand consistency.
• Monitor your registration email inbox for any requests for additional information.

3.5 Brand Rejection — Common Errors and Remediation

If your brand registration is rejected, Telnyx will surface the TCR error code. Use the MyTCRPlus error code directory at mytcrplus.com/fix to identify the exact remediation steps for your code.

Part 4 — Campaign Registration via Telnyx

4.1 Overview of Campaign Registration

Campaign registration defines the specific message program you intend to run. Each campaign is tied to your verified brand and describes one category of messages — their purpose, the audience, the opt-in method, and the message content. Carriers use campaign registration data to make routing and filtering decisions.

Cost: $10 to $60 per month depending on use case category, charged by TCR through Telnyx. Campaign fees are recurring for the duration the campaign is active.

Expected timeline: 1 to 10 business days. Low-risk use cases (2FA, Account Notifications) approve faster. Marketing, Political, and Sweepstakes campaigns undergo manual carrier review.

4.2 Selecting the Correct Use Case

Use case selection is the most consequential decision in campaign registration. The wrong use case generates error code 9001 (Campaign Use Case Mismatch) — requiring you to restart the campaign registration process. Select the narrowest applicable category that accurately describes your message content.

4.3 Common Use Case Selection Mistakes

4.4 Campaign Registration Fields — Complete Reference

Access campaign registration in the Telnyx portal at: Messaging > 10DLC > Campaigns > Register Campaign. Complete each field as specified below.

4.4.1 Campaign Description

The campaign description is the most reviewed text field in your registration. TCR reviewers check whether the description clearly explains who you are, what you send, to whom, and why. Vague or mismatched descriptions generate the highest volume of campaign-level rejections.

Use this formula for your campaign description:

4.4.2 Sample Messages

TCR requires a minimum of three sample messages. These samples must accurately represent the actual messages your campaign will send. Reviewers use them to verify use case alignment and content compliance.

Every sample message must contain all five of the following elements:

• Brand name — your legal business name or recognized DBA, positioned at the start of the message.
• Opt-out instruction — "Reply STOP to opt out" or "Text STOP to unsubscribe" — positioned at or near the end.
• Realistic variable values — no placeholder text such as [NAME] or {ORDER_ID}; populate with representative real examples.
• No URL shorteners — Bit.ly, TinyURL, and similar services trigger carrier spam filters; use your full branded domain.
• Use case alignment — marketing samples must contain promotional language; transactional samples must not.

Compliant Sample Message Examples

4.4.3 Opt-In Method Documentation

TCR requires you to document exactly how consumers provide consent to receive your messages. This is the third most common rejection category after description issues and opt-out language. Select the method that accurately reflects your actual collection process and provide documentation in the format TCR expects.

4.4.4 Privacy Policy URL

Submit the direct URL to your privacy policy page — not your website homepage. The URL must resolve at HTTPS. Reviewers will navigate to this URL and verify that your SMS Communications section is present. A broken URL, an HTTP link, or a missing SMS section generates error code 9108.

4.4.5 Subscriber Opt-In Opt-Out Help Message Templates

TCR requires you to configure automated keyword response messages for STOP, HELP, and START (or UNSTOP). These must process within 5 seconds of receipt — a hard requirement enforced by all three major carriers as of August 2024. Configure these in the Telnyx portal under your campaign settings after registration approval.

Part 5 — Telnyx Platform Configuration After Campaign Approval

5.1 Campaign Approval Notification

When your campaign is approved by TCR, you will receive a notification via the Telnyx portal and the email address associated with your account. Your campaign status will change to ACTIVE in the portal. At this point, your campaign exists in the TCR database but is not yet bound to any phone numbers — you must complete the phone number assignment steps in Sections 5.2 and 5.3 before messages can flow.

5.2 Phone Number Acquisition for 10DLC Campaigns

10DLC campaigns require standard 10-digit long code (local) numbers. These are distinct from toll-free numbers and short codes, both of which have separate registration requirements not covered in this guide.

5.2.1 Selecting Numbers for Your Campaign

• In the Telnyx portal, navigate to: Numbers > Search & Buy Numbers.
• Select Voice Enabled and SMS Enabled as capabilities.
• Choose area codes that reflect your geographic service area or your target audience's region.
• Purchase the required quantity of numbers based on your expected message volume and throughput requirements.

5.2.2 Number Pool Sizing Reference

5.3 Binding Numbers to Your Campaign

After purchasing your numbers, you must bind them to your approved campaign. Unbound numbers will have messages filtered by carriers regardless of your campaign approval status.

• Navigate to: Messaging > 10DLC > Campaigns.
• Locate your approved campaign and select it.
• Select 'Add Phone Numbers' or 'Assign Numbers.'
• Select the numbers you purchased in Section 5.2.
• Confirm the binding. Status should update to reflect active number assignment.
• Verify the binding is complete before initiating any sends by checking that each number appears in your campaign's number list with an ACTIVE status.

5.4 Configuring Messaging Profiles

Telnyx uses Messaging Profiles to group sending numbers and apply shared configuration settings including webhook endpoints for incoming message handling, traffic routing preferences, and compliance controls. Each campaign should have a dedicated Messaging Profile.

• Navigate to: Messaging > Messaging Profiles > Create New Profile.
• Name the profile to match your campaign (e.g., "Acme_Marketing_Q4" or "Acme_Appointment_Reminders").
• Set Webhook URL to your application's inbound message handler endpoint. This endpoint must process STOP keyword responses and forward them to your opt-out list.
• Enable the Inbound Webhook for status callbacks to track delivery confirmations and failed delivery events.
• Assign your 10DLC numbers to this profile.
• In Compliance Settings, confirm that STOP/HELP/START auto-response templates are configured (per Section 4.4.5).

5.5 Webhook Configuration for Opt-Out Management

Carrier-mandated opt-out processing requires that STOP keyword responses are honored within 5 seconds. Your application must be configured to receive and process inbound STOP messages in real time. Failure to process opt-outs within the carrier-required window can result in campaign suspension.

At minimum, your inbound message webhook must:

• Receive the inbound message payload from Telnyx.
• Identify STOP, END, CANCEL, UNSUBSCRIBE, and QUIT keywords — all five must be treated as opt-out requests.
• Immediately add the sending phone number to your suppression list.
• Halt all future outbound sends to that number until an explicit START or UNSTOP keyword is received.
• Send the configured opt-out confirmation message (your STOP response template from Section 4.4.5).
• Log the opt-out event with timestamp for consent record retention.

Part 6 — Rejection Remediation: Error Codes and Recovery

6.1 Understanding the Remediation Process

Campaign rejections are normal at industry scale — the baseline first-submission approval rate for campaigns submitted without pre-registration preparation is approximately 54%. With proper readiness work (Parts 2 and 3 of this guide), your probability improves significantly. If your campaign is rejected, the remediation process is structured and predictable.

The four-phase remediation workflow:

• Diagnose — identify all error codes from the rejection notification.
• Classify — determine whether each error is auto-remediable (same-day fix), requires documentation revision, or is terminal (cannot be fixed without business-level changes).
• Fix and document — make the required changes and prepare your resubmission package.
• Resubmit and track — submit through Telnyx and monitor for approval or secondary rejection.

6.2 Campaign-Level Error Codes — Complete Reference

6.2.1 Campaign Description Errors (2001–2006)

6.2.2 Opt-In and Consent Errors (2100–2108)

6.2.3 High-Frequency Error Codes

Error 9106 — Missing Opt-Out Language in Sample Messages

This single error code accounts for approximately 15% of all campaign denials. Every sample message submitted — all three required samples — must contain opt-out language. TCR reviewers check each sample independently.

• Required language: "Reply STOP to opt out" OR "Text STOP to unsubscribe"
• Position: before or at the end of the message, not buried mid-message.
• Fix: Add opt-out language to all three samples. Resubmit same business day.

Error 9108 — Privacy Policy Compliance Failure

Accounts for approximately 12% of campaign denials. Your privacy policy URL is broken, the page has no SMS section, or the required non-sharing statement is absent.

• Required statement (exact language): "SMS consent and phone numbers are not shared with third parties or affiliates for their marketing purposes."
• Required section header: "SMS Communications" (exact title required by carriers).
• Fix: Add or update SMS section; verify URL resolves at HTTPS; resubmit.

Error 9607 — Consent Verification Failure

TCR cannot verify how opt-in was collected from the documentation provided. This requires photographic or screenshotted evidence.

• Required: Screenshot of web form showing checkbox in UNCHECKED default state.
• Required: Form URL (must be live and HTTPS at time of review).
• Required: Verbatim text of consent language as it appears on the form.
• Required: Timestamp proof — if form is not currently live, provide a dated screenshot.

Error 9001 — Campaign Use Case Mismatch

Message content in your samples conflicts with the declared use case category.

• Fix Option A: Change your use case to the category that matches your sample content.
• Fix Option B: Rewrite your sample messages to align with your declared use case.
• Do not submit promotional language in transactional use case samples under any circumstances.

6.3 Error Severity Classification

6.4 Resubmission Package Checklist

Before resubmitting a rejected campaign, verify every item in the following checklist. Incomplete resubmissions with the same deficiencies extend your timeline by an additional 3 to 7 business days.

• All error codes identified and classified.
• Updated sample messages — all three samples contain brand name, opt-out language, realistic variables, no URL shorteners, and use-case-aligned content.
• Consent documentation — screenshot with visible unchecked checkbox, consent language verbatim text, and live HTTPS URL.
• Privacy policy URL — functioning HTTPS link; SMS Communications section present with required non-sharing statement.
• Business verification documentation — if brand-level rejection contributed, include DUNS number, EIN documentation, or supplemental business identity verification.
• Campaign description revised — if error codes 2002, 2003, 2004, or 2005 were received.

6.5 Carrier Escalation Process

If your campaign is rejected a second time after a complete remediation, you may request carrier escalation through Telnyx's support team. The escalation request should be structured as follows:

Part 7 — Industry-Specific Compliance Requirements

7.1 Healthcare and Telehealth

Healthcare messaging operates under three overlapping regulatory frameworks: HIPAA, TCPA, and TCR carrier policies. The interaction between these frameworks creates obligations beyond standard 10DLC registration.

• HIPAA Business Associate Agreement (BAA): Required with Telnyx before sending any messages that could contain Protected Health Information (PHI). Contact Telnyx enterprise support to establish a BAA.
• PHI prohibition in message content: Combinations of patient name plus appointment specifics, diagnosis details, prescription information, or test results constitute PHI and are prohibited in SMS message bodies unless recipients have signed HIPAA-specific authorization.
• Recommended use cases: Customer Care (appointment reminders) and Account Notifications (test result availability alerts directing patients to a secure portal).
• Consent: Healthcare SMS consent must be separate from general marketing consent and must reference potential PHI in the language.
• More: mytcrplus.com/solutions/healthcare-telehealth-messaging-compliance/

7.2 Financial Services and FinTech

Financial services messaging is subject to TCPA, CFPB oversight, and GLBA, in addition to heightened carrier scrutiny for certain categories.

• Debt collection: Maximum 3 messages per week per recipient — enforced by Verizon and AT&T. Legal disclaimers required in collection message content.
• Cryptocurrency and NFT promotions: Prohibited by AT&T; restricted with mandatory manual review by T-Mobile and Verizon.
• Payday loans and high-interest lending: Restricted across all carriers; elevated review probability regardless of use case.
• Credit repair: Elevated scrutiny; must clearly disclose nature of service in message content.
• Recommended use cases: 2FA (login verification), Account Notifications (balance and fraud alerts), Customer Care (support responses).
• More: mytcrplus.com/solutions/financial-services-and-fintech/

7.3 Real Estate

Real estate is a high TCPA-litigation-risk vertical due to the prevalence of purchased lead lists and broad outreach practices. Property alert and lead nurturing programs require particular attention.

• Property alert programs: Must include clear frequency disclosure. Consent must be property-specific or interest-category-specific — not a blanket 'contact me' consent.
• Lead nurturing sequences: Must be registered as a Marketing use case, not Customer Care, if messages contain promotional real estate content.
• TCPA exposure: Real estate is one of the most frequent targets of TCPA class-action litigation. Consent documentation practices here are especially important.
• More: mytcrplus.com/solutions/real-estate-messaging-compliance/

7.4 E-Commerce and Retail

• Order confirmations and shipping updates: Register under Delivery Notifications. Do not include promotional language in these messages — doing so converts a transactional campaign into a marketing campaign and requires separate registration.
• Cart abandonment messages: Marketing use case. Requires explicit marketing consent — not implied from the purchase transaction itself.
• Post-purchase surveys: Customer Care or Low Volume Mixed use cases.
• Promotional blasts: Marketing use case. Frequency is constrained by your trust score and throughput limits.
• More: mytcrplus.com/solutions/e-commerce-and-retail/

7.5 Automotive

• Service reminders and maintenance follow-ups: Customer Care use case.
• Inventory promotions and sales announcements: Marketing use case — requires a separate campaign from service communications.
• High-volume seasonal campaigns (year-end sales, model launches): Require trust score above 75 for adequate throughput. Plan registration 60 to 90 days before peak season.
• More: mytcrplus.com/solutions/automotive-sms-compliance/

7.6 Education and EdTech

• FERPA compliance: Student record information is prohibited in SMS message content. Do not include grades, enrollment status, or other FERPA-protected data in message bodies.
• Minors under 18: Parental consent required for all messaging.
• Emergency alerts: Must be registered as Public Service Announcements, separate from general student communications.
• Admissions outreach: Marketing use case; requires explicit marketing consent from prospective students — inquiry form submission alone does not constitute SMS consent.
• More: mytcrplus.com/solutions/education-edtech-messaging-compliance/

7.7 Prohibited Content — All Verticals

Regardless of industry, the following content categories are prohibited across all TCR campaigns. Submitting prohibited content generates terminal rejections that cannot be remediated without a fundamental change in your messaging program.

Part 8 — Ongoing Campaign Administration and Compliance Maintenance

8.1 Campaign Monitoring — Metrics That Trigger Carrier Action

Carrier enforcement is data-driven. All three major carriers continuously monitor active campaign performance against defined thresholds. Exceeding these thresholds triggers automated throttling, manual review, or suspension — without prior warning in many cases.

8.2 List Hygiene Practices

Maintaining a clean subscriber list is the most effective way to control opt-out rates and spam complaints — the two leading triggers of carrier enforcement action.

• Suppress opted-out numbers immediately and permanently: once a subscriber texts STOP, they must not receive any further messages regardless of the sending number. Maintain a unified suppression list across all campaigns.
• Remove undeliverable numbers: consistently undeliverable numbers inflate your error rate and signal to carriers that your list may contain purchased or non-consented contacts. Remove numbers after 3 consecutive delivery failures.
• Honor re-subscribe requests: when a previously opted-out subscriber texts START or UNSTOP, restore them to your active list and send the configured START response. Log the re-subscribe event.
• Segment by consent type: never send marketing messages to subscribers who consented only to transactional communications. Consent type is campaign-specific.
• Audit your suppression list quarterly: verify that your technical suppression mechanism is functioning across all sending numbers and messaging platforms.

8.3 Modifying an Active Campaign

Material changes to your messaging program require campaign updates in the Telnyx portal, which may trigger re-review by TCR. Understanding what constitutes a material change prevents unintended compliance gaps.

8.4 Campaign Renewal and Ongoing Fees

TCR campaign registrations are not perpetual. Campaign fees are charged monthly and the campaign remains active as long as it is not voluntarily deactivated and fees continue to be paid. Telnyx manages the billing cycle.

• Monthly campaign fees: $10 to $60 per month depending on use case. Review your Telnyx billing dashboard for campaign-specific fee schedules.
• Lapsed campaigns: if a campaign is deactivated due to non-payment or voluntary deactivation, you must re-register — which may trigger re-review. Avoid campaign gaps for active messaging programs.
• Annual compliance review: even without regulatory triggers, conduct an annual review of your opt-in language, privacy policy, sample messages, and consent records to ensure they reflect current practices and any updated carrier requirements.

8.5 Carrier Policy Update Monitoring

Carrier policies evolve continuously. Material policy changes — particularly from T-Mobile, AT&T, and Verizon — can render previously compliant campaigns non-compliant without any rejection notification. The carrier policy enforcement dates below reflect changes that took effect or were reinforced through 2024 and into 2025.

8.5.1 T-Mobile Active Enforcement Policies

8.5.2 AT&T Active Enforcement Policies

8.5.3 Verizon Active Enforcement Policies

8.6 Trust Score Management

Your TCR trust score affects both your campaign approval probability and your active message throughput. Unlike the one-time nature of brand and campaign registration, trust score management is an ongoing operational discipline.

8.6.1 Actions That Improve Trust Score

8.6.2 Actions That Damage Trust Score

• Opt-out rate exceeding 5% in any monitoring window.
• Spam complaints exceeding 0.1% of delivered messages.
• Volume spikes that trigger automated carrier flagging.
• Confirmed TCPA violations or demand letters received by carriers.
• Operating prohibited content — SHAFT categories or extended prohibited list.
• Failed STOP processing within the 5-second window.

Part 9 — MyTCRPlus.com Tool Reference for Telnyx Customers

9.1 Tool Map by Workflow Stage

The following table maps each MyTCRPlus tool to the specific stage of your registration and compliance workflow where it adds the most value.

9.2 Using the Pre-Registration Symptom Checker

The symptom checker at newclient.mytcrplus.com evaluates your brand's readiness across four dimensions before you submit to Telnyx. Run this tool after completing your readiness work in Part 2 and before opening the Telnyx registration portal.

• Navigate to newclient.mytcrplus.com.
• Enter your business website URL and the email address you will use for TCR registration.
• Complete the 12-question intake covering business type, use case, opt-in method, website status, and consent documentation.
• Review the readiness report. Address all flagged items before proceeding.
• Re-run the checker after fixing flagged items to confirm readiness.

9.3 Using the Error Code Directory After Rejection

• Locate your error code(s) in the Telnyx portal rejection notification.
• Navigate to mytcrplus.com/fix.
• Enter each error code to retrieve the specific remediation workflow.
• Follow the fix steps in order. Do not skip steps even if they appear redundant.
• Use the resubmission checklist at the end of each workflow before returning to the Telnyx portal.

9.4 Using the AI Compliance Document Generator

The document generator at aio.mytcrplus.com produces compliant text for the three most commonly rejected documentation elements.

• Privacy policy SMS section: Input your brand name, opt-in method, and message frequency. The generator outputs a complete SMS Communications section including the required T-Mobile non-sharing statement.
• Opt-in consent language: Select your use case (promotional, transactional, or combined). The generator outputs form checkbox language containing all five required TCPA elements.
• Verbal consent script: Input your brand name and message types. The generator outputs a complete agent script with all required elements for STOP instruction, privacy URL reference, and brand identification.

Copy generated text directly to your website, consent forms, or training materials. Verify the text is live and accessible before resubmitting a rejected campaign.

Part 10 — Consent Language Quick Reference

10.1 Promotional SMS Consent (Web Form)

10.2 Transactional + Promotional Combined Consent

10.3 Transactional Only Consent (Lower TCPA Risk)

10.4 Healthcare Consent

10.5 Verbal Consent Script

10.6 Required Privacy Policy SMS Section

Part 11 — Quick Reference Summary

11.1 Complete Registration Workflow

11.2 Sample Message Compliance Checklist

• Brand name present (first word or within first 10 characters).
• Opt-out language present: 'Reply STOP to opt out' or equivalent.
• No URL shorteners (Bit.ly, TinyURL): use full branded domain.
• Variables populated with realistic examples, not [PLACEHOLDER] text.
• Message character count realistic (no truncation in submitted samples).
• No prohibited content (SHAFT categories + extended prohibited list).
• Message type matches declared use case (no promotional language in transactional samples).
• Frequency disclosure present for marketing campaigns.
• 'Msg & data rates may apply' included.

11.3 Monthly Compliance Review Checklist

• Opt-out rate reviewed — below 2% target; investigate if approaching 5%.
• Spam complaint rate reviewed — below 0.05% target; investigate if approaching 0.1%.
• Suppression list verified — numbers that texted STOP are not receiving messages.
• Privacy policy URL verified — still live, HTTPS, SMS section intact.
• Opt-in form or consent collection method still functioning correctly.
• Carrier policy updates reviewed — check mytcrplus.com for new enforcement notices.
• Consent records audit — new records captured correctly with all required fields.
• Number pool throughput — sufficient for current and projected send volume.

11.4 Key URLs Reference