JAMB Profile Code Not Received — The SMS and Email Channel Diagnostic

The JAMB profile code is delivered to the candidate's phone by SMS from the shortcode 55019 or 66019, in response to the candidate's NIN SMS to the same shortcode. When the reply does not arrive, the natural reflex is to assume JAMB has failed to issue the code and to look for a JAMB-side reissue route. In practice the no-show is almost always held up at the candidate-side delivery channel — the SIM, the telco's SMS gateway, the network, or (where email-side notifications are at issue) the registered email account. The right discipline is to work the delivery-channel diagnostic first and route to JAMB-side escalation only after the candidate-side channels are cleared.

This article walks the diagnostic per channel. The companion reference that names the profile code as an identifier and distinguishes it from the JAMB Registration Number, the CAPS Profile and the NIN is the profile code reference; the upstream registration walkthrough that situates the profile code in the full registration sequence is the JAMB registration hub.

The article speaks to the panicked candidate whose SMS to the shortcode has returned nothing — sometimes within minutes of the registration window opening, sometimes hours into a peak-period queue. Three overlapping readers. The first-time UTME candidate who has just sent the NIN SMS and is staring at a phone screen with no reply. The Direct Entry candidate working through the DE registration window and stalled at the profile-code step. The parent or guardian managing the registration logistics on an under-18 candidate's behalf and watching the clock against the closing date of the registration window.

The three-actor framework matters in this article specifically because the route to recovery differs by which actor holds the answer. The candidate fixes input issues (SMS format, airtime); the telco's SMS gateway is the surface where most no-shows actually originate; JAMB itself is the route of last resort.

A profile-code SMS that does not arrive has four common operational causes. Each has a specific diagnostic and a specific recovery sequence.

A fifth, less common cause is a JAMB-side shortcode outage — the JAMB shortcode itself is unresponsive for all candidates simultaneously. This is rare and typically resolves within hours of JAMB's operations team noting it; the JAMB FAQ page and the JAMB social channels carry the notice when it occurs. The candidate-side diagnostic is the same regardless: confirm the candidate-side channels first, then escalate.

Work the diagnostic in order. Each step takes minutes and either delivers the code or rules out a cause cleanly before the next step.

1. 1
   Re-confirm the exact SMS formatOpen the sent-SMS folder on the phone. Re-read the message exactly as it was sent. The canonical format is NIN (uppercase), one space, and the 11-digit NIN with no dashes or spaces inside the digits. Example: NIN 12345678901. If the format was wrong, re-send the SMS in the canonical format. If it was right, move to the next step.
2. 2
   Confirm the SIM has at least ₦100 airtimeCheck the SIM's airtime balance with the operator's balance USSD code (typically *310# on MTN, *123# on Airtel, *124# on Glo, *200# on 9mobile/T2). The SMS to the shortcode is charged at ₦50; ₦100 airtime headroom covers a single retry. If the balance is below ₦100, top up at any agent and re-send the SMS.
3. 3
   Send a normal test SMS to a friend's numberSend any regular text message to a known number. If the test SMS delivers within a minute, the SIM is active and the network is reaching the SMS infrastructure normally; the shortcode is the specific issue. If the test SMS itself does not deliver, the issue is the SIM or the network and the route is the telco's customer-care channel, not JAMB.
4. 4
   Try the alternate shortcodeJAMB operates two shortcodes for profile-code generation — 55019 and 66019. If the original SMS was sent to 55019 and returned nothing, send a fresh SMS in the canonical format to 66019 (and vice versa). The two shortcodes route through different parts of the telco SMS gateway infrastructure; a delay on one often does not affect the other.
5. 5
   Wait 30 minutes during peak periodsIf all the candidate-side checks have cleared and the SMS still has not been answered, give the request 30 minutes during peak registration windows. SMS gateway congestion is a real operational factor on the first days of the registration window; the shortcode reply may simply be queued. Do not re-send the NIN every five minutes — repeated sends compound the cost without speeding delivery.
6. 6
   Try RESEND if a code may have been issued previouslyIf you suspect a code was issued in an earlier SMS attempt that you did not see (perhaps an old phone, an old SIM, or a forgotten attempt), send the single word RESEND from the same phone number to 55019 or 66019. RESEND returns the previously issued code at no additional shortcode-handshake delay. RESEND from a different phone number returns nothing — the binding is to the original sender.
7. 7
   Check the email channel for JAMB-side notificationsWhere the candidate's profile already exists from a prior cycle or where JAMB has flagged the request to the registered email, the channel that becomes available again is sometimes the email rather than the SMS. Sign into the registered email at the inbox, spam, and promotions tabs; some JAMB notifications route through the email channel as a parallel to the SMS gateway.
8. 8
   Escalate to JAMB state office after a 24-hour windowPast a 24-hour window with multiple failed attempts on both shortcodes, with the SIM confirmed active and the candidate-side checks all clear, the diagnostic is candidate-side exhausted and the JAMB state office is the next route. Bring the NIN slip, a government photo ID, the phone with the SMS history, and a written record of the attempts. The state office can route a JAMB-side reissue at the agency's discretion.

A subtle trap at this stage is the candidate who has sent the NIN SMS more than once. JAMB binds the first successful profile code to the sending phone number; a second NIN SMS from the same number typically returns Number Already Registered. The candidate sees no profile code in the inbox and assumes none was issued, when in fact the first attempt produced a code that arrived on a different phone the candidate is no longer holding, was deleted, or was overlooked in the operator-message folder.

The right discipline in this case is RESEND. Send the single word RESEND (no NIN, no other parameter) from the same phone number used for the original NIN SMS to 55019 or 66019. The shortcode will return the existing profile code — the same ten-character code that was issued on the first attempt. The route opens delivery to the same number without paying for a fresh NIN SMS to a shortcode that will refuse it. RESEND from a different phone number returns nothing; the binding is fixed.

A second subtle case: a candidate who switched SIMs (same number, new physical SIM) between the original SMS and the present. The binding is to the phone number, not to the physical SIM, so RESEND from the new SIM on the same number still works. A candidate who changed the number entirely is in a harder spot — the JAMB state office is the route, with the NIN slip and a written request explaining the change.

The candidate-side diagnostic is exhausted when:

• The SMS has been sent in the canonical format to both shortcodes.
• The SIM has at least ₦100 airtime and is sending and receiving regular SMS normally.
• 24 hours have passed since the first attempt, including off-peak windows.
• RESEND has been tried and returned nothing.
• The registered email inbox has been checked (including spam and promotions) and has no JAMB notification.

At that point the JAMB state office in the candidate's state of registration is the right escalation route. The eFacility portal itself — the candidate-side surface for every routine self-service request through the JAMB cycle — is deliberately not the route for a profile-code-no-show reissue:

The portal does not provide a self-service profile-code reissue for a no-show case by design, because a self-service reissue route would invert the SMS-binding fraud-control surface. The state-office route exists precisely because the candidate-side identity needs to be verified by a JAMB officer before a reissue is appropriate.

What to take:

• The original NIN slip (paper) or a printed NIN screenshot from the NIMC MobileID app.
• A separate government photo ID (international passport, driver's licence, or PVC).
• The phone with the SMS history showing the original NIN SMS attempts and any error responses received.
• A written request describing the attempts already made (dates, times, shortcodes tried, error messages or absence of reply).
• The candidate's full name and date of birth exactly as on the NIN.
• The email address registered against the candidate's records.

The JAMB officer at the state office reviews the documentary stack, confirms the candidate's identity, and may issue a fresh profile code through the internal JAMB system. The state-office turnaround on a clean case varies between same-day at high-volume Lagos and Abuja offices and a working week at smaller state offices; the published service window is the floor, not the ceiling.

The profile-code no-show is a candidate-side issue at the start of the registration cycle. The articles that bear on it most directly:

• JAMB profile code reference — the vocabulary anchor for the profile code as an identifier.
• How to register for JAMB — the registration hub that situates the profile code in the full sequence.
• JAMB email linking — the email-as-portal-identity-anchor framework for the email channel side of the diagnostic.
• JAMB password reset — the credential-recovery step where the registered email or the eFacility password is the recovery surface.
• JAMB portal login problem — the session-state-and-credential diagnostic for portal-side issues that surface after profile-code generation.

SMS shortcode rates (₦50) and the airtime guidance (at least ₦100 headroom) reflect telco and JAMB practice current at the 2026 UTME cycle. JAMB state-office processing variance is real — same-day at high-volume offices, a working week at smaller offices — and the published service window is the floor of the operational distribution, not the ceiling. The 24-hour candidate-side window in this article is operational discipline, not a JAMB-published service standard.