Integrasikan API Verifikasi SMS (V3) dengan Pusat Pesan
π Pelajari cara mengotentikasi pengguna dengan SMS OTP API menggunakan Message Central di NodeJS, Python, Java, PHP, Ruby, dan C#!
1. Kerangka Regulasi
| Dialing Code | +91 |
|---|---|
| Country Name | Republic of India (Bharat) |
| ISO Code | IN |
| Dialing Code | +91 |
| Region | Asia (South Asia) |
| Mobile Country Code (MCC) | 404 (BSNL, Airtel, Jio, Vi, others) and 405 (Airtel, Jio, Vi, BSNL, Vodafone) |
| Population (Mobile Subscribers) | ~1.18 billion mobile subscribers β world's second-largest mobile market |
| Time Zone | IST β Indian Standard Time (UTC+5:30). No Daylight Saving Time. Entire country is a single time zone. |
| Two-Way SMS Supported | Yes |
| Number Portability Available | Yes β Mobile Number Portability (MNP) fully operational |
| Concatenated Messages Supported | Yes* β with caveats depending on Sender ID type |
| Message Length (Single SMS) | 160 characters (GSM-7) or 70 characters (UCS-2/Unicode) |
| MMS Support | Converted to SMS with embedded URL β no native MMS delivery from international platforms |
| Sending to Landline Numbers | Not possible β API throws error 21614; account not charged |
| Primary Gateway Options | Domestic (DLT-registered, via Indian TSPs) and International (via ILDO connections) |
| Key Regulatory Body | TRAI β Telecom Regulatory Authority of India |
| Primary Regulation | TCCCPR 2018 (Telecom Commercial Communications Customer Preference Regulations), last amended February 12, 2025 |
| Mandatory DLT Registration | Yes β for ALL domestic commercial SMS. Required since February 28, 2019. |
| International Route Available | Yes β ILDO route; no DLT required; bypasses DND; different restrictions apply |
2. Kerangka Regulasi
India memiliki salah satu ekosistem regulasi SMS komersial yang paling terstruktur dan berteknologi canggih di dunia. Pada intinya adalah TCCCPR 2018 β kerangka kerja bertenaga blockchain yang mengatur setiap pesan komersial yang dikirim ke pelanggan seluler India. Memahami kerangka kerja multi-layer ini sangat penting sebelum SMS tunggal dikirim.
2.1 TRAI - Otoritas Pengatur Telekomunikasi India
Otoritas Pengatur Telekomunikasi India (TRAI), didirikan berdasarkan Undang-Undang TRAI 1997, adalah otoritas pengatur puncak untuk telekomunikasi di India. TRAI mengeluarkan peraturan, arahan, dan perintah yang mengatur A2P SMS dan komunikasi komersial. Instrumen utamanya untuk kepatuhan SMS adalah Telecom Commercial Communications Customer Preference Regulations (TCCCPR), pertama kali diberlakukan pada tahun 2018 dan diubah secara signifikan pada Februari 2025
Referensi: Situs Resmi TRAI | Halaman TRAI TCCCPR
2.2 TCCCPR 2018 - Kerangka Inti (Diubah 12 Februari 2025)
Peraturan Preferensi Pelanggan Komunikasi Komersional Telekomunikasi (TCCCPR), 2018 diberitahukan pada 19 Juli 2018 dan mulai berlaku penuh pada 28 Februari 2019. Mereka menggantikan TCCCPR 2010 sebelumnya. TCCCPR 2018 adalah instrumen hukum utama India untuk mengatur SMS komersial dan komunikasi suara dan terkenal secara global sebagai kerangka peraturan telekomunikasi pertama di dunia yang menerapkan teknologi blockchain (Distributed Ledger Technology/DLT) untuk tata kelola komunikasi komersial.
Peraturan ini memiliki tujuan ganda: melindungi konsumen dari Komunikasi Komersional yang Tidak Diminta (UCC/spam), sambil memungkinkan bisnis yang sah untuk berkomunikasi dengan pelanggan yang telah menyetujui atau menetapkan preferensi yang sesuai.
Tonggak penting dalam evolusi TCCCPR:
- 19 Juli 2018: TCCCPR 2018 diberitahukan - adopsi DLT yang diamanatkan, pendaftaran Pengirim/Entitas Utama, daftar putih templat.
- 28 Februari 2019: Penegakan penuh dimulai.
- November 2020: Batas waktu pendaftaran DLT wajib untuk semua entitas yang mengirim SMS komersial.
- 1 Februari 2021: Penggosokan template sepenuhnya diberlakukan β templat yang tidak terdaftar diblokir di tingkat jaringan.
- 1 Oktober 2024: CTA (Call-to-Action) Whitelisting dan Variable Tagging diamanatkan β semua URL/tautan dalam pesan harus disetujui sebelumnya; semua variabel template harus diberi tag sebelumnya.
- 12 Februari 2025: Amandemen utama - sistem akhiran kategori pesan baru (-P, -S, -T, -G), kategori Layanan Eksplisit dihentikan, mekanisme pengaduan UCC yang lebih ketat, otentikasi biometrik ditambahkan ke pendaftaran, penerapan honeypot diamanatkan.
- 6 Mei 2025: Aturan akhiran header efektif - semua header SMS secara otomatis membawa akhiran -P, -S, -T, atau -G ditambahkan oleh TSP selama penggosokan DLT.
Referensi: Teks Asli TCCCPR 2018 (TRAI) | Amandemen TCCCPR 2025 - Lembaran Resmi
2.3 DLT - Mesin Blockchain yang Memberdayakan Ekosistem SMS India
Teknologi Buku Besar Terdistribusi (DLT) adalah platform berbasis blockchain yang mendukung semua SMS A2P domestik di India. Setiap entitas yang mengirim SMS komersial di India β baik bank, perusahaan e-commerce, rumah sakit, atau startup β harus terdaftar pada platform DLT yang dioperasikan oleh salah satu operator telekomunikasi resmi India. Platform DLT:
- Mencatat semua pendaftaran Entitas Utama (PE) dan ID Entitas unik
- Memelihara registri terpusat dari semua Header SMS yang disetujui (ID Pengirim)
- Memelihara registri semua Templat Konten dan Templat Persetujuan yang disetujui
- Menjalankan pembersihan real-time dari setiap SMS komersial yang keluar terhadap preferensi DND, header yang disetujui, dan templat yang disetujui
- Menyinkronkan data di semua platform DLT operator β jadi pendaftaran sekali mencakup semua jaringan
- Mencatat persetujuan konsumen untuk komunikasi promosi
- Melacak keluhan dan memberlakukan daftar hitam pelanggar
Pada awal 2025, ekosistem DLT mencakup sekitar 250.000+ Entitas Utama terdaftar, 600,000+ Header terdaftar, dan lebih dari 55 juta templat pesan yang disetujui.
2.4 Undang-Undang Perlindungan Data Pribadi Digital, 2023 (Undang-Undang DPDP)
Undang-Undang Perlindungan Data Pribadi Digital, 2023 (Undang-Undang DPDP), diberlakukan pada 11 Agustus 2023, adalah undang-undang privasi komprehensif pertama di India. Sementara ketentuan penegakan substantifnya masih dioperasionalkan (Dewan Perlindungan Data India belum dibentuk pada awal 2026, dan Draf Aturan DPDP 2025 sedang dalam konsultasi publik), bisnis harus mempersiapkan penegakan penuh segera.
Khususnya untuk SMS, Undang-Undang DPDP menutupi kewajiban persetujuan tambahan di atas TCCCPR:
- Persetujuan Granular: Nomor telepon (data pribadi) hanya dapat digunakan untuk pemasaran SMS dengan persetujuan spesifik, terinformasi, diberikan secara bebas, tanpa syarat, dan tidak ambigu. Selimut atau persetujuan yang dibundel (misalnya, kotak centang S&K umum) tidak lagi cukup.
- Batasan Tujuan: Persetujuan yang diperoleh untuk satu tujuan (misalnya, peringatan pengiriman e-commerce) tidak dapat digunakan kembali untuk SMS promosi tanpa persetujuan baru.
- Hak Penarikan: Pelanggan dapat menarik persetujuan kapan saja; penarikan harus semudah pemberian persetujuan.
- Kewajiban Fidusia Data: Bisnis yang memproses nomor telepon untuk SMS adalah 'Data Fiduciari' dengan kewajiban termasuk minimalisasi data, akurasi, keamanan, dan penghapusan setelah tujuan selesai.
- Manajer Persetujuan: Kategori institusional baru β Manajer Persetujuan terdaftar β akan mengelola persetujuan pelanggan di seluruh platform.
- Lingkup Ekstrateritorial: Undang-Undang DPDP berlaku untuk setiap entitas di luar India yang memproses data pribadi warga negara India sehubungan dengan penawaran barang atau jasa di India.
- Hukuman berdasarkan Undang-Undang DPDP: Hingga βΉ50 crore (~ USD $6 juta) per instans untuk memproses data tanpa persetujuan yang sah; hingga βΉ250 crore (~ USD $30 juta) per insiden untuk pelanggaran data.
Referensi: Undang-Undang DPDP 2023 β Teks Lengkap (MEiTY) Β | Β Draft DPDP Rules 2025
2.5 Β Other Applicable Legislation
- Telecom Act, 2023: The new Telecommunications Act (replacing the Telegraph Act, 1885) reinforces powers around subscriber data, interception, and commercial communications.
- IT Act, 2000 (Sections 43A & 72A): Currently the operative data protection law pending DPDP Act enforcement β imposes liability for breach of sensitive personal data.
- Consumer Protection Act, 2019 & CCPA Guidelines (2023): Prohibit 'dark patterns' in digital consent collection. Directly relevant to opt-in flows and subscription traps in SMS marketing.
- RBI Circular on Digital Payment Security Controls (2021): For banking/fintech entities β mandates specific standards for OTP and transactional SMS delivery.
- SEBI Circular on Investor Communication: Securities-related SMS must comply with SEBI guidelines in addition to TCCCPR.
Reference: Telecom Act 2023 (DoT) Β | Β TRAI TCCCPR Full Resource Page
3. Two Delivery Routes: Domestic vs International
India offers two fundamentally different SMS delivery routes for businesses, each with distinct requirements, capabilities, and trade-offs. Understanding which route is right for your use case is the most important decision before you begin.
| Feature | Domestic Route | International (ILDO) | Notes |
|---|---|---|---|
| Who can use it | India-registered entities (or via a registered Indian aggregator) | Any entity worldwide | International companies need DLT only for domestic route |
| DLT Registration Required | YES β mandatory | NO | This is the defining difference |
| Sender ID (Header) | 6-char alphanumeric brand header (e.g., VM-ABCDEF) β DLT approved. Operator prefix added. | Random 5β9 digit ILDO short code (e.g., 54321). No brand ID. | DLT route preserves brand identity |
| DND Bypass | Transactional/Service messages bypass DND. Promotional respects DND. | Bypasses DND entirely β but only for genuine transactional/opted-in promo | International bypasses DND but content still screened |
| Promotional SMS | Supported β with DLT-registered template and DND scrubbing (10 AMβ9 PM) | Restricted β limited to non-DND numbers in daytime hours without opt-in | For promotional at scale, domestic route preferred |
| OTP / Transactional | Supported 24/7 via Service Implicit category | Supported 24/7 if truly transactional/OTP | Both routes support OTP well |
| Time Restrictions | Promotional: 10 AMβ9 PM IST only. Service/Transactional: 24/7. | Promotional without consent: 10 AMβ9 PM, non-DND only. Opted-in/OTP: 24/7. | Same window regardless of route for promo |
| URL Shorteners | Blocked β all URLs must be CTA-whitelisted (since Oct 1, 2024) | Generally not allowed β may be filtered | No shortened URLs on either route |
| Delivery Reports (DLR) | Reliable for transactional/service. Promotional may vary. | Unreliable for promotional (best-effort) | Domestic route provides better DLR |
| Brand Visibility | Full brand header visible (e.g., VM-HDFC-T) | No brand β random short code shown | Domestic wins for brand trust |
| Best For | Recurring communications, OTP, marketing campaigns, full compliance | International businesses, one-off OTP, testing | Most serious India programmes use domestic |
If you are an India-registered entity or have a local Indian business entity β use the Domestic Route via DLT registration for full brand visibility, reliable delivery, and promotional capability.
β
If you are an international company with no Indian entity and primarily need OTP/transactional messages β the International (ILDO) Route can work without DLT registration, but you'll lose brand identity (random short code shown) and promotional capabilities are severely limited.
β
Not sure which path makes more sense for your business? Our team can assess your use case and recommend the right route from day one β saving you weeks of trial and error.
4. DLT Registration β The Complete Step-by-Step Process
Since February 2021, telecom operators have been fully enforcing DLT scrubbing. Any SMS submitted to the domestic route from an unregistered entity, with an unregistered header, or matching no approved template will be silently dropped at the network level. The sender receives no error β the message simply never arrives.
4.1Β DLT Platforms β Choose One, Covers All
TRAI authorises major Indian telecom operators to host DLT platforms. You only need to register on ONE platform β all DLT platforms are synchronised with each other, so your Entity ID, Headers, and Templates are automatically available across all operators' networks.
| DLT Platform | URL & Notes |
|---|---|
| Airtel DLT (Recommended) | dltconnect.airtel.in β Strong support, fast approvals. Recommended for most businesses. |
| Jio TrueConnect | trueconnect.jio.com β Popular, good UI. Registration fee: βΉ5,900 incl. GST. |
| Vodafone Idea (VILPOWER) | vilpower.in β Vodafone Idea's platform. |
| BSNL DLT | ucc-bsnl.co.in β Government operator; slightly different process. |
| Tata Teleservices | telemarketer.tatateleservices.com β Tata's DLT platform. |
| Videocon (Ping Connect / SmartPing) | smartping.live β Used by some aggregators; recommended for faster approvals by some providers. |
| MTNL | ucc-mtnl.in β Delhi/Mumbai government operator |
Choosing the right DLT platform matters β some have faster approval queues, better support, and more intuitive interfaces than others. Our team knows exactly which platforms process applications
β
fastest and where common bottlenecks occur. We can guide you to the right platform and submit your application correctly the first time, avoiding the back-and-forth that delays most first-time registrants by weeks
4.2 Stage 1: Principal Entity (PE) Registration
The Principal Entity (PE) is your company or organisation β the legal entity that authorises commercial SMS to be sent on its behalf. Registering as a PE is the foundation of the entire process. Upon approval, you receive a unique PE ID (Entity ID) that must be passed in the message payload of every SMS you send.
Registration Types:
- Enterprise (Principal Entity): For any company, institution, or individual that wants to send SMS to its own customers. This is what most businesses register as
- Telemarketer: For SMS aggregators, resellers, and CPaaS providers that transmit commercial SMS on behalf of other businesses. If you are a CPaaS platform, you register as a Telemarketer (or both).
Documents Required for PE Registration:
- PAN Card: Business PAN card (mandatory β primary KYC document)
- GST Certificate: GSTIN (GST Identification Number) certificate
- Business Registration: Certificate of Incorporation (for companies) / Partnership Deed / Shop & Establishment Certificate / any valid business licence
- Authorized Signatory PAN & Aadhaar: KYC documents of the person signing on behalf of the entity
- Letter of Authorization: On company letterhead, authorising the signatory to register on behalf of the company
- Valid Business Email ID and Mobile Number: Used for OTP verification and communication
- 2025 Amendment β Biometric Authentication: The February 2025 TCCCPR amendments mandate physical verification and biometric authentication (Aadhaar-based OTP or biometric) for all new registrations. This applies to both PE and Telemarketer registrations
Registration Fee:
- PE Registration: βΉ5,900 (inclusive of GST) β one-time fee. This is the standard fee across Airtel, Jio, Vodafone Idea, and most other operators.
- BSNL: βΉ3,300 (inclusive of GST) β slightly lower
- Business Registration: Certificate of Incorporation (for companies) / Partnership Deed / Shop & Establishment Certificate / any valid business licence
Approval Timeline:
Entity approval typically takes 24β72 working hours if all documents are correct and complete. Common reasons for delay include mismatches between company name and PAN card, unclear document scans, or missing authorisation letters.
PE registration rejections are surprisingly common β documents in regional languages need translation, company names must exactly match the PAN card, and KYC requirements are strictly interpreted. Our team prepares your entire registration package before submission, reviews every document for accuracy, and handles any queries from the operator's verification team. Most of our clients get approved in 24β48 hours.
4.3 Β Stage 2: Header (Sender ID) Registration
A Header (formerly called Sender ID, now officially termed 'Header' in TRAI regulations) is the unique 6-character alphanumeric identifier that appears as the 'from' name on the recipient's phone. It must represent your brand name or service.
Header Format Rules:
- Length: Exactly 6 characters for transactional/service headers
- Case: Uppercase alphabetic (AβZ) only β no numbers in the 6-char header itself (numbers appear in the operator prefix)
- Brand Relevance: The header must be clearly identifiable as your brand or service. Generic headers (e.g., ALERTS, NOTICE, UPDATE) are rejected
- Uniqueness: A uniqueness check is enforced β if another entity already has your desired header, you must choose a different one
- Supporting Document: If the header doesn't obviously correlate with your company name, upload a document proving the relationship (trademark certificate, brand guidelines, etc.)
Header Types (Pre-2025 Amendment Classification):
| Header Type | Description |
|---|---|
| Promotional Header | 6-digit numeric (e.g., 654789). For marketing/promotional SMS to non-DND numbers. Displayed as a numeric ID to recipients. |
| Transactional / Service Header (Other) | 6-character alphanumeric brand header (e.g., HDFC, SWGGY, AMZN). For OTPs, transaction alerts, service messages. Displayed with operator prefix (e.g., VM-HDFC-T). |
May 2025 Update β Header Suffix System:
From May 6, 2025 (per TCCCPR 2025 Amendment), all SMS headers automatically carry a suffix appended by the telecom operator during DLT scrubbing, indicating the message category. Businesses do NOT need to change anything β this is applied automatically by the TSP.
| Suffix | Category & Description |
|---|---|
| -T (Transactional) | OTPs, bank alerts, transaction confirmations, balance alerts. Triggered within 30 minutes of a customer-initiated transaction. No explicit consent required. |
| -S (Service) | Service Implicit messages β updates to existing customers about products/services they actively use (warranty info, delivery updates, balance alerts, software upgrades). Based on inferred consent from the customer relationship. |
| -P (Promotional) | Marketing and advertising messages. Also now covers former 'Service Explicit' category (post-May 2025). Requires DND compliance and promotional time window. Only sent to subscribers who have not blocked promotional messages or have given explicit consent. |
| -G (Government) | Messages from Central/State Government or TRAI-authorised agencies. Exempt from DND restrictions. Can be sent at any time. |
The 'Service Explicit' category (which required proof of user consent and allowed service messages with a recommendation component) was discontinued effective May 7, 2025. All existing Service Explicit templates were automatically migrated to the Promotional (-P) category with the same content and header retained. Businesses previously using Service Explicit templates should review whether their messages are now being treated as promotional (subject to DND scrubbing and time window restrictions).
Header Fee:
- Sender ID/Header Registration: βΉ590 per header per year β annual renewal required.
- Additional headers for the same entity cost the same annual rate.
Header Approval Timeline: β
Header approval typically takes 1β3 working days. Unused headers (no traffic for 90 days) are automatically deactivated by operators and must be re-registered.
Header selection is deceptively tricky β your chosen 6 characters must be brand-relevant, not already taken, and must pass the operator's approval review. We've seen companies waste days on rejected headers. We advise on the right header choice upfront, check availability before you apply, and prepare the supporting brand documentation to get approval the first time
4.4 Β Stage 3: Content Template Registration
Every single SMS you intend to send must match a pre-approved Content Template registered on the DLT platform. This is non-negotiable. A message that doesn't match an approved template is silently blocked at the network level. There is no error message; the SMS simply disappears.
Template Categories:
| Category | Rules & Use Cases |
|---|---|
| Transactional (-T) | Triggered within 30 minutes of a customer-initiated transaction. OTPs, bank alerts, payment confirmations, login codes, refund notifications. No DND restrictions. Can be sent 24/7. Variables like OTP code, amount, date, account number are allowed. |
| Service Implicit / Service (-S) | Communications to existing customers about products/services they currently use, based on inferred consent from the existing relationship. Delivery updates, warranty alerts, software upgrades, balance reminders, appointment confirmations. No explicit consent needed. Can be sent 24/7. Cannot contain promotional content. |
| Promotional (-P) | Marketing messages promoting products or services. Only sent to subscribers who have not blocked promotional communications (DND-compliant) or who have given explicit digital consent. Time-restricted: 10 AM β 9 PM IST only. Promotional content mixed with any other category = treated as Promotional. |
| Government (-G) | Central/State Government or TRAI-authorised communications. Exempt from all DND and time restrictions. |
Template Formatting Rules:
- Brand Name Required: Every template must include your brand name (complete business name, brand name, or trademark) in the content field. This is mandatory.
- Variables (Placeholders): Dynamic content (OTP codes, names, amounts, order IDs, dates, tracking numbers) is represented by the placeholder {#var#} in templates. A maximum of 5β6 variables is allowed per template. Variables must be pre-tagged by purpose (since October 1, 2024).
- Variable Tagging (October 1, 2024 Mandate): Each variable must be tagged according to its type β e.g., OTP, amount, account number, date. This prevents misuse of open-ended variables to inject spam content. Variables can only carry the specific data type for which they're tagged.
- Template ID: Each approved template gets a unique Template ID that must be passed in the message payload alongside the PE ID.
- Template Ownership: Once approved, the entity retains ownership of that template across all DLT platforms.
- Template Registration Cost: Free β there is no charge for registering content templates.
- Template Approval Time: 1β3 working days.
Template Example:
Dear {#var#}, Your OTP for logging into ABCBRAND is {#var#}. Valid for {#var#} minutes. Do not share this with anyone. - ABCBRANDΒ Variable Tags: [1] Customer name β type: Name | [2] OTP code β type: OTP | [3] Validity β type: Duration Template Category: Transactional (-T) | Header: ABCBRD
Your {#var#} is {#var#}. {#var#} β ABCBRANDΒ Reason: Variables not tagged by purpose. Untag open-ended variables are rejected since October 1, 2024.
Template registration is where most businesses hit their biggest wall. The October 2024 Variable Tagging requirement alone has caused widespread confusion and registration failures. Our team writes and structures your templates to TRAI specifications, selects the right category (transactional vs service vs promotional), tags all variables correctly, and pre-screens every template before submission. We also maintain your template library and update it whenever your message content changes
4.5 Stage 4: CTA Whitelisting (Mandatory Since October 1, 2024)
Effective October 1, 2024, all Call-to-Action (CTA) elements in SMS templates β including URLs, app download links (APKs), OTT platform links, and any clickable content β must be pre-whitelisted on the DLT platform before they can be included in messages. Any message containing a non-whitelisted URL is automatically scrubbed (blocked) during delivery.
CTA Whitelisting Rules:
- Mandatory Pre-Approval: Every URL, app link, or OTT link intended for use in SMS must be submitted and approved via the DLT platform before use.
- No Public URL Shorteners: Shortened URLs (bit.ly, tinyurl, etc.) are blocked. Use full branded URLs or dedicated branded short domains.
- Domain Ownership Proof: You must demonstrate ownership or authorised use of the URL/domain you wish to whitelist.
- Scope: Covers all URLs, APK download links, OTT links (WhatsApp, Telegram, etc.) β any clickable or callable element.
- Existing Templates: All previously approved templates containing URLs must be updated and the URLs whitelisted β retroactively applied.
CTA Whitelisting has been one of the biggest sources of delivery failures since October 2024. Many businesses didn't realise their existing templates were being blocked until they noticed delivery drops. We audit your entire template library for CTA compliance, whitelist all your approved domains correctly, and set up a process to whitelist new URLs before your campaigns go live β so you never face a surprise block.
4.6 Stage 5: PE-TM Binding (Linking Your Provider)
The final step before you can send via a Telemarketer (your SMS provider/CPaaS platform) is the PE-TM (Principal Entity β Telemarketer) Binding. This creates a formal, DLT-recorded relationship between your entity and your chosen provider, authorising them to send messages on your behalf.
- Log in to your DLT account after PE registration is complete.
- Navigate to 'Telemarketer Request' or equivalent section.
- Search for your SMS provider/CPaaS by their registered Telemarketer ID (your provider will give you this ID). Add them and submit the binding request.
- The Telemarketer must accept the binding request from their side.
- Once bound, your provider can transmit messages using your registered headers and templates.
- TCCCPR 2025 Restriction: The maximum number of intermediaries between the Principal Entity and the end Telemarketer is now limited (typically one aggregator between PE and final TSP), to ensure full traceability of messages.
PE-TM binding sounds simple but it's a step that many businesses forget, causing puzzling delivery failures even after registration is complete. We guide you through the exact binding process for our platform, ensure the binding is confirmed on both sides, and verify end-to-end delivery before you launch.
4.7 Β DLT Registration Costs Summary
| Item | Cost |
|---|---|
| PE Entity Registration | βΉ5,900 (incl. GST) β one-time, per entity. (BSNL: βΉ3,300) |
| Additional platform registrations | Free β synced automatically after first registration |
| Sender ID / Header Registration | βΉ590 per header per year β annual renewal required |
| Content Template Registration | Free |
| CTA URL Whitelisting | Free |
| PE-TM Binding | Free |
| Telemarketer Registration (if applicable) | βΉ5,900 one-time + βΉ590/year per header (renewal after 5 years) |
| Typical Total for One Entity, One Header | ~βΉ6,490ββΉ7,000 for first year (one PE + one header) |
| Additional Headers (each) | βΉ590/year |
4.8 Β Typical DLT Registration Timeline
| Stage | Estimated Time |
|---|---|
| PE Entity Approval | 24β72 working hours (1β3 business days) |
| Header / Sender ID Approval | 1β3 working days |
| Template Approval | 1β3 working days |
| CTA Whitelisting | 1β3 working days |
| PE-TM Binding | Same day (both sides accept) |
| Total Expected Timeline (all steps, no rejections) | 5β10 business days |
| Total with corrections/rejections (common for first-timers) | 2β4 weeks |
| With Expert Assistance | 3β7 business days (our team pre-validates everything) |
5. Message Categories, DND, and Time Restrictions
5.1 Β The Four Message Categories (Post-May 2025)
Every commercial SMS in India must be classified into one of four categories. This classification determines: whether the message bypasses DND, when it can be sent, and what consent is required.
| Category | Description & Rules |
|---|---|
| Transactional (-T) | Customer-initiated, within 30 minutes of a transaction. OTPs, bank alerts, refund info, login codes, payment confirmations. NO DND restrictions. 24/7 delivery. No consent beyond the transaction itself required. |
| Service Implicit (-S) | Service updates to existing customers about products/services they actively use β based on the inferred consent of an existing commercial relationship. Delivery updates, warranty alerts, balance reminders, appointment reminders, software upgrade notices. NO DND restrictions. 24/7 delivery. Cannot contain promotional content β if mixed, treated as Promotional. |
| Promotional (-P) | Advertising and marketing messages. Also covers former Service Explicit (post-May 2025). Subject to DND scrubbing β only delivered to non-DND subscribers or those with explicit digital consent. Time-restricted: 10 AM β 9 PM IST. Must use DLT-registered promotional template. |
| Government (-G) | Central/State Government or TRAI-authorised body communications. Completely exempt from DND and time restrictions. Requires TRAI-approved government header. |
5.2 Β DND β Do Not Disturb Registry
The National Do Not Disturb (DND) Registry (also called the National Customer Preference Register / NCPR) is managed by TRAI and maintained by all telecom operators. Subscribers can register to block all commercial communications or selectively block by category (financial, real estate, education, health, etc.).
DND has several levels:
- Fully Blocked: All commercial communications blocked, except Transactional, Service Implicit, and Government messages.
- Partially Blocked: Subscriber allows certain promotional categories. E.g., 'Receive only banking and healthcare promotions.' The DLT scrubbing system checks the promotional category tag in your template against the subscriber's allowed preferences.
- Not on DND: All commercial communications permitted, subject to time window restrictions for promotional messages.
DLT scrubbing runs in real-time against the DND registry for every outgoing message. Promotional messages to fully blocked numbers are silently dropped. There is no error β the message is simply not delivered.
If a subscriber has given explicit digital consent (via the TRAI-mandated Digital Consent Acquisition / DCA facility) to a specific sender for a specific purpose, promotional messages from that sender CAN be delivered even if the subscriber is on DND. This is a powerful exception β but the consent must be digitally recorded on the DLT Consent Register via the DCA process, which involves OTP verification from the subscriber
5.3 Promotional SMS β Time Restriction
All Promotional (-P) SMS messages may only be delivered between 10:00 AM and 9:00 PM Indian Standard Time (IST, UTC+5:30).
β
India is a single time zone β there is no regional adjustment needed. Messages sent outside this window (9:01 PM β 9:59 AM) are blocked at the DLT scrubbing layer and are NOT queued for later delivery β they are dropped. Transactional (-T) and Service (-S) messages can be sent at any time
5.4 Β Digital Consent Acquisition (DCA)
The DCA facility, mandated by TRAI (Direction issued June 2, 2023), enables businesses to digitally register customer consent for receiving promotional communications. The process:
- Business creates and submits a Consent Template on the DLT platform (distinct from Content Templates).
- Customer is presented with the consent request (web, app, IVR, or in-person).
- Customer verifies consent via OTP (triggered through the telecom operator).
- Consent is recorded on the DLT Consent Register, linked to the subscriber's mobile number.
- Business can then send promotional messages to that subscriber regardless of DND status.
Note: Consent via DCA is valid for 12 months from approval date and must be renewed. TRAI acknowledged in 2025 that many businesses find the DCA process restrictive and alternatives are being explored.
6. How SMS Headers Appear to Recipients
Understanding the full structure of an SMS header as it appears on a recipient's phone is important for managing customer expectations and for correctly structuring your Sender ID registration.
| Header Type | Format & Example |
|---|---|
| Standard Format (Domestic) | XX-HEADER-Y (e.g., VM-HDFC-T) Where: XX = 2-letter operator+circle code | HEADER = your 6-char brand header | -Y = category suffix (-T, -S, -P, or -G, effective May 6, 2025) |
| Example: Vodafone Mumbai | VM-HDFC-T (Vodafone Mumbai, HDFC Bank header, Transactional) |
| Example: Airtel Delhi | AD-AMAZON-S (Airtel Delhi, Amazon header, Service) |
| Example: Jio Bangalore | JB-SWIGGY-P (Jio Bangalore, Swiggy header, Promotional) |
| International Route | Random 5β9 digit numeric code (e.g., 54321 or 56789012) β no brand identity visible |
| Government Header | Exempt from prefix requirements β shown as the registered government header |
The two-letter operator+circle code (e.g., VM = Vodafone Mumbai, JB = Jio Bangalore, AD = Airtel Delhi) is automatically prepended by the carrier. Businesses do not control this prefix. If a subscriber moves from one circle or operator to another (using MNP), the prefix changes accordingly.
7. Consent Requirements
Consent requirements in India differ by message category. The most restrictive rules apply to promotional messages; transactional messages require the least formality.
| Scenario | Consent Required |
|---|---|
| Transactional (-T) | No explicit consent needed β the customer's own transaction (within 30 minutes) constitutes the basis. Sending OTPs, payment confirmations to customers who transact with you requires no separate consent registration. |
| Service Implicit (-S) | Based on inferred consent from the existing customer/subscriber relationship. If someone is your customer, you may send them service messages related to that relationship without separate consent registration on DLT. However, must not include promotional content. |
| Promotional (-P) to Non-DND | No explicit consent needed if the subscriber is not on DND and the message is sent within the promotional time window. The subscriber's absence from DND implies acceptance of promotional communication within TRAI's framework. |
| Promotional (-P) to DND subscribers | Requires explicit digital consent recorded via DCA (Digital Consent Acquisition) β OTP-verified and registered on the DLT Consent Register. This consent overrides DND status. |
| Under DPDP Act (when enforced) | Granular, specific, informed, freely given consent required for use of phone numbers for marketing. Existing blanket consent must be refreshed with proper notice. Consent withdrawal must be honoured immediately. |
7.1 Β Opt-Out Requirements
- STOP / UNSUBSCRIBE: All promotional SMS campaigns must offer and honour opt-out. Standard opt-out keyword is STOP (or START to re-subscribe).
- Mandatory Opt-Out Mechanism (2025 Amendment): Telecom operators are now required to include a mandatory opt-out option in promotional messages (e.g., 'Reply STOP to opt out'). This is becoming a required element of all promotional templates.
- 90-Day Re-Contact Rule: After a subscriber opts out, you may NOT send them a consent acquisition request for 90 days from the opt-out date.
- 1909 Short Code: Subscribers can report spam to their operator by SMSing to 1909 or calling 1909. Complaints can be filed within 7 days of receiving the spam message (extended from 3 days in 2025 amendment).
- TRAI DND App: Subscribers can also report spam via the TRAI DND mobile app.
8. Content Restrictions
8.1 Β Absolutely Prohibited Content
- Firearms β promotion, sale, or instruction related to weapons
- Gambling β any form, including online casinos, lottery, fantasy sports with financial stakes
- Adult / sexually explicit content
- Money / loan schemes β payday loans, unregulated lending, debt collection with threats
- Political content or election campaign messaging
- Religious content β proselytising or faith-based solicitation
- Controlled substances β narcotics, cannabis, vaping
- Alkohol β promosi minuman beralkohol kepada masyarakat umum
- Phishing dan penipuan β peniruan identitas, ID Pengirim palsu, konten yang menyesatkan
- Spam β pesan massal yang tidak diminta tanpa persetujuan terdaftar atau persetujuan DLT
- Lalu lintas P2P melalui jalur A2P β merutekan komunikasi pribadi melalui saluran komersial untuk menghindari DLT
- Rute abu-abu/perutean tidak sah β menggunakan kotak SIM atau telemarketer yang tidak terdaftar untuk melewati DLT
- OTP atau pesan bermerek bank yang dikirim oleh entitas non-bank yang menyamar sebagai lembaga keuangan
8.2 Pembatasan URL dan Tautan
Sejak 1 Oktober 2024, SEMUA URL dalam template SMS harus:
β
1. URL lengkap (tidak ada penyingkat publik seperti bit.ly, tinyurl, t.co, dll.)
β
2. Pra-daftar putih di platform DLT melalui proses Whitelisting CTA
β
3. Dari domain yang Anda miliki atau diizinkan untuk digunakan
β
Setiap SMS yang berisi URL yang tidak masuk daftar putih akan diblokir secara diam-diam selama penggosokan DLT. Ini berlaku surut untuk templat yang disetujui sebelumnya β jika Anda memiliki URL di templat lama, templat tersebut harus diperbarui dan URL dimasukkan ke daftar putih.
8.3 Aturan Khusus OTP
- Pesan OTP harus dikirim melalui kategori Transactional (-T)
- Pesan OTP harus cocok dengan template Transaksional terdaftar
- Template OTP harus menyertakan nama merek
- Kode OTP harus dalam variabel bertag {#var #} dari tipe 'OTP'
- Validitas dan instruksi OTP ('Jangan bagikan') sangat disarankan
- Tidak ada konten promosi yang boleh dicampur ke dalam pesan OTP β ini mengklasifikasi ulang pesan sebagai Promosi dan tunduk pada batasan DND/waktu
- Untuk OTP perbankan: RBI mengamanatkan standar keamanan tambahan (tidak ada tautan yang dapat diklik dalam pesan OTP per penasihat RBI)
8.4 Sektor Keuangan (BFSI) - Aturan Tambahan
- Pedoman RBI: Pesan OTP untuk otentikasi perbankan dan pembayaran harus mematuhi Kontrol Keamanan Pembayaran Digital RBI. Tidak ada URL dalam pesan OTP perbankan.
- SEBI: Komunikasi pasar modal (peringatan perdagangan, pembaruan portofolio) harus mematuhi persyaratan sirkular SEBI tentang komunikasi investor.
- : SMS terkait asuransi harus mematuhi pedoman komunikasi IRDAI.
- Tidak Ada Header Bank Palsu: Meniru ID Pengirim bank merupakan pelanggaran pidana berdasarkan Undang-Undang TI dan IPC selain pelanggaran TCCCPR.
9. Pengkodean Pesan & Batas Karakter
| Encoding | Details |
|---|---|
| GSM-7 (Standard) | 160 characters per SMS segment. Concatenated: up to 6 segments = 918 characters max. Supports standard Latin alphabet + common punctuation. Available for all routes. |
| UCS-2 / Unicode | 70 characters per SMS segment. Concatenated: up to 6 segments = 402 characters max. Required for Hindi, Tamil, Telugu, Bengali, Kannada, Gujarati, Punjabi, Marathi, and other Indian languages. Supported on domestic DLT route (Transactional/Service). Also supported on International route. |
| Concatenation Support | Supported with caveats β not all Sender ID types guarantee proper concatenation. Where messages are split may vary by carrier. |
| Indian Language Scripts | All 22 scheduled Indian languages can be sent via UCS-2 encoding. Message limits are 70 characters per segment in Unicode mode. |
| Special Characters | The following GSM-7 characters use 2 character slots: { } [ ] ^ ~ \ | β¬. Template length should account for this. |
| Template Character Limit | Templates may define up to 5β6 variables. The total template length including all variables must be structured for the intended encoding. A 160-character GSM-7 template can have up to the limit, with variable content added at runtime. |
10. Lanskap Pembawa
India memiliki lima operator telekomunikasi utama (TSP) yang melayani lebih dari 1,18 miliar pelanggan seluler. Portabilitas Nomor (MNP) beroperasi penuh β pelanggan dapat berpindah antar operator sambil mempertahankan nomor mereka. Platform DLT secara otomatis merutekan pesan ke operator yang benar setelah portabilitas.
| Operator | Details |
|---|---|
| Reliance Jio | Largest operator β ~470 million subscribers. Launched 4G in 2016, rapidly became the market leader. DLT Platform: TrueConnect (trueconnect.jio.com). MCC/MNC: 404-50, 405-857, and others. |
| Bharti Airtel | Second largest β ~380 million subscribers. India's oldest private telecom operator. Strong enterprise and B2B presence. DLT Platform: DLT Connect (dltconnect.airtel.in). MCC/MNC: 404-10, 404-20, and multiple others by circle. |
| Vodafone Idea (Vi) | Third largest β ~225 million subscribers. Result of Vodafone-Idea merger. DLT Platform: VILPOWER (vilpower.in). MCC/MNC: 404-20, 404-30, 405-028, and others. |
| BSNL (Bharat Sanchar Nigam Ltd) | Government-owned PSU. ~100 million subscribers. Primarily serves smaller cities and rural areas. DLT Platform: ucc-bsnl.co.in. MCC/MNC: 404-01, 404-07, and others. |
| MTNL (Mahanagar Telephone Nigam Ltd) | Government-owned. Operates only in Delhi and Mumbai. ~3 million subscribers. DLT Platform: ucc-mtnl.in. MCC/MNC: 404-68 (Mumbai), 404-69 (Delhi). |
11. Mengirim Praktik Terbaik
- Selalu Sertakan ID PE dan ID Template dalam Payload Pesan: Keduanya harus diteruskan sebagai parameter dalam permintaan SMS API Anda untuk setiap pesan. Tanpa mereka, pesan gagal menggosok DLT.
- Hormati Jendela Promosi: 10:00 AM β 9:00 PM IST secara ketat. Jadwalkan kampanye untuk memastikan meskipun pengiriman API dilakukan pada pukul 20:55, pengiriman selesai sebelum pukul 21:00.
- Jangan pernah mencampur konten promosi dan transaksional: Satu kalimat promosi dalam pesan layanan/transaksional mengklasifikasi ulang seluruh pesan sebagai Promosi β memicu pemeriksaan DND dan pembatasan waktu.
- Gunakan URL Lengkap Saja: Semua URL harus masuk daftar putih CTA dan berdurasi penuh. Tidak ada pemendek publik. Ini sekarang adalah blok tingkat jaringan keras.
- Pertahankan Aktivitas Header: Header yang tidak digunakan selama 90 hari secara otomatis dinonaktifkan. Pastikan setidaknya lalu lintas minimal untuk mempertahankan header aktif, atau perbarui secara proaktif sebelum dormansi.
- Double Opt-In untuk Daftar Pemasaran: Terapkan langkah konfirmasi setelah opt-in awal. Kirim SMS konfirmasi dan aktifkan pelanggan hanya ketika mereka merespons dengan tegas.
- Catatan Persetujuan Simpan: Simpan catatan tentang bagaimana dan kapan setiap pelanggan memilih, termasuk saluran, stempel waktu, kata-kata opt-in, dan bukti pendukung apa pun. Di bawah Undang-Undang DPDP (ketika diberlakukan), Anda harus membuktikan persetujuan.
- Sertakan Opt-Out di Setiap Pesan Promosi: 'Balas STOP untuk memilih keluar' atau serupa. Segera hormati pilihan keluar.
- Uji Template Sebelum Kampanye Massal: Kirim pesan uji ke nomor Anda sendiri sebelum meluncurkan kampanye besar untuk memverifikasi pencocokan dan pemformatan template yang benar.
- Jangan Gunakan Rute Abu-abu: Perutean kotak SIM dan telemarketer yang tidak terdaftar secara aktif terdeteksi oleh sistem AI/ML dan honeypot TRAI. Hukuman termasuk pemutusan segera dan daftar hitam.
- Pesan Bahasa India: Gunakan pengkodean UCS-2 untuk konten bahasa regional. Template yang berisi skrip India harus terdaftar dalam pengkodean yang benar.
- Tinjau Template Setelah Pembaruan Peraturan: TRAI sering memperbarui peraturan. Kategori template, aturan variabel, dan persyaratan CTA semuanya telah berubah sejak 2021. Audit perpustakaan template Anda setelah setiap pengumuman TRAI utama.
12. Hukuman untuk Ketidakpatuhan
| Violation Type | Consequence |
|---|---|
| Unregistered Commercial SMS (UTM) | Warning on first instance β Usage cap (max 20 messages/day) for 6 months on second instance β Full disconnection of all telecom resources on third/subsequent violations |
| Financial Disincentives (Access Providers) | TRAI may impose financial penalties on TSPs for failing to act on UCC complaints or misreporting β ranging from βΉ2 lakh to βΉ10 lakh per instance |
| Blacklisting | Registered Telemarketers found violating TCCCPR are blacklisted β barred from registering on any DLT platform and using any commercial communication resource |
| DPDP Act β Processing Without Consent (when enforced) | Administrative penalty up to βΉ50 crore (~USD $6 million) per instance |
| DPDP Act β Data Breach Failure | Up to βΉ250 crore (~USD $30 million) per incident |
| IT Act β Data Breach (current) | Civil liability up to βΉ5 crore; criminal liability up to 3 years imprisonment under Section 72A for wrongful disclosure of personal data |
| Maximum TCCCPR Penalties on Businesses | Up to βΉ50 lakh in fines under some interpretations; service termination for repeated violations |
| Grey Route Detection | Immediate termination of SMS services; potential criminal liability under IT Act |
| Using Fake/Impersonating Sender IDs | Criminal offence under IT Act and IPC β fraud, cheating, and identity theft provisions apply |
| Complaint Window (2025 Update) | Subscribers now have 7 days (previously 3 days) to file UCC complaints. Action must be taken within 5 days against unregistered senders. |
13. Daftar Periksa Kepatuhan SMS India Pra-Peluncuran
Pendaftaran DLT β Rute Domestik
- [] Menentukan rute pengiriman mana yang akan digunakan: Domestik (DLT) atau Internasional (ILDO)
- [] Platform DLT yang dipilih (Airtel, Jio, Vi, BSNL, Tata, atau SmartPing)
- [] Menyelesaikan pendaftaran Entitas Utama (PE) dengan semua dokumen KYC
- [] Menerima dan dicatat ID PE unik (ID Entitas Utama)
- [] Verifikasi OTP biometrik/Aadhaar selesai (per amandemen 2025)
- [] Semua Header SMS (ID Pengirim) terdaftar - header yang relevan dengan merek 6-karakter untuk transaksi/layanan, numerik untuk promosi
- [] Semua Template Konten terdaftar - kategori yang benar (Transaksial/Layanan/Promosi/Pemerintah)
- [] Nama merek termasuk dalam setiap template konten
- [] Semua variabel dalam template pra-tag berdasarkan jenis (OTP, jumlah, nama, tanggal, dll.) Per mandat 1 Oktober 2024
- [] Semua URL dalam templat CTA-Daftar Putih di platform DLT (mandat 1 Okt 2024)
- [] Tidak ada penyingkat URL publik yang digunakan dalam template apa pun
- [] Integrasi ID PE dan ID Template dikonfirmasi dengan API penyedia SMS
- [] PE-TM Binding selesai dengan penyedia SMS Anda/platform CPaaS
Kategori Pesan & DND
- [] Setiap jenis pesan dikategorikan dengan benar: Transaksional (-T) /Layanan (-S) /Promosi (-P) /Pemerintah (-G)
- [] Pesan promosi dijadwalkan untuk dikirim hanya antara pukul 10:00 AM β 9:00 PM IST
- [] Tidak ada konten promosi yang dicampur ke dalam template Transaksional atau Layanan
- [] DND scrubs dikonfirmasi aktif untuk kampanye promosi
- [] Proses Persetujuan Digital Eksplisit (DCA) diatur jika mengirim promosi ke pelanggan DND
Persetujuan & Opt-Out
- [] Mekanisme persetujuan opt-in berlaku untuk semua penerima pemasaran
- [] Catatan persetujuan disimpan dengan stempel waktu, saluran, kata-kata, dan nomor telepon
- [] Respons kata kunci STOP/opt-out dikonfigurasi
- [] Instruksi opt-out termasuk dalam setiap pesan promosi
- [] Pembatasan kontak ulang 90 hari diprogram untuk nomor yang dipilih keluar
Konten & Hukum
- [] Ulasan konten terlarang selesai: tidak ada perjudian, dewasa, politik, agama, senjata api, alkohol, konten ganja
- [] Pesan OTP hanya berisi kode OTP, nama merek, dan validitas - tidak ada konten promosi
- [] Pesan OTP perbankan/fintech mematuhi Kontrol Keamanan Pembayaran Digital RBI
- [] Rencana kepatuhan Undang-Undang DPDP di tempat β siap untuk penegakan
- [] Penasihat hukum dengan keahlian telekomunikasi/privasi India telah meninjau program ini
14. Sumber & Referensi Otoritatif
14.1 TRAI - Sumber Peraturan Resmi
14.2 Tautan Platform DLT
14.3 Legislasi Utama
14.4 Pelaporan Spam
14.5 Analisis Hukum & Peraturan
Kerangka kerja DLT India benar-benar salah satu sistem kepatuhan SMS paling kompleks di dunia β dan berkembang pesat. Antara amandemen TCCCPR 2025, mandat Daftar Putih CTA Oktober 2024, persyaratan Penandaan Variabel, penegakan Undang-Undang DPDP yang tertunda, dan proses pendaftaran DLT lima langkah, ada banyak hal yang bisa salah jika Anda melakukannya sendiri.
β
Anda tidak perlu mencari tahu sendiri.
β
Pakar SMS India kami telah memandu ratusan bisnis - dari pemula hingga perusahaan - melalui proses pendaftaran DLT lengkap. Kami tahu platform DLT mana yang paling cepat menyetujui, cara menyusun template untuk menghindari penolakan, cara memasukkan URL CTA ke daftar putih dengan cepat, dan cara menghindari kesalahan umum yang menunda sebagian besar bisnis selama 2-4 minggu.
β
Apa yang kami tangani untuk Anda:
β
β’ Pendaftaran DLT penuh: pengaturan entitas PE, persiapan dokumen KYC, dan penyerahan
β
β’ Pemilihan header/Pengirim ID, pemeriksaan ketersediaan, dan pendaftaran
β
β’ Semua pembuatan Template Konten, penandaan variabel, dan klasifikasi kategori
β
β’ Daftar putih URL CTA untuk setiap domain dan tautan yang Anda butuhkan
β
β’ Pengikatan PE-TM dengan platform kami
β
β’ Pemantauan kepatuhan berkelanjutan saat peraturan TRAI berkembang
β
β’ Dukungan kepatuhan India khusus setiap kali Anda memiliki pertanyaan
β
Sebagian besar klien kami tinggal dan mengirim di India dalam 5-7 hari kerja. Hubungi dan mari kita siapkan dan jalankan program SMS India Anda β dengan benar, sesuai, dan cepat.
πΊπΈ
United States
SMS Guidelines, Regulations & A2P 10DLC Compliance
The Complete Reference for Businesses Sending Commercial SMS in the USA
Dialing Code: +1 | ISO: US | Region: North America | MCC: 310, 311, 312, 316
Regulator: FCC (Federal Communications Commission) | FTC (Federal Trade Commission) | Framework: TCPA + CTIA Messaging Principles | Last Updated: February 2026
β
This document is for informational reference only and does not constitute legal advice. US SMS regulations are subject to regulatory updates and carrier policy changes. Consult qualified legal counsel and review current FCC/CTIA guidelines before launching any SMS programme.
β
Navigating A2P 10DLC registration β from TCR brand registration to campaign submission, carrier vetting, and content compliance β can feel overwhelming. The USA has multiple overlapping regulatory bodies and carrier-level policies that change frequently.
Message Central's team handles the entire registration process for you: TCR brand setup, campaign submission, carrier approvals, and ongoing compliance monitoring. Let us take the paperwork off your plate so your campaigns go live without delays or blocks.
β
1. Country Overview
| Parameter | Detail |
|---|---|
| Country | United States of America |
| ISO | US |
| Dialing Code | +1 |
| MCC | 310β316 (multiple) |
| Time Zones | ET (UTC-5/-4), CT (UTC-6/-5), MT (UTC-7/-6), PT (UTC-8/-7) β DST applies MarchβNovember |
| Mobile Subscribers | ~350 million |
| Two-Way SMS | Fully supported |
| Number Portability | Yes β full MNP |
| Concatenated SMS | Yes β fully supported |
| Message Length | 160 chars (GSM-7) | 70 chars (UCS-2) |
| MMS | Natively supported on 10DLC and Short Codes |
| Primary Number Types | 10DLC long codes, Toll-Free numbers, Short Codes |
| DLT/Registry | The Campaign Registry (TCR) for A2P 10DLC |
β
2. Regulatory Framework
2.1 TCPA β Telephone Consumer Protection Act (47 U.S.C. Β§ 227)
The TCPA is the primary federal law governing commercial SMS. Enforced by the FCC, it prohibits sending marketing text messages to mobile numbers without prior express written consent. Key provisions:
β’ Prior Express Written Consent (PEWC): Required for all marketing/promotional SMS. Must be a clear, conspicuous written agreement β digital opt-in (checkbox, keyword) is acceptable. Pre-checked boxes are NOT valid.
β’ Prior Express Consent (PEC): Sufficient for transactional/informational messages (where the customer provided their number in connection with the transaction).
β’ FCC 2024 Consent Revocation Order: Effective from January 27, 2025 β consent revocation (opt-out) must be actioned within 10 business days. Consumers may revoke via any reasonable channel (call, text, email, web form).
β’ TCPA Penalties: $500β$1,500 per violation. Class actions are common; a single campaign to thousands can result in millions in liability.
TCPA β FCC Reference | TCPA Statute β 47 U.S.C. Β§ 227
β
2.2 CTIA Messaging Principles & Best Practices (May 2023)
The CTIA (Cellular Telephone Industry Association) Messaging Principles and Best Practices are carrier-enforced standards that all A2P SMS providers and their customers must follow. They govern prohibited content, opt-in/opt-out mechanics, and message content requirements. Violations result in campaign suspension or blocking by carriers.
CTIA Messaging Principles & Best Practices
β
2.3 The Campaign Registry (TCR) & A2P 10DLC
The Campaign Registry (TCR) is the third-party registration hub for A2P 10DLC (Application-to-Person long code messaging). All businesses sending A2P SMS via 10DLC must register their Brand and Campaign(s) with TCR before submitting messages through carrier networks. Registration is mandatory since 2021.
The Campaign Registry (TCR) | T-Mobile Code of Conduct
β
2.4 FTC Telemarketing Sales Rule (TSR) & CAN-SPAM
The FTC's Telemarketing Sales Rule (TSR) governs text messages as a form of telemarketing, requiring consent and prohibiting deceptive practices. CAN-SPAM applies primarily to email but some provisions (deceptive headers, identity) are relevant to commercial communications broadly.
FTC Telemarketing Sales Rule | FTC ROSCA (Negative Option Rule)
β
2.5 State Laws
Several US states have enacted additional SMS/telemarketing laws that go beyond federal requirements:
β’ Florida (FTSA β Florida Telephone Solicitation Act): Imposes a state-specific prior express written consent requirement for automated or prerecorded text messages. Among the most litigated state laws.
β’ California (CCPA / CPRA): While primarily a data privacy law, the CCPA gives Californians the right to opt out of the 'sale' of personal data (including phone numbers). Relevant to marketing list management.
β’ Oklahoma, Washington, Texas: Have enacted state-level telemarketing restrictions that may supplement TCPA requirements.
FCC Consumer Resources on Texts | CCPA β California AG
3. Number Types & Registration
3.1 A2P 10DLC β The Standard for Business SMS
β
10DLC (10-Digit Long Code) refers to standard 10-digit US phone numbers repurposed for A2P (Application-to-Person) business messaging. Since 2021, all 10DLC A2P traffic requires mandatory TCR Brand + Campaign registration. Unregistered or non-compliant traffic is filtered or blocked by all major US carriers.
β
TCR Registration Process:
1. Register your Brand on TCR β costs $4 one-time. Standard vetting ~24 hours; Enhanced vetting $40 (required for higher throughput).
2. Register your Campaign on TCR β specify the use case, message content examples, opt-in method, and opt-out mechanism. Cost: $10β$15/month depending on campaign type.
3. Carrier vetting β AT&T, T-Mobile, Verizon all independently review campaigns. T-Mobile has an additional $10/month fee for most campaign types.
4. Assign 10DLC phone number(s) to the approved campaign via your SMS provider.
5. Begin sending β within throughput limits assigned to your campaign.
10DLC Throughput:
β
| Tier | Throughput / Notes |
|---|---|
| Standard (no vetting) | Up to ~75 MPS (messages per second). Unvetted brands start lower. |
| Enhanced vetting | Up to ~300 MPS. Faster delivery, higher throughput. |
| T-Mobile Non-Compliance Fees | $1,000β$10,000 for policy violations discovered post-launch. |
β
3.2 Toll-Free Numbers (TFN)
Toll-Free numbers (+1-800/888/877/866/855/844/833 prefix) are a popular A2P SMS channel. They require separate Toll-Free Verification (TFV) registration. Key details:
β’ Throughput: Up to 3 messages/second unverified; up to 50 MPS when fully verified.
β’ Registration: Submit Toll-Free Verification form via your SMS provider β 3β6 weeks for full approval.
β’ Best For: Customer service, transactional alerts, two-way SMS β cannot be used for a 'short code' feel but has lower registration friction than 10DLC for some use cases.
β
3.3 Short Codes
Dedicated 5 or 6-digit short codes (e.g., 54321) are the highest-throughput A2P channel and provide the most reliable delivery.
β’ Provisioning Time: 6β12 weeks (shared short codes have been deprecated β all short codes are now dedicated).
β’ Cost: $500β$1,000/month for dedicated short codes.
β’ Throughput: Up to 500+ MPS β highest of any US number type.
β’ Best For: High-volume campaigns, voting, sweepstakes, mass alerts where throughput matters most.
β
Whether you need 10DLC, Toll-Free, or Short Code β the registration steps, carrier submission timelines, and approval quirks are different for each. Message Central's experts have registered hundreds of campaigns across all number types. We submit everything correctly the first time, monitor carrier approvals, and notify you the moment you're cleared to send.
β
4. Consent Requirements
β
| Message Type | Required Consent |
|---|---|
| Marketing / Promotional | Prior Express WRITTEN Consent (PEWC) β must be a clear affirmative act (checkbox, keyword opt-in, paper form). Cannot be inferred from a prior purchase. |
| Transactional / Informational | Prior Express Consent (PEC) β providing a phone number in connection with the transaction typically constitutes consent for related informational messages. |
| OTP / Two-Factor Authentication | Generally falls under PEC β the user initiating the authentication action provides the basis. |
β
4.1 Opt-Out Requirements (TCPA + CTIA)
β’ Universal Opt-Out Keywords: STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT. Any of these must trigger immediate opt-out.
β’ Opt-Out Window: 10 business days to process (per FCC 2024 Consent Revocation Order, effective January 27, 2025).
β’ Confirmation Message: Send a one-time confirmation message after opt-out: 'You have been unsubscribed from [Brand]. No further messages will be sent.' No marketing content in this message.
β’ HELP Keyword: Must trigger a response with the brand name, customer service contact, and opt-out instructions.
β’ No Re-Enrollment Trap: Do not immediately re-enroll opted-out users or use dark patterns to circumvent opt-out.
β
5. Content Restrictions (SHAFT + CTIA)
The SHAFT categories are strictly prohibited across all US carriers and platforms:
β’ S β Sex: Adult content, pornographic material, sexual services.
β’ H β Hate: Hate speech, discrimination, content promoting violence against groups.
β’ A β Alcohol: Promotion of alcohol (especially to minors).
β’ F β Firearms: Promotion or sale of firearms, ammunition, illegal modifications.
β’ T β Tobacco/Cannabis/Vaping: Promotion of tobacco products, cannabis, or vaping devices.
β
Additionally prohibited:
β’ Payday loans, high-interest short-term lending, debt collection using threats
β’ Phishing, fraud, smishing β impersonating brands or government entities
β’ Multi-level marketing (MLM) or pyramid schemes
β’ Lead generation aggregators routing opt-in lists across multiple brands
β’ 'Get rich quick' or investment fraud schemes
β’ No URL shorteners: Public shorteners (bit.ly) are blocked by carriers. Use full branded URLs.
β
6. Sending Best Practices
β’ Respect Quiet Hours: No legally mandated nationwide quiet hours under TCPA, but best practice is 8:00 AM β 9:00 PM recipient local time. Some state laws impose stricter windows.
β’ Message Frequency: State message frequency clearly at opt-in (e.g., 'Up to 4 msgs/month'). Don't exceed it without updating the consent disclosure.
β’ Sender Identification: Every message should clearly identify your brand.
β’ Keep Messages Relevant: CTIA guidelines require message content to match the declared campaign use case. Off-topic messages trigger carrier filtering.
β’ Honour Opt-Outs Immediately: Although 10 business days is the formal window, honour opt-outs as fast as technically possible β ideally in real time.
β’ Scrub Against DNC Lists: Regularly scrub your lists against the National Do Not Call Registry for voice and against your own suppression lists for SMS.
FCC National Do Not Call Registry
β
7. Penalties
β
| Violation | Consequence |
|---|---|
| TCPA β per violation | $500 (negligent) to $1,500 (wilful) per message |
| TCPA β class actions | Commonly millions to hundreds of millions USD for large campaigns |
| FCC Enforcement Orders | Cease-and-desist, injunctions, civil monetary penalties |
| State law penalties (e.g., FTSA) | $500 per text; up to $1,500 for wilful violations |
| T-Mobile non-compliance fees | $1,000β$10,000 per violation |
| Carrier blocking | Immediate traffic suspension for policy violations |
| TCPA β FCC 2024 Revocation Rule | Violations of the 10-business-day opt-out window = TCPA violation |
8. Compliance Checklist
β’ [ ] Brand registered on The Campaign Registry (TCR) β $4 one-time
β’ [ ] Campaign registered on TCR β use case, opt-in method, sample messages, opt-out language
β’ [ ] Carrier vetting completed (standard or enhanced)
β’ [ ] Phone numbers assigned to approved TCR campaign
β’ [ ] Prior Express Written Consent (PEWC) obtained for all marketing recipients
β’ [ ] Opt-in disclosure clearly states: brand name, message frequency, 'msg & data rates may apply', opt-out instructions
β’ [ ] STOP / HELP keywords configured and tested
β’ [ ] 10-business-day opt-out processing confirmed (per FCC 2025 Revocation Rule)
β’ [ ] No SHAFT content in any campaigns
β’ [ ] No public URL shorteners β full branded URLs only
β’ [ ] Message content matches declared TCR campaign use case
β’ [ ] Sending hours respect recipient time zone (8 AM β 9 PM local)
β’ [ ] Legal counsel reviewed programme for TCPA and applicable state law compliance
β
9. Authoritative Sources
β’ FCC β Stopping Unwanted Calls and Texts
β’ TCPA β 47 U.S.C. Β§ 227 Full Text
β’ FCC 2024 Consent Revocation Order
β’ FTC Telemarketing Sales Rule
β’ CTIA Messaging Principles & Best Practices
β’ The Campaign Registry (TCR)
β’ T-Mobile Code of Conduct
β’ FCC National Do Not Call Registry
β’ CCPA β California AG
This document is for informational reference only and does not constitute legal advice. Β© 2026 Message Central.
β