Sinch A2P 10DLC Guide

SINCH A2P 10DLC REGISTRATION

& ONGOING CAMPAIGN ADMINISTRATION

Step-by-Step User Guide Using MyTCRPlus.com Tools

Version 1.0 | 2025 | mytcrplus.com

Table of Contents

Section 1: Orientation — Sinch, 10DLC, and TCR Framework

Section 2: Pre-Registration Preparation

Section 3: MyTCRPlus Tool Sequence for Sinch Registration

Section 4: Brand Registration — Step-by-Step

Section 5: Campaign Registration — Step-by-Step

Section 6: Sinch-Specific Submission Workflow

Section 7: Trust Score Optimization

Section 8: Post-Approval Campaign Administration

Section 9: Rejection and Remediation Procedures

Section 10: Ongoing Compliance Monitoring

Section 11: Troubleshooting Reference

Appendix A: Required Documentation Checklist

Appendix B: TCR Trust Score Reference Table

Appendix C: Carrier-Specific Content Restrictions

Appendix D: Sinch-Specific Error Code Reference

Section 1: Orientation

1.1 What This Guide Covers

This guide covers the complete lifecycle of A2P SMS operations for Sinch customers: from initial compliance preparation through brand registration, campaign registration, Sinch platform submission, trust score management, ongoing monitoring, and rejection remediation. Every procedural step identifies which MyTCRPlus.com tool accelerates or de-risks that step.

Sinch operates as a Campaign Service Provider (CSP) — the intermediary between your business and The Campaign Registry (TCR). Sinch submits your brand and campaign data to TCR on your behalf and routes approved messages through carrier networks. This means your registration must satisfy both TCR standards and Sinch's internal submission requirements.

1.2 Regulatory Framework Overview

10-Digit Long Code (10DLC) is the CTIA-mandated framework requiring all Application-to-Person (A2P) messaging businesses to register sender identity and campaign intent with The Campaign Registry (TCR) before sending commercial SMS at volume. The Telephone Consumer Protection Act (47 U.S.C. § 227) (TCPA) separately governs consent requirements and imposes $500–$1,500 per-message liability for violations.

1.3 Why Sinch Customers Need a Separate Tool Layer

Sinch's dashboard facilitates submission but does not provide pre-submission diagnostic tools, use case optimization guidance, trust score simulation, or rejection remediation workflows. MyTCRPlus.com fills this gap as a provider-agnostic compliance infrastructure layer that operates before, during, and after Sinch's submission process.

Sinch's average TCR approval timeline is 4–8 business days, among the longer timelines for Tier 1 providers. Pre-submission validation through MyTCRPlus tools can reduce rejection risk by eliminating the most common failure modes before the application enters Sinch's review queue.

Section 2: Pre-Registration Preparation

2.1 Business Entity Requirements

TCR requires verifiable business identity. The following must be in place before initiating any registration through Sinch. Missing or mismatched documentation is the leading cause of brand-level rejection.

2.2 Running the MyTCRPlus Pre-Submission Readiness Assessment

Before opening the Sinch dashboard, complete the following MyTCRPlus tool sequence. This sequence validates your documentation, identifies trust score gaps, and confirms use case classification — the three areas where 80%+ of TCR rejections originate.

Step 2.2.1 — Brand Consistency Checker

Tool: Brand Consistency Checker (mytcrplus.com/tools)

Purpose: Validates that your brand name, EIN, domain, and address are consistent across registration fields. EIN/legal name mismatches are the most common brand rejection trigger.

What to input:

• Legal business name as it appears on IRS Form SS-4
• Business website URL
• Physical address
• EIN (without dashes for comparison purposes)

What the tool checks:

• Name format consistency (LLC vs L.L.C., Inc. vs Incorporated)
• Domain-to-brand-name alignment (acme.com for Acme LLC)
• Address format standardization (abbreviated vs. spelled-out street types)
• Cross-field consistency that TCR's verification algorithms flag

Expected output: A consistency score with specific field-level flags. Resolve all flagged discrepancies before proceeding. A score below 85% indicates high rejection probability at brand vetting.

Step 2.2.2 — Trust Score Preflight Simulator

Tool: Trust Score Preflight Simulator (mytcrplus.com/tools)

Purpose: Estimates your TCR trust score (0–100 scale) before submission. Trust score determines throughput limits and approval speed.

Input the following business profile data:

• Business entity type (Corporation, LLC, Sole Proprietor, Non-Profit, Government)
• Years in operation
• DUNS number status (obtained / applied / not started)
• Website domain age (months)
• Online review presence (Google, BBB, Yelp ratings)
• Prior TCR registration history (if any)
• Planned use case category

Interpreting results:

If the simulator returns a score below 50, address the deficiencies identified before submitting to Sinch. Key improvement actions:

• Obtain DUNS number if not already registered (adds 10–15 points; apply at dnb.com)
• Age the business domain to 6+ months minimum if possible
• Build Google Business Profile with 4+ star average rating
• Start with a low-risk use case (2FA, Notifications) before adding Marketing campaigns

Step 2.2.3 — TCR Use Case Selector/Wizard

Tool: TCR Use Case Selector (mytcrplus.com/tools)

Purpose: Determines the correct TCR use case category for your messaging program. Incorrect use case selection is a primary campaign rejection cause. Sinch's internal taxonomy adds a layer of classification that must align with the underlying TCR category.

The selector walks through a decision tree based on:

• Primary purpose of messages (Marketing, Notifications, Alerts, Customer Care, 2FA, Mixed)
• Content type (promotional offers, transactional updates, security codes, support responses)
• Audience relationship (existing customers, prospects, subscribers, employees)
• Expected message frequency (one-time, recurring, triggered)
• Industry vertical (healthcare, financial, retail, automotive, etc.)

The tool outputs:

• Recommended TCR use case with justification rationale
• Sinch-specific use case mapping (Sinch's category labels differ from TCR's)
• Content restrictions applicable to the selected use case
• Sample message templates pre-approved for the use case
• SHAFT content warnings if your industry is adjacent to restricted categories

Section 3: MyTCRPlus Tool Sequence for Sinch Registration

3.1 Complete Tool Workflow Sequence

Execute tools in the following order. Each tool output feeds into the next step. Do not skip steps — each validates a distinct failure category that cannot be detected by downstream tools.

3.2 SMS Message Validator — Sample Message Preparation

Tool: SMS Message Validator (mytcrplus.com/tools)

TCR requires 1–5 sample messages per campaign. These samples must:

• Reflect the actual content of messages you will send
• Include your brand name in every message
• Include opt-out language (Reply STOP to opt out) in marketing messages
• Not contain public URL shorteners (bit.ly, tinyurl.com — use branded domains)
• Not exceed 160 characters if submitting as single-segment SMS
• Align with the declared use case (marketing samples cannot accompany a 2FA use case)

Run each sample message through the validator before adding it to Sinch's campaign registration form. The validator flags:

• Missing brand identification
• Absent or malformed opt-out instructions
• URL shortener detection
• Character count and segment analysis
• Prohibited SHAFT content keywords
• Carrier-flagged high-risk terminology

Corrected sample: A compliant marketing message format acceptable to Sinch and TCR:

3.3 Consent Language Validator

Tool: Consent Language Validator — SMS Consent Requirements Tool (mytcrplus.com/tools)

TCR and TCPA both require documented consent. The validator confirms your opt-in language contains all mandatory elements:

• Clear disclosure that the subscriber will receive SMS messages from your business
• Brand name identification in the consent language
• Message frequency disclosure (e.g., '2-4 msgs/month' or 'message frequency varies')
• Standard disclosure: 'Msg & data rates may apply'
• Opt-out instructions: 'Reply STOP to opt out'
• Help instructions: 'Reply HELP for help'
• Link to Privacy Policy
• Affirmative action requirement (checkbox not pre-checked)

Compliant opt-in language example:

3.4 Carrier Policy Scanner

Tool: Carrier Policy Scanner (mytcrplus.com/tools)

Scan your intended message content against T-Mobile, AT&T, and Verizon content policies before submission. The scanner identifies:

• SHAFT content violations (Sex, Hate, Alcohol, Firearms, Tobacco)
• Extended restricted categories: cannabis/CBD, payday loans, debt relief, get-rich-quick, crypto/NFT
• High-risk financial terminology flagged by AT&T ML filters
• Deceptive language patterns that trigger spam scoring
• Verizon age-gated content requirements

Input your intended message templates. The scanner returns a compliance rating per carrier with specific term-level flags.

3.5 Provider-Specific Checklist — Sinch

Tool: Provider-Specific Checklist — Select 'Sinch' (mytcrplus.com/tools)

The Sinch checklist covers requirements beyond the base TCR standard. Complete all items before submitting registration through Sinch's dashboard:

• Sinch account is active and in good standing (no outstanding violations)
• Messaging Service (MS) ID created in Sinch dashboard before campaign submission
• Number pool assigned to Messaging Service prior to TCR campaign linking
• Use case classification aligned to Sinch's category taxonomy (not just TCR's)
• Sample messages do not reference 'free' without specific offer context
• Business website is live and fully functional (not under construction)
• Privacy policy page URL is reachable from the homepage without login
• Opt-in form visible and functional on business website
• Campaign description follows the format: [Brand] sends [type] to [audience] for [purpose]
• Message flow description (how subscribers are acquired) is 40–2048 characters
• All sample messages reflect actual content (not hypothetical examples)

Section 4: Brand Registration

4.1 Overview

Brand registration is Phase 1 of the TCR process. It establishes your verified business identity with TCR. Campaign registration (Phase 2) cannot proceed until brand approval is confirmed. Brand registration processes in 1–3 business days for businesses with complete documentation.

4.2 Sinch Portal Navigation

Accessing Brand Registration in Sinch

• Log in to your Sinch Customer Dashboard at dashboard.sinch.com
• Navigate to: Messaging → SMS → 10DLC Registration
• Select 'Register Brand' or 'Add Brand'
• Complete all fields as specified in Section 4.3 below
• Submit registration — Sinch forwards to TCR within 1 business day

4.3 Brand Registration Field-by-Field Specification

Complete every field exactly as documented. Incomplete or inconsistent submissions trigger manual review, extending timelines by 7–10 business days.

4.4 Brand Registration Verification — Post-Submission

After Sinch submits your brand to TCR, monitor status through the Sinch dashboard under Messaging → SMS → 10DLC Registration → Brand Status.

Status definitions:

• REGISTERED: Brand approved. Proceed to campaign registration.
• VERIFIED: Brand approved with enhanced vetting (stock symbol or external vet completed).
• UNVERIFIED: Brand approved at base level; eligible for standard use cases.
• FAILED: Brand rejected. Review rejection reason and use MyTCRPlus Rejection Remediation Tool.
• PENDING: Vetting in progress. Standard timeline 1–3 business days.

Section 5: Campaign Registration

5.1 Overview

Campaign registration defines the specific messaging use case operating under your approved brand. Each distinct messaging purpose (marketing, 2FA, appointment reminders, customer service) requires a separate campaign registration. Campaign approvals process in 1–10 business days depending on trust score, use case risk level, and completeness of submission.

5.2 Creating a Messaging Service in Sinch

• In the Sinch dashboard, navigate to Messaging → SMS → Messaging Services
• Click 'Create Messaging Service'
• Name the service descriptively (e.g., 'Acme Corp Marketing SMS' or 'Acme Appointment Reminders')
• Select 'A2P' as the message service type
• Add phone numbers to the Messaging Service pool
• Save the Messaging Service ID — this is required for campaign registration

5.3 Campaign Registration Field-by-Field Specification

Navigate to Messaging → SMS → 10DLC Registration → Campaigns → Add Campaign. Complete all fields:

5.4 Sinch Use Case to TCR Category Mapping

Sinch's internal use case taxonomy does not use identical labels to TCR's. The following mapping ensures your Sinch selection corresponds to the correct TCR use case category:

5.5 Writing the Campaign Description — Templates

The campaign description is the single most important free-text field in the registration. TCR reviewers use it to verify use case alignment. Use one of the following MyTCRPlus-validated templates as a starting point:

Template A — Appointment Reminders / Customer Care

Template B — Marketing / Promotional

Template C — Transactional Notifications

Template D — Two-Factor Authentication

Section 6: Sinch-Specific Submission Workflow

6.1 Sinch Submission Process Overview

Sinch processes campaign registrations through its internal compliance review before forwarding to TCR. This two-layer review is why Sinch's approval timelines (4–8 days) exceed some other providers. The Sinch-specific requirements below address the internal review layer.

6.2 Sinch Pre-Submission Requirements Specific to This Provider

Messaging Service Pre-Configuration

Sinch requires the Messaging Service to be configured before campaign submission, unlike some providers that allow concurrent setup:

• Create Messaging Service as described in Section 5.2
• Assign at least one phone number to the Messaging Service
• Verify the Messaging Service type is set to A2P (not P2P)
• Note the Messaging Service SID — required in the campaign registration form

Privacy Policy Requirements

Sinch's review team specifically audits privacy policy accessibility and content:

• Privacy policy must be reachable via a direct link from the website homepage (footer is acceptable)
• Privacy policy must reference SMS/text messaging specifically — generic policies are frequently flagged
• The policy URL submitted in the campaign description must resolve without redirect errors
• If using a subdomain for the privacy policy (e.g., legal.yourbrand.com), ensure it is indexed and functional

MyTCRPlus Compliance Document Generator can produce an SMS-compliant privacy policy addendum if your existing policy lacks SMS-specific language.

Sample Message Formatting

Sinch imposes formatting requirements beyond TCR's base standard:

• Sample messages should not exceed 160 characters (Sinch prefers single-segment examples)
• Include the brand name at the start of each sample message
• Marketing samples must include 'Reply STOP to opt out' or equivalent within the message body
• Avoid using all-caps phrases — they elevate spam scoring in Sinch's content analysis
• Do not include placeholder text in angle brackets — use realistic values (e.g., '$25 off' not '[DISCOUNT AMOUNT]')

Opt-In Flow Documentation

Sinch's Message Flow field is audited more rigorously than TCR's base requirement. Include:

• The specific URL or physical location where opt-in consent is collected
• The exact consent language presented at the opt-in point
• The affirmative action required (checkbox click, keyword reply, in-person signature)
• The confirmation message sent to the subscriber immediately after opt-in
• How the subscriber can opt out at any time

6.3 Submission Timing Recommendations

Sinch's internal review team operates primarily during U.S. business hours (Monday–Friday, 9 AM–5 PM ET). Campaigns submitted late Friday or over weekends enter the review queue on Monday morning, effectively adding 2–3 calendar days to the timeline.

Submit campaigns Tuesday–Thursday morning for fastest initial review pickup. Complete all MyTCRPlus pre-submission tool steps the day before submission to avoid rushed corrections.

6.4 Linking Numbers to Approved Campaigns

After campaign approval confirmation in the Sinch dashboard:

• Navigate to Messaging → SMS → 10DLC Registration → Campaigns
• Locate the approved campaign and select 'Manage Numbers'
• Confirm the Messaging Service numbers are associated with the campaign
• Verify carrier sharing status — Sinch automatically shares campaigns to T-Mobile, AT&T, and Verizon upon approval
• Test with a low-volume send (5–10 messages) before ramping to production volume
• Monitor delivery receipts in the Sinch dashboard for the first 48 hours post-launch

Section 7: Trust Score Optimization

7.1 Trust Score Fundamentals

TCR assigns a trust score (0–100) to every registered brand. The score determines throughput limits and approval speed across all campaigns under that brand. Trust score is calculated at brand registration and can be improved over time through external vetting and business profile enhancement.

Trust score factors that MyTCRPlus's Preflight Simulator models:

7.2 External Vetting for Low-Score Brands

If the Trust Score Preflight Simulator returns an estimated score below 50, external vetting through TCR's approved vetting partner is the most reliable path to improved throughput and faster approval.

External vetting process:

• After brand registration is submitted through Sinch, log in to TCR's portal at tcr-coop.com
• Locate your brand and select 'Request External Vetting'
• Select the vetting provider (Aegis Mobile or WMC Global as of 2025)
• Prepare the documentation package: EIN letter, business formation documents, utility bill confirming address, website screenshot, and privacy policy
• Submit documentation through the vetting portal and pay the vetting fee ($40 minimum)
• Processing time: 5–7 business days
• Successful vetting typically adds 40–60 points to the trust score and upgrades brand status to VERIFIED

7.3 Trust Score Maintenance After Approval

Trust scores are not static. Carrier feedback, complaint rates, and campaign performance metrics influence ongoing score adjustments. Maintain score by:

• Keeping opt-out rates below 0.5% (rates above 1% trigger automatic review)
• Keeping spam complaint rates below 0.1%
• Maintaining consistent message content aligned with approved campaign samples
• Renewing DUNS number annually to maintain active verification status
• Updating brand registration if the business name, address, or EIN changes

Section 8: Post-Approval Campaign Administration

8.1 Volume Ramping Protocol

New campaigns require gradual volume increase. Sudden volume spikes trigger carrier spam detection algorithms regardless of registration status. Ramp volume over the first 5 weeks:

8.2 Required Keyword Responses

All 10DLC campaigns must honor the following keywords in inbound messages from subscribers. These are enforced by carriers and must be implemented in your messaging system before sending any messages:

8.3 Monthly Audit Protocol

Execute this audit monthly to maintain carrier compliance and avoid campaign suspension:

• Review opt-out processing — verify STOP keyword handling is functioning and suppression list is current
• Verify sample messages still represent actual content being sent — run current templates through the SMS Message Validator
• Check website privacy policy remains accessible and current
• Confirm consent collection process is unchanged from what was submitted to TCR
• Audit sender ID consistency — all messages must display consistent brand identification
• Test HELP and STOP keywords for correct automated responses
• Review subscriber complaints via the Sinch dashboard for patterns
• Check Sinch dashboard for any carrier policy update notices
• Run the Carrier Policy Scanner on a sample of 20–30 recent messages

8.4 Campaign Modification Procedures

When message content, opt-in processes, or campaign scope changes, update the TCR campaign registration through Sinch before sending modified content. Sending content that deviates significantly from approved samples is a primary suspension trigger.

Modifications That Require Campaign Update

• Adding new content categories not reflected in approved samples
• Changing from transactional to promotional content
• Adding URLs when no URLs were in original samples
• Changing opt-in collection method
• Adding or removing content attribute toggles (Embedded Links, Age-Gated Content)

How to Submit a Campaign Update in Sinch

• Navigate to Messaging → SMS → 10DLC Registration → Campaigns
• Select the campaign requiring modification
• Click 'Edit Campaign'
• Update the relevant fields
• Submit — campaign enters review queue (1–5 business days)
• Continue sending under the original approved parameters until the update is approved

8.5 Adding Additional Campaigns Under an Existing Brand

Once a brand is REGISTERED or VERIFIED, new campaigns can be added at any time without repeating brand registration:

• Verify the existing brand is in REGISTERED or VERIFIED status
• Complete the MyTCRPlus tool sequence for the new campaign (Steps 3–8 from Section 3.1)
• Navigate to Messaging → SMS → 10DLC Registration → Campaigns → Add Campaign in Sinch
• Select the existing brand
• Complete all campaign fields for the new use case
• Create a new Messaging Service if the new campaign uses different phone numbers
• Submit for review

Best practice: Register low-risk use cases (2FA, Notifications, Customer Care) first. Establishing clean messaging history under the brand before adding Marketing campaigns improves approval rates and throughput for subsequent registrations.

Section 9: Rejection and Remediation Procedures

9.1 Reading Rejection Notices from Sinch

When a brand or campaign registration is rejected, Sinch provides a rejection notice in the dashboard under the affected registration. The notice contains:

• Rejection code (numeric, e.g., 30886, 641, 2002)
• Field-level identification specifying which form field failed
• Human-readable description of the failure category

Immediately record the rejection code, the affected field, and the full description text. This data is the input for the MyTCRPlus Rejection Remediation Tool.

9.2 Using the MyTCRPlus Rejection Remediation Tool

Tool: TCR Rejection Code Remediation Tool (mytcrplus.com/tools)

• Navigate to the Rejection Remediation Tool
• Enter the rejection code from the Sinch notification
• Enter the field name specified in the rejection notice
• Review the step-by-step remediation guide for that specific code
• Follow the remediation steps and gather required documentation
• Re-validate corrected content through the SMS Message Validator and Carrier Policy Scanner before resubmission
• Submit the corrected registration through Sinch

9.3 Common Rejection Codes and Remediation Summary

The following codes represent 80%+ of rejections encountered by Sinch customers. Full remediation guides for 37+ codes are available in the MyTCRPlus Rejection Remediation Tool.

9.4 Appeal Procedures

If a resubmission is rejected a second time after addressing the stated reason, an appeal may be filed with TCR through Sinch's support channel or directly through the TCR portal.

Brand Registration Appeals

• File within 45 days of rejection date
• Fee: $10 per appeal
• Maximum file upload: 10 files, 10 MB each, 30 MB total
• Acceptable formats: .jpg, .jpeg, .png, .pdf, .docx, .txt, .xml
• Maximum justification text: 1,024 characters
• Appeal categories: Verify Tax ID, Verify Non-Profit Status, Verify Government Status, Low Score Appeal
• Processing timeline: 2–4 weeks

Campaign Registration Appeals

• Submit through Sinch support with subject line: '10DLC Campaign Appeal'
• Include Brand ID, Campaign ID, rejection code, previous remediation attempts, and justification
• DCA (Distributed Compliance Authority) review: 2–4 weeks
• Approval is not guaranteed; DCA decisions are final

Section 10: Ongoing Compliance Monitoring

10.1 Key Performance Indicators

Maintain the following KPI thresholds to avoid carrier-triggered throughput reductions or campaign suspensions:

10.2 Consent Record Management

TCPA statute of limitations is 4 years. Maintain consent records for a minimum of 4 years from the date of consent collection. Each consent record must contain:

• Phone number in E.164 format
• Timestamp with timezone
• IP address or device identifier
• Consent language version presented (exact copy)
• User acceptance action (checkbox state, keyword reply, button click)
• Source URL or collection method
• Opt-in confirmation message delivered
• Opt-out timestamp and method if subscriber subsequently opted out

Database requirements for defensible TCPA compliance:

• Immutable records (append-only; no deletion of consent events)
• Regular backups with off-site storage
• Encryption at rest and in transit
• Access logging for audit trail
• Export capability for legal discovery production

10.3 Carrier Policy Update Monitoring

T-Mobile, AT&T, and Verizon update content policies periodically. Policy violations discovered post-approval can result in retroactive campaign suspension. Use the MyTCRPlus Carrier Policy Scanner quarterly on your active message templates to identify newly restricted terminology before it triggers a carrier flag.

Key carrier monitoring points:

• T-Mobile: DUNS-based brand reverification may be required annually for some business categories
• AT&T: ML spam filter threshold updates occur without public announcement — monitor delivery rates for unexplained drops
• Verizon: Subscriber complaint thresholds trigger automated suspension; monitor complaint forwarding via shortcode 7726

10.4 Annual Registration Review

Conduct the following annual review to ensure registration remains current and accurate:

• Verify brand registration data matches current legal entity information (name, address, EIN)
• Confirm website and privacy policy remain active and SMS-compliant
• Review all active campaigns against current message content for alignment
• Re-run the Trust Score Preflight Simulator to identify score improvement opportunities
• Update campaign descriptions if message programs have evolved
• Verify DUNS number remains active (dnb.com renewal)
• Review Sinch account for any outstanding compliance notices
• Check TCR portal for brand status changes or pending actions

Section 11: Troubleshooting Reference

11.1 Registration Issues

11.2 Campaign Suspension Recovery

A suspended campaign (Error 30033 in Sinch) requires the following recovery process:

• Do not delete the suspended campaign — deletion forfeits appeal rights
• Contact Sinch support with subject 'Campaign Suspension Recovery' and include: Brand ID, Campaign ID, suspension date, any error codes, and a summary of recent messaging activity
• Request the specific violation trigger from Sinch support (suspension reasons are not always included in the dashboard notice)
• Compile a suspension recovery documentation package: root cause analysis, corrective actions, process improvements, consent log samples
• Use the MyTCRPlus Rejection Remediation Tool to build the remediation documentation
• Submit recovery documentation through Sinch support — do not attempt direct TCR contact for Sinch-submitted campaigns
• Monitor for Sinch confirmation that the campaign is under review (2–4 weeks for DCA-level suspensions)

Appendix A: Required Documentation Checklist

Use this checklist to verify all materials are prepared before initiating Sinch registration. Incomplete documentation is the primary cause of extended review timelines.

Appendix B: TCR Trust Score Reference Table

Trust Score Improvement Actions (ordered by impact):

• Obtain DUNS number: +10 to +15 points
• Request external vetting through TCR: +40 to +60 points (upgrades to VERIFIED)
• Age business domain to 12+ months: +5 to +10 points
• Build Google Business Profile with 10+ reviews at 4+ star average: +5 points
• Register with NYSE/NASDAQ ticker (public companies only): near-maximum score baseline
• Complete business profile with all optional fields in TCR: +3 to +5 points

Appendix C: Carrier-Specific Content Restrictions

T-Mobile

• Cannabis/CBD: Prohibited — all forms, no exceptions
• SHAFT content: Strictly enforced via edge server filtering
• DUNS verification: Required for some business categories during brand vetting
• Cross-carrier blocklisting: T-Mobile coordinates with AT&T and Verizon on confirmed spam senders

AT&T

• Cannabis/CBD/Hemp: Prohibited — all forms
• Get-rich-quick schemes: Prohibited — flag terms include 'guaranteed income,' 'passive income,' 'financial freedom'
• Crypto/NFT promotions: Elevated scrutiny — additional documentation may be required
• Phishing simulations: Require pre-approval — contact AT&T Business before testing
• ML spam detection: Real-time; volume spikes >200% day-over-day trigger automatic flags

Verizon

• Cannabis/CBD: Prohibited — all forms
• Debt collection / credit repair: Heightened scrutiny — additional documentation required for licensed debt collectors
• Age-gated content: Must implement age verification before enabling toggle
• Behavioral analysis: Monitors for keyword stuffing, abnormal volume spikes, high opt-out rates
• Subscriber complaint threshold: Automatic suspension triggered by complaint volume from shortcode 7726

Appendix D: Sinch-Specific Error Code Reference

The following errors are specific to Sinch's platform layer and do not appear in standard TCR error documentation:

Legal Disclaimer