USSD Menu Design and Optimisation in Nigeria and Africa: Customer Journey Guide

USSD menu optimisation should help people complete the task they came to do. A longer feature list is not necessarily a better service. Banking, bill payment, ordering and customer self-service journeys need clear choices, understandable outcomes and a workable response when something goes wrong.

Wigmore Trading accepts enquiries for USSD application and customer-journey improvement projects. Share the current menus, intended users and evidence of problems so the team can assess redesign and integration requirements.

Start with the most important tasks

List the actions customers use most often and the problems support receives. Separate essential tasks from information that could be provided elsewhere. Define the outcome for each journey and the system responsible for confirming it.

For a new service, test assumptions with representative users before treating the first menu tree as final. A product team’s terminology may not match the words customers understand.

Keep choices clear and consistent

Use concise labels that describe the action and avoid ambiguous options. Maintain consistent navigation and explain the effect of a choice before a consequential action. Confirm the provider’s actual limits for menu content and supported characters.

Plan language requirements around the intended audience. Translation should preserve the meaning of amounts, dates, instructions and confirmations, not merely replace individual words.

Map input and error recovery

Design for uncertainty

When a back-end request is slow, the interface should not claim a definite success or failure without evidence. Agree how a pending result is communicated and how the customer can check it. Avoid inviting an immediate repeat of a financial action that may already have completed.

The session reliability guide addresses timing and recovery, while the payment guide covers transaction-state requirements.

Use analytics to select improvements

Define which journeys, stages and errors will be measured and what constitutes completion. A high exit rate can have several explanations, including a completed information task. Do not classify every session ending as a failure.

Combine appropriately protected analytics with support evidence and user testing. Make changes against a defined problem and compare outcomes using consistent measures.

Test with realistic users and systems

Include first-time users, language needs, mistakes and interrupted sessions. Test the actual back-end integrations and a representative operating context with the responsible provider. A static menu demonstration does not show how the service behaves under delay or invalid input.

Record whether users understand the result, can recover safely and know how to seek support. Keep sensitive information out of test recordings and shared screenshots.

Control redesign and automation

Maintain a versioned menu map, business rules and approval record. Check that a changed option does not break a downstream process or support script. Agree a rollout and rollback plan with the technical and operations teams.

Workflow automation should preserve authorisation and evidence, particularly for payments or account changes. An interface improvement should not silently expand what the service can do with customer data or funds.

Prepare an optimisation enquiry

Send Wigmore Trading the current menu tree, intended audience, markets, operators, back-end systems and the issue to improve. Include redacted reports or examples and define the desired outcome. We can assess discovery, UX review, development, testing and handover requirements.

For a new platform, begin with the USSD gateway buying guide. For implementation details, use the developer guide to prepare documentation and test requirements.