The sender ID is the short name customers see at the top of your SMS, such as the name of your bank, shop or school. It builds recognition and trust, and it is also one of the first things reviewers check. A weak or mismatched sender ID is a common reason for registration to stall. This guide explains what a sender ID is, how to pick one and how to prepare for approval.
What is a sender ID?
In India’s DLT framework, a sender ID is called a header. It is registered against your business, which is the principal entity, and it is tied to a message type such as transactional, service or promotional. Your messages are then sent under that header. When a message arrives, the handset shows a short code made up of the registered header, often with an operator-specific prefix and a suffix that indicates the category.
Rules for choosing a name
- Keep it short. Headers are limited in length, and six alphabetic characters is the common format
- Make it recognisable. It should clearly relate to your brand or business name
- Use plain letters. Avoid special characters and unusual spellings
- Do not imitate other organisations, banks or government bodies
- Do not use a generic word that says nothing about your business, if a closer match is available
If your brand name is longer than the limit, choose a sensible abbreviation that customers will connect with you, such as the first letters of each word. Whatever you choose, be ready to explain how it relates to the entity name.
One header or several?
Many businesses register more than one header: one for security codes and transactions, and another for service notices or promotions. Customers then recognise at a glance whether a message is an urgent code or an offer. Separate headers also keep each category’s templates and reporting clean. The trade-off is more registration work. Decide this before you file, because changing it later means a new approval.
What to prepare
- Your principal entity registration, completed and approved first
- The exact header text you want, and one or two backups in case it is taken
- Proof that the name is yours if it is a brand or trademark that differs from your registered name
- A short explanation of how the header relates to your business, for the reviewer
- The message type the header will be used for
The header cannot be approved before the entity it belongs to, so complete the steps in order. Our guide to the DLT registration process shows where headers fit in the sequence.
Common reasons for rejection
- The header does not obviously relate to the registered entity
- It resembles a bank, government agency or well-known brand that you do not own
- It is already registered by another entity
- It uses disallowed characters or the wrong format
- It is registered for one message type but used for another
- Supporting proof of brand ownership is missing or unclear
If your header is rejected
Read the reason given, fix the specific issue and re-submit rather than filing the same text again. If the problem is the name itself, choose a closer variation of your brand name or provide proof of ownership. If another entity holds the name, use a different abbreviation. Avoid filing many variations in a row without understanding the reason, because that only slows things down.
After approval
Once the header is approved, you register message templates under it. Each template is tied to a header and a category, so approval of the header alone does not let you send. Our guide to DLT templates covers the next step. Our promotional versus transactional guide helps you decide which category each header should serve.
Keeping your sender ID healthy
- Use each header only for the message type it was registered for
- Keep a record of the approval for audit and for your own team
- Review your headers when you launch a new brand or product
- Do not share a header with another company, even a related one, unless it is registered for both
Examples of strong and weak headers
A strong header is one a customer would guess. A business called Greenfield Pharmacy might register a short form of Greenfield, because anyone who has dealt with the shop will recognise it. A weak header is one that has no visible link to the entity, such as a random string of letters, or one that borrows the name of a larger brand. If you operate under a brand that differs from your registered company name, say so in your application and have proof of the brand ready.
- Strong: a clear short form of the brand name that matches the entity details
- Acceptable: an abbreviation of the company name that staff and customers already use
- Weak: an unrelated word, a misspelling of a famous brand or a name that implies an official body
Plan the timing
Header approval is only one part of onboarding, and it depends on the entity being approved first. Start the entity registration early, prepare header names and backups while you wait, and file templates as soon as the header is cleared. Doing these in parallel where possible shortens the time before your first live send.
We can help
Orian’s compliance team prepares header applications as part of onboarding, checks them against your entity details before submission and tracks the result. See our DLT registration service for what is included, or contact us to start. Once your header and templates are approved, you can send through the bulk SMS and OTP gateway in the sandbox first and then live.