Smart meters, solar systems, vehicle trackers and cold-chain sensors are spreading across Nigeria. Most of them talk to the cloud over mobile data. But data coverage drops, bundles run out and towers get congested. When that happens, a device that can fall back to SMS keeps working: it still sends its alert, and it can still receive a command.
This guide explains why SMS remains a practical channel for Internet of Things (IoT) projects in Nigeria, where it fits, and how to design for it.
Why SMS still suits IoT devices
- It works where data doesn't. SMS travels on the basic GSM signalling network, so it often gets through on weak 2G coverage in rural areas, basements and moving vehicles.
- It needs almost no power or hardware. Low-cost GSM modules send and receive SMS with very little code and battery drain, which suits devices that sleep most of the day.
- It reaches people directly. An alert can go to the device owner's phone without any app, so a farmer, technician or customer sees it on any handset.
- It's simple to integrate. One API call sends a message; a webhook receives replies. No VPN, broker or always-on connection is required.
SMS isn't a replacement for data. It is the dependable backup and the human-facing alert channel next to it.
Common IoT use cases in Nigeria
| Use case | What SMS does |
|---|---|
| Solar and inverter systems | Alerts on low battery, faults or tampering; remote shut-off when a pay-as-you-go plan expires |
| Prepaid electricity meters | Low-credit warnings and token delivery to the customer's phone |
| Vehicle and asset trackers | Geofence and ignition alerts to the owner; “locate” commands sent by SMS |
| Generators and telecom sites | Fuel level, temperature and outage alarms to field engineers |
| Cold chain and pharma | Temperature breaches in fridges and trucks, with time and location |
| Agriculture | Soil moisture and pump status alerts to farmers on basic phones |
| Security and access | Intruder and door alarms; arm or disarm with a coded SMS |
Two ways to use SMS in an IoT system
Device to person. Your platform receives data from devices and sends an SMS to the right person when a threshold is crossed: “Site 14 generator fuel at 12%. Refill within 6 hours.” This is the most common pattern and needs only an SMS API on your server.
Device to platform, and back. The device itself has a SIM. It sends status messages to a number or shortcode when data is unavailable, and your platform replies with commands. Incoming messages reach your server through a webhook, so the device and the cloud stay in sync even offline.
Design tips
- Make SMS the fallback, not the default. Send routine telemetry over data; use SMS for alarms and when data fails for longer than a set time.
- Keep messages short and structured. One page holds 160 standard characters. Use a fixed format devices and people can both read, such as
ALM;TEMP;9.4C;ST14. - Secure commands. Accept commands only from known numbers, include a PIN or signed code, and confirm every action with a reply.
- Throttle alerts. Group repeated alarms so a faulty sensor doesn't send hundreds of messages and drain your balance.
- Track delivery. Use delivery reports to see whether alerts reached the engineer, and escalate to a second contact if not.
- Plan SIM management. Device SIMs need registration like any other line; keep records of which SIM is in which device.
Frequently asked questions
Is SMS fast enough for alarms? Yes. Messages on transactional routes typically arrive in seconds, which is enough for most operational alerts.
Can devices receive commands by SMS? Yes. A device with a SIM can receive an SMS and act on it; your platform sends the command through an SMS API.
How do I receive replies from devices or people? Use a virtual number or shortcode with a webhook, so each incoming SMS is posted to your server.
What does it cost? You pay per SMS page sent, so alert-only designs stay cheap. See current bulk SMS prices.