Africa's Talking expects callback responses to begin with CON for continuing menus or END for final screens. This builder validates that shape before you copy code.
Prepare a gateway handoff before shortcode submission.
USSD providers usually need a public callback URL, a response contract, sample payloads and evidence that every menu path terminates cleanly. The launch brief tab turns the current local flow into a handoff note for engineering, QA or aggregator review.
- Use the simulator to test happy paths, invalid input, back navigation and final END responses.
- Keep request examples synthetic. Do not put PINs, national IDs, payment secrets or real phone numbers in shared JSON.
- Export the flow JSON and launch brief together so callback developers can replay the same screen map.
USSD Flow Builder FAQ
How should I use this builder?
Create menu, input and END screens, simulate phone input, review lint warnings, then export JSON, starter handlers, callback payloads and the launch brief.
What should I verify before submission?
Check CON/END responses, prompt length, dead links, END screens, callback payload fields, session persistence, HTTPS hosting, data minimization and current provider rules.
Does this provision a live USSD code?
No. It is a local design and starter-code tool. Your aggregator or telco still controls shortcode provisioning, billing, certification and production launch.
Validate menu behavior before telco submission
Build screens, simulate a phone session, lint CON/END behavior, watch character limits, and export callback starter code.
No telco, aggregator, or live USSD code is provisioned.
What to check
- Methodology: store screens/options locally, render simulator state, lint menu links and length, then generate Node, PHP, JSON, and test payload outputs.
- Test every path, invalid input, timeout, back/cancel behavior, language variant, and telco character limit before submission.
- Export JSON and code only after reviewing callback security, session persistence, logging, and data-minimization rules.
Limitations
- Disclaimer: design and code starter only, not telco approval, aggregator certification, production hosting, or payment compliance.
- Gateway callback formats, session timeouts, shortcode rules, and billing terms differ by market and provider.
- Do not put PINs, national IDs, phone numbers, or payment secrets into shared examples.
Source/reference note: verify against current aggregator docs, telco submission rules, data-protection requirements, and production callback tests before launch.