---
title: "Bulk SMS in Nepal: NTA Rules, Sender ID and Nepali Unicode"
description: "Bulk SMS Nepal guide: NTA and its A2P SMS notice, sender ID with Nepal Telecom and Ncell, consent practice, and Nepali Devanagari Unicode message length."
canonical: "https://omnichannels.ai/blog/bulk-sms-nepal-guide/"
language: "en"
updated: "2026-11-06"
publisher: "BroadNet Technologies"
brand: "OmniChannels.ai"
category: "sms"
primaryQuery: "bulk sms nepal"
keywords: ["bulk sms nepal", "sender id nepal", "nta sms rules", "nepal telecom ncell sms", "nepali unicode sms", "a2p sms nepal", "otp sms nepal"]
published: "2026-11-06"
author: "OmniChannels.ai Editorial Team"
reviewer: "BroadNet Messaging Solutions Team"
readingMinutes: 10
answer: "To send bulk SMS in Nepal, use a provider with licensed routes to Nepal Telecom and Ncell, register your alphanumeric sender ID (up to 11 characters) through the operators, and send marketing only to people with verifiable opt-in. Nepali in Devanagari script is Unicode, so a single message holds 70 characters (67 per part) instead of 160. The Nepal Telecommunications Authority has warned against unauthorised A2P SMS termination."
takeaways: ["The regulator is the Nepal Telecommunications Authority (NTA); our regulation data lists sender ID requirements as set by the operators, with a typical lead time of 7 to 14 business days and alphanumeric IDs up to 11 characters, with local script supported.", "In July 2025 the NTA warned against unauthorised international A2P SMS termination, citing the Telecom Act 2053: only licensed companies may terminate SMS. Choose a provider with legitimate, licensed routes.", "Two operators carry mobile traffic in our coverage data, both with direct routes: Nepal Telecom (429-01) and Ncell (429-02).", "Nepali in Devanagari script is Unicode: 70 characters per single message and 67 per part when split. Romanised Nepali and English fit GSM-7 at 160 (153).", "Our regulation data calls for verifiable opt-in and records no regulator-published time-of-day window for promotional SMS; schedule promotions for local daytime and keep OTPs on a transactional route."]
faq: 
  - q: "Is bulk SMS legal in Nepal?"
    a: "Yes, businesses send OTPs, alerts and marketing by SMS. The caution is about routes: the NTA said in July 2025 that under the Telecom Act 2053 only licensed companies may provide SMS termination, and that it would act against illegal A2P termination. Use a provider with legitimate routes to Nepal Telecom and Ncell, and keep consent records."
  - q: "Do I need to register a sender ID in Nepal?"
    a: "Plan on it. Our regulation data says alphanumeric sender IDs, up to 11 characters, are set up through the operators and that BroadNet confirms the current requirements during onboarding, with a typical lead time of 7 to 14 business days. Timing is not guaranteed, so test delivery on both networks before a launch."
  - q: "Does Nepali text use GSM-7 or Unicode?"
    a: "Nepali written in Devanagari script is Unicode, so one message holds 70 characters and 67 per part when split. Nepali written in Latin letters (romanised) and English fit GSM-7 at 160, or 153 per part. Choose by audience: Devanagari is more readable, romanised text is cheaper in parts."
  - q: "Who are the mobile operators in Nepal?"
    a: "Our coverage data lists two networks with direct routes: Nepal Telecom (429-01) and Ncell (429-02). Read delivery reports for each, because a blended figure can hide a weak network. Confirm the current operator landscape with your provider before you plan volumes."
  - q: "Do I need consent to send promotional SMS in Nepal?"
    a: "Treat consent as required. Our regulation data calls for verifiable opt-in and categorises traffic by use case at registration, with a STOP keyword for opt-out. We did not verify a specific Nepali statute on marketing consent, so keep a record of when and how each number agreed and ask Nepali counsel about edge cases."
  - q: "Can I send SMS to Nepal from an international platform?"
    a: "Only through a route that is permitted. The NTA's July 2025 notice warns that unlicensed parties may not terminate A2P SMS through licensed networks. Ask your provider how traffic reaches Nepal Telecom and Ncell, and avoid routes that cannot explain their licence and sender ID handling."
sources: 
  - title: "Nepal Telecommunications Authority (NTA)"
    url: "https://www.nta.gov.np/"
  - title: "NTA warns against unauthorized termination of international A2P SMS in Nepal, Nepali Telecom (news report, 24 July 2025)"
    url: "https://www.nepalitelecom.com/2025/07/nta-warns-against-unauthorized-termination-of-international-a2p-sms-in-nepal.html"
  - title: "Unicode Standard: Devanagari block (U+0900 to U+097F)"
    url: "https://www.unicode.org/charts/PDF/U0900.pdf"
  - title: "3GPP TS 23.038: Alphabets and language-specific information"
    url: "https://www.3gpp.org/dynareport/23038.htm"
---

# Bulk SMS in Nepal: NTA Rules, Sender ID and Nepali Unicode

Canonical: https://omnichannels.ai/blog/bulk-sms-nepal-guide/
Language: en
Publisher: OmniChannels.ai by BroadNet Technologies

This guide is for banks, e-commerce, education and operations teams that want to send business SMS to Nepali mobile numbers: OTPs, payment alerts, reminders and promotions. It explains who regulates SMS, what the NTA's 2025 notice means for route choice, how sender IDs work, and how Nepali script changes message length. It is a practical overview, not legal advice; confirm requirements with Nepali counsel and the operators before launch.

## What rules apply to bulk SMS in Nepal?

Telecom regulation by the NTA and the operators' own policies decide most of what happens to a business SMS in Nepal. We did not find a single statute named as a bulk or marketing SMS law, and we have left out any data-protection or consent claims we could not verify from an official text.

| Layer | What it covers | Where to check |
|---|---|---|
| Nepal Telecommunications Authority (NTA) | Telecom regulation and licensing; public notices to operators | [nta.gov.np](https://www.nta.gov.np/) |
| Operators (Nepal Telecom, Ncell) | Routes, sender ID set-up, filtering | Your provider, at onboarding |
| Your own consent records | Evidence that each recipient agreed to marketing | Your CRM and sign-up flows |

Our regulation data lists the Nepal Telecommunications Authority as the regulator. It records that sender ID requirements are set by the operators, so the rule that matters on launch day is the one the operator route enforces. NTA notices appear on its website, so check it before large campaigns.

## What did the NTA say about A2P SMS routes?

In July 2025 the NTA warned against unauthorised delivery of international application-to-person (A2P) SMS in Nepal. **A2P SMS** is a message sent by an application, such as a bank or shop system, to a person's phone, as opposed to person-to-person texts.

As reported on 24 July 2025, the NTA said the Telecom Act 2053 lets only licensed companies provide SMS termination, namely holders of a basic telephone and mobile service licence and an international trunk telephone (ILD) licence. It said some organisations were using licensed providers' networks to terminate SMS without authorisation, and that it would act under the law against entities involved in illegal A2P SMS termination. The NTA's own site also carries an October 2020 notice telling operators not to send or allow misleading messages.

We cite a news report of the July 2025 notice and not the notice text, so read the original on the NTA site if the exact wording matters to your contract. What it means in practice:

- **Ask where traffic terminates.** A provider should explain how messages reach Nepal Telecom and Ncell. Grey routes are a known source of blocked or altered messages; read our explainer on [grey routes versus direct routes](/blog/grey-route-vs-direct-route-sms/).
- **Do not rely on cheap, unexplained routes** for OTPs, because they can be filtered or switched off without notice.
- **Keep sender IDs and content consistent** with what was registered.

## How do sender ID registrations work in Nepal?

Business SMS to Nepal uses an alphanumeric sender ID of up to 11 characters, and our regulation data notes that local script is supported. The requirements are set by the operators and confirmed at onboarding. Our published lead time is 7 to 14 business days. Treat it as typical, not guaranteed.

| Step | What to do |
|---|---|
| 1. Classify | Decide which traffic is transactional (OTP, alerts) and which is promotional, and plan one sender ID for each |
| 2. Choose names | Use your registered business or brand name; avoid names that imitate banks, operators or government bodies |
| 3. Prepare documents | Business registration papers and an authorisation letter naming the sender IDs and your provider |
| 4. Submit | Your provider files with the operators; track each approval |
| 5. Test | Send an OTP and a promotion to Nepal Telecom and Ncell handsets |

Our [sender ID letter generator](/tools/sender-id-letter-generator/) drafts the authorisation letter, and you can check the current position with the [sender ID checker](/tools/sender-id-checker/) or the [Nepal sender ID page](/sender-id/nepal/). If you want us to prepare and file the registration with you, see [registrations](/services/registrations/); approval decisions stay with the operators and regulators. The background on formats is in our guide to [sender ID types](/blog/sms-sender-id-types-explained/).

## What does consent look like for Nepal SMS?

Our regulation data requires verifiable opt-in, categorises traffic by use case at registration and handles opt-out with a STOP keyword. It also records that template approval, similar to the system used in some other markets, applies in several countries. It does not state that a Nepali statute sets a particular marketing-consent standard, and we could not verify one, so we describe practice and not a legal rule.

A safe routine:

1. **Capture consent with a record:** the exact wording shown, date and time, channel and number.
2. **Say who is sending and why** at sign-up, for example "Offers from Himal Cafe by SMS".
3. **Honour opt-outs immediately** and keep one suppression list across campaigns and channels.
4. **Keep records** so you can respond to an operator or regulator query.
5. **Do not buy lists.** Purchased numbers have no consent trail.

Our [opt-in consent generator](/tools/opt-in-consent-generator/) drafts sign-up wording in plain language, and the guide to [opt-in consent across channels](/blog/opt-in-consent-multichannel-campaigns/) shows how to record it.

## Which operators carry SMS in Nepal?

Two mobile networks appear in our coverage data, each with a direct route:

| Operator | MCC-MNC |
|---|---|
| Nepal Telecom (NTC) | 429-01 |
| Ncell | 429-02 |

Read delivery reports per operator, not just a blended rate. A healthy overall figure can hide a weak network, and our guide to [improving SMS delivery rates](/blog/sms-not-delivered-improve-delivery-rate/) shows how to diagnose it. Public sources disagree on whether other mobile brands still operate, so confirm the live list with your provider rather than assuming it. For neighbouring markets with a similar structure, see our guides to [Bangladesh](/blog/bulk-sms-bangladesh-guide/) and [Pakistan](/blog/bulk-sms-pakistan-guide/).

## How should you separate OTP and promotional traffic?

Keep OTPs, payment confirmations and other service messages on a transactional sender ID and route, and promotions on their own. A promotion inside an OTP puts your login codes at risk if the route is filtered, and it can confuse customers about what is safe to act on.

| Traffic | Example | Practice |
|---|---|---|
| Transactional | OTP, payment confirmation, delivery alert | No promotion inside; own sender ID; any hour |
| Promotional | Sale, new product, loyalty offer | Consented numbers only; opt-out in the message; daytime schedule |
| Mixed | "Your order shipped. Get 10% off next time" | Avoid; the offer makes it promotional |

Keep OTPs short, never ask the recipient to reply with a code, and say that staff never request it. For design and security, read our [OTP authentication messages guide](/blog/otp-authentication-messages-guide/) and the article on [SMS pumping fraud prevention](/blog/sms-pumping-fraud-prevention/).

## How does Nepali Devanagari affect SMS length?

Nepali written in Devanagari script is Unicode, so a single message holds 70 characters, or 67 per part when split. English and romanised Nepali (Nepali written in Latin letters) fit the default GSM 7-bit alphabet at 160 characters (153 per part). **Devanagari** is the script used for Nepali, Hindi and several other languages; its characters sit in the Unicode block U+0900 to U+097F, which is outside GSM-7. See [GSM-7](/glossary/gsm-7/), [Unicode SMS](/glossary/unicode-sms/) and [concatenated SMS](/glossary/concatenated-sms/) for definitions.

| Encoding | Single message | Per part when concatenated |
|---|---|---|
| GSM 7-bit | 160 characters | 153 |
| Unicode (UCS-2) | 70 characters | 67 |

These examples were counted against the limits (Himal Cafe is a synthetic business; the Nepali wording is illustrative, so have a native speaker review your final copy):

| Message | Encoding | Characters | Parts |
|---|---|---|---|
| `Himal Cafe: Yo Shanibar duita coffee kinda euta free. Details: himalcafe.example/s Rokna STOP pathaunus` | GSM-7 | 103 | 1 |
| `हिमाल क्याफे: तपाईंको अर्डर #1042 तयार भयो।` | Unicode | 43 | 1 |
| `तपाईंको हिमाल क्याफे कोड 482913 हो। ५ मिनेटसम्म मान्य। कसैलाई नदिनुहोस्।` | Unicode | 72 | 2 |
| `हिमाल क्याफे: यो शनिबार दुई कफी किन्दा एउटा निःशुल्क। विवरण: himalcafe.example/s रोक्न STOP पठाउनुहोस्` | Unicode | 102 | 2 |

The third row shows how easily a Devanagari OTP tips from one part to two: it is 72 characters against a limit of 70. Trim the wording or the brand name so the code fits in one part. Mixed messages also count as Unicode as soon as a single Devanagari letter appears. Check final copy in the [SMS character counter](/tools/sms-character-counter/). For other scripts see [SMS character limits and Unicode](/blog/sms-character-limits-unicode-arabic/).

Remember that handset display of Devanagari depends on fonts and the phone, so test conjunct characters (for example क्ष and त्र) on common devices before sending a large campaign.

## When should you send?

We have not found a regulator-published time-of-day window for promotional SMS in Nepal, and our regulation data records none. Agree sending hours with your provider and the operators, send promotions in local daytime (Nepal Time, UTC+5:45) and avoid late evenings. OTPs and alerts can go at any hour. The [send time planner](/tools/send-time-planner/) helps schedule campaigns, and our [SMS marketing rules by country](/blog/sms-marketing-rules-by-country/) article compares hours across markets.

## A worked example: a Kathmandu online shop

"Himal Cafe" (synthetic) sells coffee online and runs a loyalty app.

- It registers two sender IDs, one for transactional and one for promotional traffic, and tests both on Nepal Telecom and Ncell.
- It collects consent in the app and at checkout, storing wording, timestamp and number, and shows "Offers by SMS" with an opt-out instruction.
- OTPs are short Devanagari or romanised messages, written to fit one part.
- The weekly offer is checked against the suppression list and scheduled for local daytime.
- It uses a provider that can explain how messages reach both operators, in line with the NTA's 2025 warning.

## What are the common mistakes?

- **Choosing a route by price alone.** Unlicensed termination is exactly what the NTA warned about.
- **Treating Devanagari like English.** The limit is 70 characters, not 160.
- **No consent evidence.** Without a timestamp and source you cannot answer a complaint.
- **Look-alike sender names.** Names that imitate banks, operators or government bodies risk blocking.
- **Mixing OTP and promotion on one sender ID.**
- **Treating lead times as promises.** Plan buffer beyond 7 to 14 business days.

## How OmniChannels.ai helps

OmniChannels.ai is powered by BroadNet, which has direct routes to Nepal Telecom and Ncell in our coverage data. We prepare and file sender ID registration with you, support Unicode text and give you per-operator delivery reports, with SMPP 3.4 for high volume. For indicative list prices, see the [Nepal SMS pricing page](/sms-pricing/nepal/), then [book a demo](/demo/). Small team? Our [SMS marketing guide for small businesses](/blog/sms-marketing-small-business-guide/) covers the basics.
