Skip to main content
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; 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.

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.

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.
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.
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. 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:
Marketing use cases (double opt-in required) — full message flow:
Political / charity use cases (double opt-in required) — full message flow:
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.
Implied consent (consumer texts you first):
Express consent — keyword opt-in:
Express consent — web form opt-in:
Express written consent (signed / paper form):
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.
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

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.

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. Terms & Conditions, third-party sharing, age verification, political campaigns — see the full requirements in Campaign Compliance Requirements. Pre-submission checklist: 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. 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.
If rejected, see TF Troubleshooting.

How to actually submit (mechanics)

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

Reference (authoritative source articles)