DLT Sender ID / Header ID Categories & Examples
1. Promotional Sender IDs
Format: 6-digit numeric (auto-assigned by DLT portal)
Purpose: Marketing messages to non-DND numbers
- 562993 – Used by a retail brand for seasonal offers
- 248751 – Used by a travel agency for flight deals
- 495573 – Used by an e-commerce site for flash sales
These IDs are not customizable and are assigned based on your business category.
2. Transactional Sender IDs
Format: 6-character alphanumeric
Purpose: OTPs sent by banks only
- HDFCBK – HDFC Bank OTP messages
- ICICIB – ICICI Bank OTP alerts
- SBIBNK – State Bank of India OTPs
Only banks are allowed to use this category for OTPs.
3. Service Implicit Sender IDs
Format: 6-character alphanumeric
Purpose: Informational messages based on existing customer relationship
- AMAZON – Delivery updates or order confirmations
- ZOMATO – Order status or refund alerts
- MYNTRA – Shipment tracking or return confirmations
No promotional content allowed—purely service-based.
4. Service Explicit Sender IDs
Format: 6-character alphanumeric
Purpose: Service messages sent with customer consent
- TATASK – Subscription reminders from Tata Sky
- NETFLX – Account updates from Netflix India
- CREDIT – Loan or EMI reminders from a finance company
Consent must be recorded and templates approved.
Key Rules for Sender IDs
- Must reflect your brand or business name.
- Case-sensitive:
ABCDEF ≠ abcdef
- Cannot be reused across categories.
- Must be linked to approved templates before use.
New TRAI Guidelines: Sender ID Suffixes
Every SMS Sender ID (Header ID) will now include a suffix that indicates the type of message being sent. This suffix is auto-applied by the DLT system based on your approved template.
| Suffix |
Message Type |
Description |
| -P |
Promotional |
Ads, offers, discounts, marketing campaigns |
| -S |
Service (Implicit) |
Informational messages based on existing customer relationship |
| -T |
Transactional |
OTPs, banking alerts, purchase confirmations (only for banks) |
| -G |
Government |
Official government communications (TRAI-exempted entities only) |
Example: If your Sender ID is MYBRND and you’re sending a service message, it will appear as MYBRND-S on the recipient’s phone.
Key Implementation Notes
- No manual action required: suffix is auto-applied by the DLT platform.
- Suffix is determined by the category of the approved template.
- “Service Explicit” category is being phased out → templates will now fall under -P (Promotional).
- Same Sender ID can be used across categories with different suffixes.
Why This Matters
- Helps recipients instantly identify the nature of the message.
- Reduces risk of phishing and fraud by clarifying message intent.
- Ensures compliance with TRAI’s updated TCCCPR 2025 regulations.
Need Help? Would you like me to draft a Sender ID for your business or suggest the right category? I can tailor it to your brand and use case.