USSD and rewards in Africa: the infrastructure that reaches everyone
WhatsApp gets the attention. USSD reaches 600 million people who don't have smartphones or data plans. If your reward programme can't work on USSD, it can't work in most of Africa.
Every conversation about digital engagement in Africa eventually mentions WhatsApp. It's everywhere — 500 million users, used for everything from customer service to bank notifications to family group chats. The instinct to build reward delivery on WhatsApp is understandable.
But WhatsApp requires a smartphone. Smartphones require data. Data requires money, coverage, and a device worth at least $80. For a significant portion of the population across Nigeria, Ghana, Kenya, Tanzania, Uganda, and Ethiopia — including the factory workers, market traders, field sales reps, and informal economy participants who are often the intended recipients of reward programmes — none of these conditions are reliably met.
USSD requires none of them. That's the entire point.
USSD doesn't require a smartphone, a data plan, or an internet connection. It runs on any mobile phone made in the last 25 years.
What USSD actually is
USSD stands for Unstructured Supplementary Service Data. The name is obscure. The experience is familiar to anyone who has ever dialled *737# to check their bank balance in Nigeria, or *144# to check their MTN airtime in Ghana, or *100# to access Safaricom services in Kenya.
It's a real-time session between a mobile phone and a server, initiated by dialling a short code beginning with * and ending with #. The session is synchronous — the phone and server exchange messages in real-time — and requires no data connection. It runs entirely over the voice/signalling channel that exists on every mobile network.
The user experience looks like this:
User dials: *737*REWARD#
System:
Welcome to QIFTS Rewards Enter your reward code:
User enters:
QFT-8821-NG
System:
You have ₦5,000 to spend Choose a category: 1. Grocery 2. Electronics 3. Fashion 4. Connectivity
User enters:
1
System:
Your ₦5,000 grocery code: SHP-4471-8822-9103 Use at Shoprite, Spar, or Justrite Valid 90 days
The entire interaction takes under 60 seconds. No data. No smartphone. No app. Works on a ₦3,000 Nokia feature phone bought at a roadside market.
Why this matters for reward programmes specifically
The answer depends entirely on who your recipients are. Let's be specific.
FMCG trade incentives and distributor rewards
If you're an FMCG brand rewarding distributors, trade partners, or the retailers who stock your products — a significant portion of these recipients are small shop owners, market traders, and informal retailers. They have phones. They're registered on a mobile network. They may not have regular internet access. An email-delivered reward card lands nowhere. A USSD-accessible reward code works perfectly.
Factory and field staff recognition
Manufacturing companies, logistics firms, and agricultural businesses often want to recognise frontline workers — the people on the floor, in the field, or on delivery routes. These are often not office workers with corporate email addresses. USSD reaches them directly on their personal number.
Mass-market consumer promotions
FMCG promotions — buy two, get a reward code on the pack — need to work for every consumer who buys the product, not just the smartphone-owning segment. In Nigeria, smartphone penetration is around 40%. That means an app-only or email-only redemption flow excludes 60% of your intended audience from the start.
Rural electrification and utility rewards
As utility companies in Nigeria, Kenya, Tanzania, and Uganda roll out reward programmes for on-time bill payment and energy conservation, their customer base extends deep into peri-urban and rural areas. USSD is the only channel that reliably reaches this population.
The coverage equation
WhatsApp: ~40% of the target population in most sub-Saharan African markets. Email: lower still. USSD: effectively any phone that can make calls — which is over 95% of mobile subscribers. The coverage difference isn't marginal. It's the difference between a programme that reaches everyone and one that reaches a slice.
USSD vs WhatsApp vs SMS — the right channel for each situation
This isn't an argument that USSD is better than WhatsApp. It's an argument that the right channel depends on your recipient profile — and that USSD needs to be in your toolkit, not treated as a legacy fallback.
The best-run reward programmes in Africa use all three channels, with automatic selection based on recipient profile. For a corporate employee programme, WhatsApp or a branded web link. For a mass-market consumer promotion, USSD with SMS confirmation. For a hybrid programme covering both segments, configurable routing based on recipient data.
The four things a USSD reward flow needs to get right
Session speed
USSD sessions have a timeout — typically 180 seconds. The flow must be simple enough that a recipient can complete it before the session times out. Three to four screens maximum. Clear, plain-language prompts. No branching menus that require eight steps to redeem.
Code delivery before the session
The reward code should be delivered via SMS before the recipient dials in — so they have it in front of them. If they have to remember a long code from a notification they received three days ago, abandonment spikes. SMS + USSD as a paired delivery model is significantly more effective than USSD alone.
Redemption confirmation by SMS
After the USSD session ends, the recipient should receive an SMS confirming their redemption code and where to spend it. The USSD session is ephemeral — once it closes, the information is gone unless it's reinforced by an SMS that stays in their message inbox.
Fallback for session failures
USSD sessions fail. Network congestion, weak signal, user errors. The infrastructure behind the USSD flow needs to handle incomplete sessions gracefully — not marking the reward as redeemed when the session timed out before the user got their code.
QIFTS USSD delivery
How USSD reward delivery works on QIFTS
Full USSD flow documentation — session design, SMS confirmation, fallback handling, and analytics.
The programmatic angle: USSD for trigger-based reward programmes
From a developer's perspective, USSD delivery in a reward programme works like this: the trigger event fires (a purchase is confirmed, a bet is settled, a survey is completed), your system calls the QIFTS API, the API issues the reward card and sends the code to the recipient's number via SMS — and separately opens a USSD prompt on their phone inviting them to redeem.
The recipient sees: a text message with a code, and a USSD prompt. They can redeem immediately via USSD while the notification is fresh, or save the SMS code and redeem later on a different channel. Either way, they got the reward. Either way, the redemption is tracked.
The coverage argument summarised
Building a reward programme without USSD support in Africa is like building a payment system without mobile money support. You can still reach people — just not most of them. For programmes where coverage matters, USSD isn't optional infrastructure. It's baseline.
All delivery channels
USSD, WhatsApp, SMS, web, and POS — all supported
Every channel recipients actually use in African markets. Configure once, route automatically by recipient profile.