smspostam
All posts

Compliance

How Nigerian DND regulation actually works

The smspostam team16 April 2026 11 min read

Almost everything you read about DND in Nigeria is either surface-level or wrong. This is our attempt to explain what it actually is, who enforces it, and how it affects anyone sending business SMS.

What DND is

DND stands for Do Not Disturb. In Nigerian telecoms, it's a consumer-protection mechanism administered by the Nigerian Communications Commission (NCC). The premise is simple: a mobile subscriber should be able to opt out of promotional SMS, short calls, and pushed data-bundle offers from their carrier without having to change networks.

The NCC mandated that all Nigerian carriers — MTN, Airtel, Glo, 9mobile — implement the DND register. They did, and they've run it more or less continuously since the mid-2010s. Today it's a fact of life.

How a subscriber gets on DND

The flow is deliberately simple. A subscriber texts a keyword to a short code. Commonly 2442 with a message like HELP, STOP 1 (promotional block), or STOP (full block depending on carrier). The carrier replies to confirm the registration and updates its internal DND register.

From that moment on, inbound SMS to that number is filtered. Messages coming from sender IDs categorised as promotional are blocked at the carrier edge — never reaching the handset. Messages from senders categorised as transactional pass through a separate route.

What "promotional" and "transactional" actually mean

This is where most operators get confused. The two words aren't subjective — they correspond to specific classes that sender IDs are approved for at the time of submission. The classes are:

A sender ID is approved for one or more of these classes. When you dispatch a campaign, you specify which class you're sending — and the route the message takes is determined by that class, not by you choosing a route directly.

The two routes

There are two corridors for outbound traffic into Nigeria:

The DND corridor is not a loophole. It's a carrier-sanctioned path for messages the carriers have agreed a subscriber would want to receive even if they've opted out of promotions. An OTP isn't promotional. An appointment reminder isn't promotional. A delivery update isn't promotional. All of these reach DND-registered numbers.

What carriers enforce, and what they don't

Carriers enforce classification. They don't enforce intent. If you classify a marketing message as transactional and try to route it on the DND corridor, the carrier doesn't read the body to catch the lie — it trusts the class you declared. But the consequence is severe: persistent misclassification gets your sender ID flagged, and eventually revoked.

We don't let you misclassify on our platform. The preflight check matches the message content against the declared class and flags mismatches before dispatch. It's not foolproof — a cleverly-worded marketing message can masquerade as a service update — but it catches the obvious cases, and it keeps our provider account clean enough that we can keep operating.

Common misconceptions

Because DND is poorly explained in most operator documentation, three beliefs keep coming up. All three are wrong.

1. "I need to remove DND numbers from my marketing list"

You don't. The carrier does the filtering. If you send a marketing campaign to a list that has 30% DND-registered numbers, the carrier blocks those 30% and delivers to the other 70%. You're not charged for the blocks. Your delivery report shows them as DND-blocked. There's no extra hygiene step you need to perform on your list.

2. "I can buy a DND-cleaned list"

There are people who sell "DND-safe" lists. These are not legitimate. The DND register is not a file you can export, and no third party has real-time access to it. What these sellers offer is either stale (a snapshot months out of date, not enforceable) or fabricated (a random subset of numbers labelled as "non-DND"). Neither helps you.

3. "OTP and transactional are the same thing"

Close, but not identical. OTP is a specific sub-class for login codes and verification — time-sensitive, short, highly regulated. Transactional is broader: order alerts, receipts, account changes. Both reach DND numbers, both route on the DND corridor, but OTP has tighter carrier scrutiny. A sender ID approved only for transactional can't send OTPs, and vice versa.

What this means for your business

The practical implications:

How smspostam handles it

All of the above is automated on our platform. You pick the message class, we pick the route. Preflight catches obvious misclassification. STOP replies are honored immediately. We keep your sender-ID reputation clean on your behalf, because our provider-account reputation depends on it too.

If you have a specific DND question not covered here, our Help Centre has short task-oriented articles, and our support team answers within a business day.

Send on the right corridor, automatically.

Pick the message class. We pick the route. Preflight handles the rest.

  • Sender IDs approved in 24–72 hours
  • Fund from ₦1,000
  • No monthly minimums