There's no published rubric for sender ID approval in Nigeria. Nobody at the carriers has written down exactly what goes into a yes or a no. But after several dozen submissions, and a smaller number of rejections, the pattern is clear enough that we can describe it.
What the reviewer is actually checking
Carrier reviewers look at three things: the sender name itself, the stated use case, and the sample message. They're trying to answer a single question: "Does this sender name look like it represents a real business sending the messages it says it will send?"
That's it. It's not a technical review. It's a judgment call by a human, usually one who reviews dozens of requests a day and doesn't have time to dig. Your job is to make the yes easy.
What gets approved quickly
The fastest approvals — sometimes within a day — share three traits:
- The sender name matches the company name. A company called Mackham Payments Limited asking for MACKHAM is an obvious yes. A company called OKP Holdings asking for MACKHAM is a pause.
- The use case is specific. "Customer order confirmations and delivery alerts for our e-commerce business" reads better than "SMS to customers." The former gives the reviewer confidence about what will actually be sent.
- The sample message sounds transactional and ordinary. "Your order #12345 has shipped. Track at mackham.co/t/12345" is instantly readable as a receipt. "Get amazing deals every day!" is not.
What slows things down
If your submission is missing the alignment above, the reviewer may approve but escalate for a second look, which adds days. We've seen three common reasons for delay:
- Vague or missing use case. Reviewers don't hunt for context. If the use case reads like a placeholder, the request goes to the bottom of the queue.
- Mismatched brand. When the sender name doesn't clearly trace to the company on record, the reviewer often sets it aside and either requests clarification or rejects by default.
- Borderline category. Fintech, crypto, gambling, and loan-related sender names get extra scrutiny. The reviewer may request licensing documentation before approving. Budget a few extra days if you're in one of these categories.
What actually gets rejected
Outright rejections are specific. Here's what we see:
Prohibited keywords
Names containing words that signal aggressive promotion: CASH4U, BIGWIN, LOANZZ, INSTACASH, MEGADEAL. Reviewers have seen the same patterns a thousand times and reject them reflexively, because the follow-up is usually a non-compliant promotional send that gets their carrier flagged.
Impersonation risk
A name that looks like it's coming from an entity you don't own. MTN-ALERT from a business that isn't MTN. GTBANK-NEW from a business that isn't GTBank. Even well-intentioned submissions like ZENITH-HR get rejected because the reviewer can't verify you're actually Zenith Bank's HR department.
All digits
A sender ID that is entirely numbers (24247, 9999, 12345) can't be distinguished from a short code. Nigerian carriers reserve numeric senders for their own use. At least one letter is required.
Unclear ownership
If your sender name is generic (SALES, ORDERS, INFO) and your company name is generic (ABC Enterprises), the reviewer has no basis to associate the two. Rejection is common. Pick a name that's distinctive — ideally the name your customers already know you by.
How we write submissions that pass
Here's the format we help our customers assemble:
- Sender name: MACKHAM
- Company on record: Mackham Payments Limited
- Use case: Customer order confirmations, delivery status alerts, and account-activity notifications for registered Mackham customers.
- Sample message: "Your order #81204 has shipped. Track at mackham.co/t/81204. Reply STOP to opt out."
- Allowed classes requested: Transactional, Service update
That submission would land in the 24-hour lane. There's no ambiguity about who the sender is, what they'll send, or whether it belongs on the transactional corridor.
What to do if you get rejected
First, read the reason. We surface it inline in the dashboard. If the reason is a prohibited keyword or impersonation concern, pick a different name — the same request with a tweaked name often gets approved on the second attempt.
If the reason is "unclear use case" or "insufficient information," the fix is your submission, not your name. Expand the use case. Replace the sample message with a more realistic one. Add any licensing or incorporation detail if you're in a scrutinised category.
You don't need to open a new ticket. The resubmit flow in your dashboard takes the existing request and lets you edit the fields. Our system submits the fresh version and tracks it independently.
Things we wish more people knew
- Fridays and Mondays are the slowest. If you submit Friday afternoon, your review might not start until Monday lunchtime.
- Requests submitted during a carrier outage sometimes get lost. We track this and escalate manually.
- Approvals are per-carrier but coordinated. In Nigeria, getting approved on MTN typically means you'll be approved on the others too, but not always simultaneously.
- A previously rejected name can sometimes be approved later if you resubmit with a stronger use case. We've seen this happen several times.
If you're about to submit
Read your sender name out loud. Does it sound like a brand, or does it sound like a pitch? Does it sound like the company you are, or like an impersonation of a company you wish you were? If the honest answer is the former in both cases, submit it.