USSD looks simple on the surface: dial a short code, choose an option and complete a task.
But small design decisions can determine whether a subscriber completes the journey or leaves halfway through.
Long menus, unclear wording, unnecessary steps and session timeouts create friction quickly. For operators, that friction can translate into abandoned transactions, repeated sessions and additional support requests.
Good USSD menu design is therefore not about fitting more options onto a screen. It is about helping subscribers reach the right action with as few decisions as possible.
Here are 10 practical rules for designing USSD journeys people can actually finish.
1. Keep the first menu focused
The first screen should answer one question:
What does the subscriber want to do?
Avoid placing every available service on the opening screen. Start with the most common actions and move secondary services deeper into the flow.
A banking menu, for example, might begin with:
- Balance Check
- Transfer Money
- Bill Payment
- Transactions
- Other
Users immediately understand where to go.
2. Reduce menu depth
Every additional screen introduces another decision and another opportunity for the session to end.
If a common task requires six or seven screens, review the journey.
Frequently used services should normally be reachable near the top of the menu structure. Less common options can sit deeper.
hSenid’s USSD platform includes functionality for tracking frequently accessed operations and presenting them under “My Favorites”, helping users reach regular services faster.
That is a useful design principle even before introducing more advanced personalization: put frequent actions closer to the user.
3. Use language people understand immediately
USSD is not the place for internal product names or telecom terminology.
Compare:
“Initiate fund disbursement”
with:
“Send Money”
The second requires almost no interpretation.
Keep labels short, familiar and action-based.
4. Make every screen easy to scan
Subscribers are working inside a small text interface.
Avoid paragraphs and unnecessary instructions. Each screen should have one clear purpose.
Instead of:
“Please select one of the options below to continue with your account-related banking services”
use:
“Select a service:”
Then show the options.
5. Keep navigation consistent
Do not make users relearn navigation on every screen.
If 9 means Back, keep 9 as Back throughout the journey.
If 0 means Main Menu, use it consistently.
Predictable navigation becomes especially important in longer USSD services where users may need to correct an earlier choice without restarting the entire session.
6. Design for timeouts
USSD sessions are time-sensitive.
A subscriber may pause to find an account number, confirm an amount or read a longer menu. If the session expires, forcing the user to start again creates unnecessary friction.
Session management should therefore be treated as part of UX design.
hSenid’s USSD Gateway includes session-resuming capability for unexpected timeouts, allowing users to return to the most recent menu within a defined period.
That can be particularly useful for payment, banking and multi-step service journeys.
7. Break long content into manageable screens
Sometimes longer information cannot be avoided.
Trying to place all of it on one USSD screen makes the interaction harder to read and navigate.
Pagination is the better approach.
The hSenid USSD Framework can divide longer content across multiple pages and automatically add navigation shortcuts.
The goal is simple: show the subscriber only what they need at that moment.
8. Localize the experience
A well-designed English menu can still fail if the subscriber would rather interact in another language.
USSD platforms should support menu localization without forcing operators to maintain completely separate services.
hSenid’s USSD platform supports multiple languages and localized menu content.
For markets with multiple widely used languages, this is not a cosmetic feature. It directly affects whether people understand each step.
9. Let menus respond to context
Not every subscriber needs to see the same options.
Menus can be adjusted according to factors such as tariff plan, class of service or account balance.
hSenid’s USSD Framework supports dynamic menus using filtering criteria and external triggers, allowing menus to change according to subscriber conditions.
For example, there is little value in showing an offer to someone who is not eligible for it.
Removing irrelevant choices makes the journey shorter.
10. Design around the transaction, not the menu
The final rule is the most important.
Do not start by asking:
“What options should this menu contain?”
Start with:
“What is the subscriber trying to finish?”
Then work backwards.
For a balance check, the shortest useful journey may only need a few interactions.
For a payment, the user may need to select a service, enter an amount, confirm the transaction and receive a result.
Every additional screen should have a reason to exist.
A real deployment shows why this matters
In the Democratic Republic of Congo, a leading bank used an hSenid USSD application to extend digital banking across mobile operators.
The service handled nearly 20,000 transactions per day and allowed subscribers to perform activities including balance checks, transfers, utility payments and wallet-related services.
At that scale, USSD menu design is not simply a UI exercise.
A confusing step affects real customer transactions thousands of times.
The best USSD journeys feel almost invisible. Subscribers dial, choose, complete and leave.
That is the standard operators should design for.
