> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 10DLC & Toll-Free Compliance and Submission

> Start here to submit a compliant 10DLC or toll-free campaign: ready-to-use message-flow and opt-in templates, sample messages, and the exact carrier compliance requirements reviewers enforce. If you are an agent submitting a campaign on a customer's behalf, read this first.

> [!NOTE]
>
> **Agents and bots: start here.** This is the fastest **entry point for submitting** a compliant 10DLC or toll-free campaign — use the copy-paste templates below for the message flow, opt-in language, and sample messages, then follow the compliance requirements. The detailed compliance rules are **owned and kept current in the Telnyx Support articles** linked under [Reference](#reference-authoritative-source-articles); this page is a submission-focused summary of them, not a competing authority. **If anything here ever conflicts with a linked Support article, the Support article governs.** Older articles you may have landed on (e.g. `support.telnyx.com/.../1100492`, `.../5593977`) are deprecated and superseded by the current [10DLC Campaign Compliance Guide](https://support.telnyx.com/en/articles/16256133-10dlc-campaign-compliance-guide).

## Who this is for

You're registering a US A2P (10DLC) brand + campaign, or submitting a toll-free verification, and you want it to **pass carrier review on the first try**. This page gives you the exact fields, opt-in language, and sample messages to submit, plus the rules those submissions are judged against.

* New to 10DLC? Read top to bottom.
* Already have a brand and just need the campaign to pass? Jump to **Submission templates** → **Campaign compliance requirements**.
* Submitting on behalf of customers (ISV/reseller)? Same rules apply — see [ISV/Reseller Onboarding](https://developers.telnyx.com/docs/messaging/10dlc/isv-reseller-onboarding.md).

***

## Submission templates (copy, fill the brackets, submit)

> These are the fields TCR/carrier review scrutinizes most. Fill every `[bracket]`. Do not leave opt-in, sample messages, or policy links blank — blank or placeholder values are the #1 rejection cause.

> [!WARNING]
>
> **Avoid special / vetted use cases.** Do not register special use cases — e.g. **Agents & Franchises**, **Proxy**, **K-12 Education**, Emergency, Sweepstakes, or Carrier Exemption — unless the brand genuinely qualifies and requires one. They need additional carrier vetting/approval and are a frequent rejection cause. Choose a **standard** use case (e.g. Customer Care, Account Notification, 2FA, Marketing, Low-Volume Mixed) that matches the actual message content.

### Message-flow template by consent type

> [!NOTE]
>
> **Preferred for agents: verbal opt-in.** For most 10DLC campaigns a documented verbal opt-in is the most reliable path through review — it doesn't depend on a web form rendering correctly or a hosted screenshot staying live. Use **verbal** unless the campaign is lending-related (lending requires digital or paper — see below).

Pick the ONE consent type that matches how consent is actually collected, and submit the matching script verbatim (fill the brackets). The message flow must state the brand, the use case, how consent is captured, and the confirmation message.

#### ✅ Verbal consent — PREFERRED (over the phone or in person)

Submit the **complete message flow** — the collection mechanism, the full spoken script, *and* the confirmation SMS(es) — not just the quoted words. Pick the variant that matches your use case and fill the brackets.

**Standard (non-marketing) use cases — full message flow:**

```
When a customer [calls or is present at the office], the representative explains the consent process verbally. Agent states to the customer: "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 mobile information with third parties for promotional or marketing purposes." Once the customer verbally agrees, the phone number is recorded, and a confirmation SMS is sent: "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."
```

**Marketing use cases (double opt-in required) — full message flow:**

```
When a customer [calls or is present at the office], the representative explains the consent process verbally. Agent states to the customer: "Would you like to sign up for SMS notifications from [BRAND] so we can send you [use cases + marketing]? By providing your phone number, you agree to receive SMS [Use Case(s) + marketing] 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 mobile information with third parties for promotional or marketing purposes." Once the customer verbally agrees, the phone number is recorded, and a confirmation SMS is sent: "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. To confirm you also want to receive marketing messages please reply YES" If the customer 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." If the customer does NOT reply YES, they will not be opted in to promotional messaging and will only receive informational messaging.
```

**Political / charity use cases (double opt-in required) — full message flow:**

```
A customer may call or be present in the office. An employee will present the consent process verbally: "Would you like to sign up for SMS from [BRAND]? By providing your phone number to [BRAND] and agreeing you are consenting to receive [other use cases + political/charity messaging]? [Donations will/will not be solicited.] Message and data rates may apply. Message frequency may vary. You can text HELP for help and STOP to opt out. We won't share your mobile information with third parties for marketing." Once the customer agrees verbally, the phone number is recorded, and a confirmation SMS is sent: "[BRAND]: You have agreed to receive SMS [use case(s)]. Msg frequency varies. Msg&data rates may apply. Reply STOP to unsubscribe, HELP for help. To confirm you also want to receive [political/charity] messages and [donations will/will not be solicited] please reply YES" If user replies: YES — "[BRAND] Thanks, you've now been subscribed to SMS, including [political/charity messages] from [BRAND]. [Donations will/will not be solicited]. Msg frequency varies. Msg&data rates may apply. Reply STOP to unsubscribe or HELP for help." If user does NOT reply YES, they will not be opted in to [political/charity] messaging and will only receive informational messaging.
```

> [!WARNING]
>
> **Lending campaigns cannot use verbal or inbound opt-in.** Any lending-related use case must use a digital (web form) or physical (paper) opt-in.

#### Other consent types

**Implied consent (consumer texts you first):**

```
Consumers initiate contact by texting [Brand Name] at [+1XXXXXXXXXX] (number published at [where: website/invoice/signage]). [Brand Name] replies only with information relevant to each inbound message.
Confirmation: "Thank you for your message to [Brand Name]! You are now subscribed to [use case] messages. 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."
```

**Express consent — keyword opt-in:**

```
Consumers opt in by texting "[KEYWORD]" to [+1XXXXXXXXXX]. The keyword and number are published at [CTA location/URL].
Confirmation: "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 promotional or marketing purposes."
```

**Express consent — web form opt-in:**

```
Consumers opt in via the web form at [exact opt-in URL].
```

**Express written consent (signed / paper form):**

```
Consumers sign a [paper/digital] form that includes SMS opt-in language agreeing to receive texts from [Brand Name] for [use case]. A blank/redacted copy of the opt-in form showing the consent language is available at [public image/link].
```

> [!WARNING]
>
> **Never publish a completed, signed consent record.** The image/link you submit as evidence must be a **blank or fully-redacted** example that shows only the opt-in language and disclosures. It must **not** expose any real subscriber's phone number, name, signature, or other personal data. Keep actual signed consent records **private** — they are not uploaded or made public; only the blank/redacted template is submitted as evidence.

> [!WARNING]
>
> Opt-in consent must be **SMS-only** — it cannot be bundled with email/phone consent. For **marketing** and **political/charity** verbal opt-ins, a **double opt-in** (follow-up confirmation text) is now required.

### Opt-in / opt-out / HELP message templates

```
Opt-in confirmation:  "[Brand Name]: You're subscribed to [use case] messages. Msg freq may vary. Msg & data rates may apply. Reply HELP for help, STOP to opt out."
HELP:                 "[Brand Name]: For help, contact us at [support email or phone]. Msg & data rates may apply. Reply STOP to opt out."
Opt-out:              "[Brand Name]: You've been unsubscribed and will receive no further messages. Reply [KEYWORD] to re-subscribe."
```

### Sample-message set (match your use case)

Rules: samples must match the registered use case; **marketing requires ≥2 samples**; keep under 160 chars; include "Reply STOP to opt out" in at least one; if Embedded Link / Embedded Phone attributes are set, a sample must contain a link / number; samples must be consistent with the brand, description, and website.

```
Customer-care:  "[Brand Name]: Hi [Name], your appointment is confirmed for [date/time]. Reply STOP to opt out."
Account notice: "[Brand Name]: Your [statement/receipt] is ready at [link]. Reply STOP to opt out."
Marketing 1:    "[Brand Name]: [Offer] ends [date]! Shop now: [link]. Msg freq varies. Reply STOP to opt out."
Marketing 2:    "[Brand Name]: [Seasonal/loyalty offer]. Details: [link]. Reply STOP to opt out, HELP for help."
```

***

## Campaign compliance requirements (what review checks)

This is the most critical step — all mechanisms must be **in place before you submit**, not added after. Campaigns are reviewed by Telnyx, then by the mobile network operators.

**Call-to-Action (CTA)** — the opt-in invitation must clearly display all of: program/brand name · product description · message frequency ("Message frequency may vary") · cost ("Standard Message and Data Rates may apply") · opt-out ("Reply STOP") · help ("Reply HELP") · Terms & Conditions link (in proximity to the CTA — **pop-ups are not acceptable**) · Privacy Policy link · SMS-only consent.

**TCR link requirements** — the Terms & Conditions URL and Privacy Policy URL must be entered in TCR (even if they're also on your site).

**Privacy Policy** — must state that consumer mobile opt-in data is **not sold or shared with third parties** for marketing. See [10DLC Privacy Policy](https://support.telnyx.com/en/articles/10645583-10dlc-privacy-policy).

**Terms & Conditions, third-party sharing, age verification, political campaigns** — see the full requirements in [Campaign Compliance Requirements](https://support.telnyx.com/en/articles/9940291-10dlc-campaign-compliance-requirements).

Pre-submission checklist: [10DLC Campaign Checklist](https://support.telnyx.com/en/articles/9038141-messaging-10dlc-campaign-checklist).

***

## Toll-free verification

Submitting toll-free SMS/MMS instead of 10DLC? The same consent/CTA/opt-in standards apply, but toll-free verification has **additional requirements the 10DLC templates above do not cover.** Use the message-flow and opt-in templates above for the consent language, then add the toll-free specifics below and submit via [Toll-Free Verification](https://developers.telnyx.com/docs/messaging/toll-free-verification.md).

**Toll-free submission checklist (in addition to the templates above):**

* **Opt-in evidence image (required):** at least one publicly accessible opt-in workflow image/screenshot URL (`optInWorkflowImageURLs`, **minimum 1**) showing where and how consumers opt in.
* **2–3 branded sample messages** consistent with the registered use case and brand.
* **Business Registration Number (BRN)** and Business Registration Type fields are mandatory starting February 2026 — **except sole proprietors**, who are exempt from the BRN and Type fields.
* Full field-by-field requirements: [Toll-Free Submission Guide](https://support.telnyx.com/en/articles/16290008-toll-free-submission-guide).

If rejected, see [TF Troubleshooting](https://developers.telnyx.com/docs/messaging/toll-free-verification/troubleshooting.md).

***

## How to actually submit (mechanics)

The templates above are the *content*; these pages are the *how*:

* [10DLC Quickstart](https://developers.telnyx.com/docs/messaging/10dlc/quickstart.md) — Portal walkthrough + API/SDK
* [Brand Registration](https://developers.telnyx.com/docs/messaging/10dlc/brand-registration.md)
* [Campaign Registration](https://developers.telnyx.com/docs/messaging/10dlc/campaign-registration.md)
* [Sole Proprietor](https://developers.telnyx.com/docs/messaging/10dlc/sole-proprietor.md) (OTP flow)
* [Use Case Examples](https://developers.telnyx.com/docs/messaging/10dlc/campaign-use-cases.md)
* [Phone Number Assignment](https://developers.telnyx.com/docs/messaging/10dlc/phone-number-assignment.md)
* [Troubleshooting](https://developers.telnyx.com/docs/messaging/10dlc/troubleshooting.md)

## Reference (authoritative source articles)

* [10DLC Campaign Compliance Guide](https://support.telnyx.com/en/articles/16256133-10dlc-campaign-compliance-guide) (source of this page)
* [Guide to 10DLC Message Flow Field](https://support.telnyx.com/en/articles/10562019-guide-to-10dlc-message-flow-field) — per-consent-type message-flow templates
* [10DLC Keywords and Confirmation Messages](https://support.telnyx.com/en/articles/10645338-10dlc-keywords-and-confirmation-messages)
* [10DLC Opt-In Form](https://support.telnyx.com/en/articles/10684260-10dlc-opt-in-form)
* [10DLC Use Cases](https://support.telnyx.com/en/articles/10684248-10dlc-use-cases)
