[TCR] 10DLC Verification Registration in Phone2

10DLC Verification Registration in Phone2

This article explains how to complete the 10DLC (10‑Digit Long Code) campaign registration for Phone2 using TCR (The Campaign Registry). It guides you through submitting correct brand and campaign data, with a special focus on crafting a compliant Message Flow—an essential part of submission. Be sure to stay within character limits and include proper disclaimers to avoid delays.

What is 10DLC?

10DLC (10‑Digit Long Code) is a US mobile carrier standard for business SMS messaging. It enhances transparency, reduces spam, and boosts deliverability for A2P (Application-to-Person) traffic. All messages sent from 10DLC numbers must be registered via The Campaign Registry (TCR) to verify brand identity and purpose.

Registration Process Overview

There are two main stages for registration:

1. Brand Registration

Registers your business (linked to your EIN or local ID) as a recognized brand.

2. Campaign Registration

Details the messaging use case, including the Message Flow, keywords, and sample messages. SMS may be enabled temporarily once the brand is validated, while campaign review is in progress.

Information Required for Registration

Brand Information

Field	Description
Entity	Legal entity type your brand represents.
Vertical	Industry category.
Display Name	DBA/trade name (required even if same as company name).
Company Name	Legal business name (must match EIN records).
EIN	Employer Identification Number (U.S.) or equivalent.
Tax Issuing Country	Country issuing the EIN or local equivalent.
Contact Phone	Authorized representative’s phone number.
Business Contact Email	Individual’s email—not a group alias.
Website	Business website URL.
Country	Legal registration country.
State/Region	State or region (U.S. use 2-letter codes).
Business Address	Full legal address, matching IRS/EIN records.

Campaign Information

Field	Description
Campaign Description	Summary of what the campaign is intended for.
Call-to-Action / Message Flow	Full description of how users opt in, receive, help, and opt out—see expanded section below.
Privacy Policy Link	A publicly accessible link.
Terms & Conditions Link	A publicly accessible link.
Sample Messages	1 per use case; 2 for marketing; mixed needs at least one per sub-use case.
Opt-in, Opt-out, Help Keywords	Required: START, STOP, HELP. You may include custom ones.

Expanded Message Flow Requirements

The Message Flow field (also known as CTA/Message Flow) is one of the most rigorously reviewed and error-prone parts of the submission. Our telecom provider requires this field to be between 40 and 2,048 characters in length, so be sure your content meets this limit.

You must clearly document how subscribers opt in, using one of the following templates. Choose the method matching your actual process and customize the placeholders:

The user navigates to [Brand Name]'s [website] and subscribes via a specific opt‑in page at [URL or page path] (see screenshot [link]).

The opt‑in form clearly states:

"By providing your phone number and clicking 'Submit,' you agree to receive SMS [update type] from [Brand Name]. Message frequency may vary. Standard Message and Data Rates may apply. Reply STOP to opt out. Reply HELP for help. Consent is not a condition of purchase. [Privacy Verbiage such as: Your mobile information will not be sold or shared with third parties for promotional or marketing purposes.] [Link to Privacy Policy]."

A customer [calls or visits] [published phone number or office address]. The representative states:

"By providing your phone number, you agree to receive SMS [Use Case(s)] from [Brand Name]. Message frequency may vary. Standard Message and Data Rates may apply. Reply STOP to opt out. Reply HELP for help. We will not share your mobile information with third parties for marketing purposes."

After consent, the user receives a confirmation SMS:

"You have agreed to receive SMS updates from [Brand Name]. Msg freq may vary. Std msg & data rates apply. Reply STOP to opt out, HELP for help."

For marketing use cases, you may include a second confirmation flow:

"[BRAND]: You have agreed to receive SMS updates. Msg frequency varies. Msg&data rates may apply. Reply STOP to unsubscribe, HELP for help. To confirm you also want to receive marketing messages please reply YES"

Then if user replies “YES”:

"[BRAND]: Thanks, you’ve now been subscribed to SMS notifications, including promotions from [BRAND]. Msg frequency varies. Msg&data rates may apply. Reply STOP to unsubscribe or HELP for help."

The user completes a paper form during [appointment/onboarding] at [address], learned via [website/social/etc.]. The form states:

"By signing this form and providing your phone number, you agree to receive SMS [Use Case(s)] from [Brand Name]. Message frequency may vary. Standard Message and Data Rates may apply. Reply STOP to opt out. Reply HELP for help. Consent is not a condition of purchase. Your mobile information will not be sold or shared with third parties for promotional or marketing purposes."

The user then receives a confirmation SMS:

"Thank you for signing up for SMS updates from [Brand Name]. Msg freq may vary. Std msg & data rates apply. Reply STOP to opt out, HELP for help."

4. Opt‑In by Keyword (e.g., SMS Opt-In)

The brand publishes a keyword (e.g., "START") and a number (e.g., 123456) via [website, flyer, QR code]. When the user texts "[Keyword]":

"Thank you for opting in to [Brand Name] SMS [update type]! Msg freq may vary. Std msg & data rates apply. Reply STOP to opt out, HELP for help. Your mobile information will not be sold or shared with third parties for marketing purposes."

5. Inbound Message to Opt In

The brand provides a number via [website, flyer, QR code, email signature]. When the user sends a message to that number:

"Thank you for your message to [Brand Name]! We will be with you shortly. Msg freq may vary. Std msg & data rates apply. Reply STOP to opt out, HELP for help. We will not share or sell your mobile information for marketing/promotional purposes."

Important Error to Avoid: If your registration is rejected with a TCR Error (806), it means your Message Flow field lacks specific opt‑in paths, required disclaimers, or links to your privacy policy. You must include all of these to pass compliance.

Keywords & Confirmation Messages

Campaign fields for keywords and autoresponses must follow prescribed format:

Opt-in Keyword: e.g., START
Opt-in Confirmation Message:
[Brand Name]: Thanks for subscribing to [Use Case(s)]! Reply HELP for help. Message frequency may vary. Msg&data rates may apply. Consent is not a condition of purchase. Reply STOP to opt out.
Opt-out Keyword: e.g., STOP
Opt-out Confirmation Message:
[Brand Name]: You are unsubscribed and will receive no further messages.
Help Keyword: e.g., HELP
Help Confirmation Message:
[Brand Name]: Please reach out to us at [website/email/phone number] for help.

Common Issues that Delay Verification

Message Flow field too short (<40) or too long (>2,048 characters).

Missing disclaimers: message frequency, data rates, opt‑out instruction, privacy policy link.

No screenshot or URL showing where opt‑in occurs (for digital forms).

Keywords or sample messages not matching registered use case.

Required keywords (START, STOP, HELP) omitted or formats incorrect.

After Submission

Brand verification may enable trial SMS usage.

Campaign review continues with TCR and carriers.

If issues arise, you’ll receive instructions for edits or appeals.

Tip: Carefully map out your Message Flow. Choose the method that mirrors your actual opt-in process, fill all placeholders, check character length, and include a link or screenshot when submitting. This will significantly reduce rejection risk and streamline your 10DLC registration.

Updated on: 22/09/2025

Was this article helpful?

Thank you!