USSD Banking Platforms

Why USSD still carries the volume

It is tempting to treat USSD as legacy. In Tanzania it is closer to the opposite: for a large part of the adult population it is the only banking channel that works. It runs on any GSM handset, needs no data bundle, no app install and no smartphone, and it holds up where a data connection will not. For a customer in a district where coverage is thin and airtime is bought in small amounts, that is the difference between an account they use and an account they opened once.

The commercial argument follows the same line. Mobile money habituated most of the market to short menus and PIN confirmations long before banking apps arrived, so the interaction is already familiar to your customers. An institution serving only smartphone customers is competing for a slice of the market while the wallet providers serve all of it.

For banks, SACCOs and microfinance institutions with members outside the major towns, this is usually the channel that decides whether digital adoption reaches the whole book or only the urban part of it.

What your customers can do on it

A USSD channel is worth having only if customers can finish what they came to do. A menu that stops at balance enquiries sends every real transaction back to a branch or an agent, and the channel turns into a cost rather than a service.

The journeys we typically deliver cover balances and mini statements, transfers between own accounts and to other customers, transfers to other banks and to mobile money wallets, bill and utility payments, merchant payments, airtime and bundle purchase, loan enquiry and repayment, standing instruction management, and PIN and profile self-service. Which of those launch first is a decision we make with you, based on what your customers actually queue up in branches to do.

Beyond the transaction list, the things customers notice are whether the menu is short, whether the confirmation makes it obvious what is about to happen, and whether a failure explains itself. Those are product decisions, and they are where most of the design effort goes.

Where it sits alongside your other channels

USSD rarely stands alone. It runs beside a mobile app, internet banking, agency banking and your branch network, and customers move between them without thinking about it. Someone who opens an account on a smartphone may still transact on USSD when they travel, and an agent may serve a customer who has never used either.

That means the products a customer sees should be the same product wherever they meet it. The same limits, the same fees, the same account. When channels are commissioned separately by different vendors at different times, they drift, and the drift reaches customers as being told different things depending on how they asked.

We build across these channels, so a USSD engagement can either fit into what you already run or be the first step of a wider programme. Either way we scope it against the channels you have rather than in isolation.

What launching a USSD service involves

Reaching customers through USSD is a commercial and regulatory arrangement as much as a technical one. Your service needs a short code, allocated within the national numbering plan that the Tanzania Communications Regulatory Authority administers, and an agreement with each mobile network operator whose subscribers you want to serve.

There are two routes into the networks. Going to each operator directly gives you the most control and the most direct relationship, at the cost of a separate agreement for each. Going through an aggregator gives you reach across several networks on one arrangement and is usually quicker to launch, at the cost of a party between you and the operator. The right answer depends on your timeline, your intended reach and your appetite for managing those relationships. We will talk it through with you before you commit.

These arrangements sit with you rather than with us, and they are frequently the longest lead time in the whole project. Starting them early is the most useful thing you can do while the rest of the work is being scoped.

Working with us

We start with discovery: understanding your customers, your products and the constraints you actually operate under, then agreeing what the channel must do at launch and what can follow. You get a scope and a plan out of that, and the plan is yours whether or not we go on to build it.

Through delivery you see working software in an environment you control rather than status reports, and the source code and documentation are yours from the first commit. We support the channel in production afterwards and train your team to take on as much of it as you want. There is no lock-in, by design and by contract.