Getting Started with USSD in Telerivet
Learn how USSD works, what you can build with it, which markets are supported, and what you need to deploy a USSD service
USSD lets users interact with a service by dialing a short code such as *123#, without a smartphone, without an internet connection, and without an app. The session runs over the mobile network's signaling channel, which means it works on any GSM handset with a cellular signal. For organizations serving populations where data access and smartphone ownership are uneven, USSD is often what closes the gap between a messaging program and the people it needs to reach.
For a full introduction to what USSD is and why it still matters in emerging markets, see What Is USSD and Why It Still Matters for Mobile Services in Emerging Markets. This article covers how USSD works in Telerivet specifically, what you can build, and what you need to get started.
How USSD compares to SMS and WhatsApp
| USSD | SMS | ||
|---|---|---|---|
| Requires smartphone | No | No | Yes |
| Requires data connection | No | No | Yes |
| Works on feature phones | Yes | Yes | No |
| Interaction type | Real-time session, menu-driven | Store and forward | Conversational |
| Stored on device after session | No | Yes | Yes |
| Best for | Interactive self-service, account lookups, structured intake | Outbound notifications, alerts, reminders | Rich conversations, support flows |
USSD and SMS are complementary, not competing. A well-designed workflow often uses both: USSD handles the interactive session (a customer checking their balance, confirming a payment, or completing a registration) and SMS handles the outbound follow-up (the confirmation message, the reminder, the receipt). For more on designing multi-channel workflows, see Which channel should you use?.
What you can build with USSD in Telerivet
Telerivet provides two ways to build USSD services, depending on the complexity of your workflow.
Rules Engine lets you build USSD menus visually using a drag-and-drop interface, without writing code. This covers the majority of common USSD use cases: registration flows, account balance checks, menu-driven service selection, and structured data collection.
Cloud Script API lets you write custom JavaScript to handle more complex logic: querying external databases, applying conditional rules, handling dynamic content, or integrating with third-party systems. This is the right option when your USSD service needs to interact with your own backend or apply logic beyond what the Rules Engine supports.
Both methods run on Telerivet's infrastructure, which means you do not need to manage your own USSD server. Telerivet handles session management and can process thousands of concurrent USSD sessions.
Within a USSD workflow, you can also:
- Trigger SMS messages to the contact after a session ends (confirmation, receipt, next steps)
- Transfer airtime directly from within the USSD flow
- Add contacts to groups or update contact fields based on what they entered
- Run campaigns triggered by a completed USSD session
This means USSD does not need to be a standalone channel. It can be the intake point for a broader workflow that continues over SMS or other channels after the session closes. For examples of how mobile money operators and PAYGo solar organizations structure these cross-channel workflows, see How Digital Lenders, Mobile Money Operators, and Insurers Communicate With Customers at Scale and How PAYGo Solar and Agricultural Finance Operators Use SMS as Operational Infrastructure.
Common use cases
| Use case | How USSD fits |
|---|---|
| Mobile money and loan services | Borrowers check balances, confirm payment receipt, or access account options without a smartphone or data plan |
| Beneficiary registration | Field programs register participants, collect survey responses, or confirm field worker check-ins in low-connectivity areas |
| PAYGo solar and utility services | Customers activate services, check account status, or make payment confirmations over USSD while SMS handles outbound reminders |
| Health program intake | Patients or community health workers complete registration or appointment booking flows on any phone |
| PIN-protected account access | Services handling sensitive data use USSD because session content is not stored on the device after the session ends |
What you need to get started
A USSD access code. Deploying a USSD service requires a short code assigned by a mobile network in your country. Telerivet does not issue USSD access codes directly. You obtain one through a USSD gateway provider that manages carrier relationships on your behalf, then connect that code to your Telerivet project.
A supported provider. Telerivet connects to USSD gateway providers with coverage across the following markets:
| Provider | Coverage |
|---|---|
| Africa's Talking | Kenya, Uganda, Tanzania, Rwanda, Nigeria, Namibia, Ghana, Malawi, Zambia, South Africa |
| Infobip | Botswana, Chad, DRC, Eswatini, Ethiopia, Gabon, Ghana, Kenya, Liberia, Malawi, Mozambique, Namibia, Nigeria, Senegal, South Africa, Tanzania, Uganda, Zambia, Zimbabwe |
Telerivet can also integrate with other USSD providers on request. If your target market is not listed above, contact the team to discuss options.
Getting started
Once you have a USSD access code from a supported provider, connecting it to Telerivet follows the same process as adding any other route: go to Routes > Add Route in your project and select USSD. You will need the access code and your provider's API credentials.
From there, you can begin building your service using the Rules Engine for straightforward menu flows, or Cloud Script for more complex logic.
For full configuration steps, see the Telerivet User Guide.
Best practice tip
Design your USSD menus for the shortest possible path to the outcome. Each additional step in a USSD session is a point where a user can lose connectivity, time out, or abandon the flow. The most effective USSD services are narrow in scope: one clear purpose, the minimum number of steps to complete it, and a confirmation at the end. If your use case requires many steps or complex branching, consider whether part of the flow can be handled over SMS after the session closes rather than extending the session itself.
Reach out to your customer success lead or get in touch if you need help scoping a USSD workflow or connecting to a provider in your market.