Almost every Nepali business ends up needing to reach a few thousand people at once: a bank confirming a transaction, a school telling parents about a closure, an online store sending a delivery update. Email gets ignored, app notifications only reach people who installed the app, and calling everyone is impossible. SMS is the one channel that reaches any phone in the country, with no app and no data connection.
This guide covers what bulk SMS actually is, how a message physically gets from your system to an NTC or Ncell handset, what it really costs, how to evaluate a provider, and how to send your first campaign, whether through a dashboard or an API.
What Is Bulk SMS?
Bulk SMS is sending one text message to many recipients at once through a platform built for volume, rather than typing each one by hand on a phone. The message a recipient receives is an ordinary SMS, identical to any other. What changes is everything behind it: how the message is submitted, how it is routed to the carrier, how delivery is tracked, and how it is billed.
A message sent from a personal handset goes out over a consumer plan, from a personal number, with no record of whether it arrived. A bulk SMS platform sends over a dedicated commercial connection to the carrier network, under a registered sender ID carrying your brand name, and returns a delivery status for every single recipient. For a fuller primer, see our practical guide to what bulk SMS is.
How Does Bulk SMS Work?
Four pieces sit between your send button and a recipient's phone. Understanding them explains most of what can go wrong, and most of what you are paying for.
SMS Gateway
The gateway is the service that accepts your message and converts it into the protocol the telecom network speaks. You submit over HTTPS, a dashboard form or an API call, and the gateway handles queueing, retries, throughput limits, and the handoff to the operator. A good gateway also decides which route a message should take when more than one is available, and fails over to a backup route when the primary one rejects a send or stops responding.
Sender ID
The sender ID is the name a recipient sees in place of a phone number. It is a required field on every message, not optional metadata, because the carrier needs something to put in the message header. Both NTC and Ncell accept alphanumeric sender IDs of up to 11 characters, which is why brand names in SMS headers are so often abbreviated.
A shared sender ID is the platform's own generic identity, used by every customer on it. A custom sender ID is your own brand name, which makes your messages instantly recognisable: the difference between an OTP arriving from a name your customer trusts and one arriving from a string of digits they have never seen.
Telecom Network
Nepal has two mobile operators of real consequence for SMS: Nepal Telecom (NTC) and Ncell. Every message you send is destined for one or the other, and a provider needs working connectivity to both. A platform connected to only one operator will silently underdeliver to roughly half your list, which is the single most common reason a campaign appears to fail for no visible reason.
Delivery Report
The delivery report, or DLR, is the acknowledgement that comes back from the carrier for each message: delivered, failed, or still pending. This is what separates bulk SMS from shouting into a void. A delivered status means the handset received it. A failed status usually means the number is switched off, out of service, or invalid. Any provider that cannot show you per-message delivery status is asking you to take their word for it.
Types of Bulk SMS
The technology is identical across all four categories below. What differs is intent, urgency, and how recipients react to them, which is why they are usually worth separating, sometimes even onto different sender IDs.
Promotional SMS
Offers, discounts, festival greetings, new product announcements. Sent to a marketing list, usually in large batches, and not time-critical to the minute. These are the messages recipients are quickest to tune out, so relevance matters far more than frequency.
Transactional SMS
Messages triggered by something the recipient did: an order confirmation, a payment receipt, a shipping update, a bank balance alert. They are expected, they are read, and they are the highest-value use of SMS for most businesses. They also need to arrive promptly, because a delivery notification that arrives after the delivery is worthless.
OTP / Authentication SMS
A one-time password confirming a login, a payment, or a new account. This is the most latency-sensitive category of all; a code that arrives two minutes late has already failed. OTP traffic should never be queued behind a marketing blast. Our guide to how SMS OTP and two-factor authentication work covers this in depth.
Informational SMS
Announcements that are neither selling nor transactional: a school notifying parents of a holiday, a clinic confirming a schedule change, an office announcing a closure. Usually one-to-many, usually not urgent to the second, but expected to actually arrive.
How Much Does Bulk SMS Cost in Nepal?
The most important thing to understand about SMS pricing is that you are not billed per message. You are billed per segment. Every SMS carries a fixed 140-byte payload, and a message longer than that is split into multiple segments and billed as multiple messages.
How many characters fit in a segment depends on the encoding. Plain English uses GSM-7. The moment a message contains a single character outside the GSM-7 alphabet, any Devanagari, an emoji, or a curly quote pasted in from Word, the whole message switches to Unicode and the limit drops sharply.
| Encoding | Single segment | Per part when split |
|---|---|---|
| GSM-7 (plain English) | 160 characters | 153 characters |
| Unicode (Devanagari, emoji) | 70 characters | 67 characters |
The per-part figures drop because a split message has to carry a 6-byte header in every part so the recipient's handset can reassemble them in order. This is why a 200-character English message costs two segments, not one and a bit, and why a 100-character Nepali message costs two rather than one.
The full breakdown, including the pasted-in characters that quietly force a message into Unicode, is in how SMS segments and character limits actually work.
Factors affecting price
- Message length and encoding. The single biggest factor, and the one entirely within your control. Writing in English rather than Nepali can cut the cost of the same message by more than half.
- Monthly volume. A provider's own upstream carrier rates shift with volume, so a business sending five thousand messages a month and one sending five million are genuinely different negotiations.
- Traffic type. Some providers price transactional and promotional traffic differently, because carriers treat them differently.
- Failed-message handling. Ask specifically whether undelivered messages are refunded. A message the carrier rejected cost the provider nothing to deliver, and charging you for it is pure margin.
- Hidden fees. Setup charges, monthly minimums, per-seat licences, or tiers that gate the API behind a higher plan.
Be wary of any quote that does not distinguish per-message from per-segment pricing; it will surprise you the first time somebody sends 200 characters. You can check exactly how a specific message will be billed with our free SMS length calculator, and the economics behind published rates are covered in how bulk SMS pricing in Nepal really works.
How to Choose a Bulk SMS Provider in Nepal
Most providers look identical on a landing page. These are the six things that actually differ, and the questions that expose them.
- Telecom connectivity. Does the provider deliver to both NTC and Ncell? Ask directly. This is the difference between reaching your list and reaching half of it.
- API. Is there a documented REST API, or only a dashboard? Even if you do not need it today, you will the first time you want automated order confirmations.
- Delivery reports. Can you see per-message delivery status, filter it, and export it? A campaign-level success percentage with no underlying detail is not a delivery report.
- Sender ID. Can you register your own brand name, and how long does approval take? Can a sender ID be locked to a specific API token so a compromised key cannot send under your brand?
- Support. When a campaign fails at 9am on a working day, is there a human in the same timezone who can tell you why?
- Pricing. Per segment or per message? Are failures refunded? Is anything gated behind a higher tier?
Bulk SMS API for Developers
A dashboard suits a person composing a message right now. An API suits a message your own software needs to send the moment something happens: an order is placed, a password reset is requested, a payment clears. Most businesses end up using both, as covered in SMS API vs. bulk SMS dashboard.
API example
A send is a single POST. Recipients are an array, so one call can address one number or thousands:
curl -X POST https://api.bulletsms.com/api/v1/sms/send \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-48213-confirmation" \
-d '{
"to": ["9779841000001", "9779851000002"],
"senderId": "BulletSMS",
"message": "Your order 48213 has shipped. Track it at bulletsms.com/t/48213",
"campaignName": "Order confirmations"
}'Add "unicode": true when the message contains Devanagari, and "scheduledAt" with an ISO 8601 timestamp to queue a send for later instead of dispatching immediately.
Authentication
Requests authenticate with a bearer token in the Authorization header. Tokens are issued per integration rather than per account, so a token used by your billing system can be revoked without touching the one your storefront uses. A token can also be restricted to an approved list of sender IDs, enforced on every send, so a leaked key still cannot send under a sender ID it was never granted.
The Idempotency-Key header in the example above makes retries safe. If a network blip causes your code to retry a request it already sent, the same key returns the original result instead of sending the message twice.
Webhooks
Rather than polling for status, register a callback URL and the platform posts events to it as they happen:
campaign.queued: accepted and waiting to dispatchcampaign.sending: dispatch in progresscampaign.completed: every message in the batch has reached a final statemessage.delivered: a specific handset confirmed receiptmessage.failed: a specific message could not be delivered
Deliveries are signed and retried on failure, and every attempt is logged so you can see exactly what was sent to your endpoint and how it responded.
Delivery reports
Any individual message can also be queried directly with GET /api/v1/sms/status/:messageId, which returns its current delivery state. For bulk reconciliation, campaign reports are exportable from the dashboard, filterable by status, operator, and date range.
Full request and response shapes are in the developer documentation.
Bulk SMS Use Cases
- Banks and financial services. Transaction alerts, OTPs for login and payment authorisation, balance notifications, loan and EMI reminders. The highest-volume and most latency-sensitive category in Nepal.
- Schools and colleges. Attendance notifications to parents, fee reminders, exam schedules, result announcements, and closures. SMS reaches guardians who do not use email or a school app.
- E-commerce. Order confirmations, dispatch and delivery updates, cash-on-delivery confirmation calls scheduled by SMS, and abandoned-cart recovery.
- Healthcare. Appointment reminders, which measurably reduce no-shows, plus report-ready notifications and vaccination or follow-up schedules.
- Government and public services. Public notices, emergency and weather alerts, and service announcements that must reach people regardless of smartphone ownership.
- Marketing. Festival campaigns around Dashain and Tihar, flash sales, loyalty offers, and event invitations: effective in short bursts, counterproductive when overused. See SMS marketing best practices, timing, and templates for how to run these well.
Is Bulk SMS Legal in Nepal?
Yes. Sending commercial SMS through a licensed provider is entirely legal, and it is how every bank, telecom, and large retailer in the country already communicates. What matters is how you do it.
Three principles apply almost everywhere, and following them keeps you on the right side of both regulation and your recipients:
- Consent. Send marketing messages to people who gave you their number for that purpose. A number collected for delivery updates is not automatically a marketing list.
- Identification. Send under a sender ID that identifies you honestly. Impersonating another brand is fraud, not marketing, and is the fastest way to lose a sender ID permanently.
- Opt-out. Give recipients a way to stop receiving promotional messages, and honour it. Transactional messages a customer needs, an OTP, a payment receipt, are a separate category and are not what opt-out is meant to cover.
This is also why reputable providers verify who you are before granting access, usually through KYC document checks. It is slower than instant signup, and it is precisely what keeps sender IDs meaningful rather than something anyone could impersonate. Requirements change over time, so confirm current obligations with your provider or the Nepal Telecommunications Authority before launching a large programme.
How to Send Bulk SMS in Nepal
- Create an account and complete verification. Expect to submit business registration documents and confirm your own mobile number. This is a one-time step.
- Register a sender ID. Pick something short and recognisable: your brand name, not a department. You get 11 characters.
- Add credit. Most providers, including this one, work on prepaid credit drawn down per segment sent, with no subscription.
- Build your recipient list. Paste numbers, upload a file, or use a saved contact group. Clean the list first: invalid numbers cost you nothing to send but waste your time in the report.
- Write and check the message. Watch the live character and segment count. Check the encoding before sending, not after; a stray pasted character can triple the cost silently.
- Send or schedule. Dispatch immediately, or schedule for a sensible hour. Marketing messages at 6am do more harm than good.
- Read the delivery report. Check delivered versus failed by operator. A consistent failure pattern on one network is a routing problem worth raising with your provider.
Bulk SMS vs WhatsApp vs Email
These are not competitors so much as tools for different jobs. The deciding factor is almost always what the recipient needs to have installed for the message to arrive at all.
| SMS | |||
|---|---|---|---|
| Requires | A phone number | The app plus internet | An email address, checked regularly |
| Reach in Nepal | Effectively universal | Widespread but not universal | Lower, and skews urban and office-based |
| Best for | OTPs, alerts, anything that must arrive | Two-way conversation, rich media | Long-form updates, receipts, newsletters |
| Length | Billed per segment | Effectively unlimited | Effectively unlimited |
| Cost per message | Low, but never free | Varies by conversation category | Near zero at volume |
In practice: SMS for anything that absolutely has to be seen, WhatsApp where you want a conversation, email where you need length. Most businesses use all three and route by urgency.
Frequently Asked Questions
How many characters is one SMS?
160 for plain English, or 70 if the message contains any Unicode character such as Devanagari or an emoji. Longer messages split into segments of 153 and 67 characters respectively, and each segment is billed.
Can I send SMS in Nepali?
Yes. Devanagari is fully supported and delivers correctly to both NTC and Ncell. It uses Unicode encoding, so plan for 70 characters per segment rather than 160.
How long does sender ID approval take?
It varies by provider and by operator, and is typically measured in working days rather than minutes. Start the process before you need it, not the week of a campaign.
Do I pay for messages that fail to deliver?
You should not. On this platform, failed messages are refunded automatically. Ask any provider this question explicitly before signing up, because the answer is not standard across the market.
Can I schedule messages in advance?
Yes, both from the dashboard and via the API using the scheduledAt field. Scheduling is how most festival and reminder campaigns are actually run.
Is there a minimum purchase or monthly commitment?
Not here. Credit is prepaid and drawn down by what you actually send, with no subscription, seat fees, or monthly minimum.
How fast do messages arrive?
Transactional and OTP messages typically arrive within seconds. Large promotional batches are dispatched at a throughput the carrier accepts, so a very large campaign completes over minutes rather than instantly.
Conclusion
Bulk SMS remains the most dependable way to reach people in Nepal, because it asks the least of them: a phone number and nothing else. No app, no data connection, no account.
The parts worth getting right are the unglamorous ones: connectivity to both operators, a sender ID your customers recognise, per-segment billing you can verify, and delivery reports detailed enough to act on. Get those right and SMS stops being a cost line and starts being infrastructure.
If you want to see the numbers behind a specific campaign before committing to anything, the SMS length calculator shows exactly how your message translates into billable segments. When you are ready to send, you can create an account or read the developer documentation to start with the API.