The menus in Symba USSD are configured for each organization. A client sees only services that are enabled and relevant to their accounts or role.
Organizations may make selected services available before authentication, such as:
When Symba Workflow is used for an application, Symba USSD collects the configured information and saves the application for staff completion or review. Saving an application does not mean that it has been approved.
When client registration includes a fee, Symba Workflow creates the pending client and charge after saving the final answer. Symba USSD durably queues the payment request before confirming that it is being prepared. Symba Workflow then asks Symba Payments to initiate the request asynchronously. A queued request does not mean the payment provider accepted it or that the fee was paid. Symba USSD then ends the session so the mobile-money prompt can appear. A saved application may instead report that payment could not be started; automatic recovery can continue without creating another application, client, or charge.
If a client registration session is interrupted, the same caller can resume the unfinished application. Symba USSD uses the caller's normalized phone number to find the application and continues at the next configured question. A different caller starts a separate application. Once registration details have been saved, later retries reuse the existing application, client, charge, and payment state instead of creating duplicates.
Applications started in Symba USSD enter Processing immediately. For an individual loan application, Symba Workflow uses the applicant phone number to link the application automatically when it uniquely identifies one active Symba Microbanking client. A caller applying for someone else is matched using that applicant's phone number.
An organization may configure a final loan consent statement. When configured, Symba USSD displays the immutable terms and explicit Accept and Decline choices after all application details have been collected. Acceptance is recorded before matching, related onboarding, fee collection, or submission continues. The caller may accept while applying for themselves or for another applicant when the organization's policy permits delegated submission.
Declining consent ends the current session without withdrawing or submitting the saved application. The same caller can resume the application at the consent step later. If staff change consent-relevant application data, the previous acceptance is cleared and the configured terms must be accepted again.
If a loan application session is interrupted, the caller may resume the same recent application when the caller and applicant details have not changed. After the details are saved, Symba USSD states whether staff matching is still needed or whether a payment request was started. These messages do not mean that the loan was approved or disbursed.
After entering a valid security code, clients may be able to:
The available products, transaction types, payment methods, and limits are defined by the organization's setup.