Android SMS Gateway Scenario 694: NGOs USSD requests in practice

Summary

Android SMS gateway scenario 694 is NGO USSD for solar-kit serial activation before beneficiary PIN SMS. Service pricing is based on device count and total SMS sent through the gateway. You need a working Android phone with a SIM and SMS credit from your mobile operator. Operator message costs are yours—we do not sell carrier SMS balance.

The kit is on the table. The clerk already queued PINs. Until USSD returns the serial live, those texts are fiction.

Earlier USSD pieces covered laminated menus, airtime gates, border SIMs, wallets, KYC, vouchers, school feeding, water trucks, partner-clinic slots, cash-agent float, and grain scales. This article stays at the village kiosk.

Key takeaways

• Android SMS gateway scenario 694 is NGO USSD for solar-kit serial activation — not laminated menus (34), airtime gates (94), border dual-SIM (154), wallet-before-receipt (214), KYC hold (274), voucher-then-PIN (334), school-feeding (394), drought water trucks (454), partner-clinic slots (514), cash-agent float (574), or grain weighbridge (634).
• Do not send the beneficiary PIN until USSD confirms the kit serial is live. A guessed serial is a warehouse lie.
• Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
• Free is 300 SMS lifetime, 300 contacts, 1 device. Developer is 25,000 SMS per year.
• Appeals never share the kiosk SIM. PIN SMS stays after the serial, never before.
• Developer Center owns live USSD fields; this page is the village-kiosk habit.

Related reading

complete practitioner guide, USSD gateway, OTP isolation, USSD.

Kiosk context

Field teams still mix USSD and SMS because the kit vendor has no HTTPS. The last hop is a labeled tech Android. That is not a CodeCanyon modem pack.

Cross-link hub cornerstones. Confirm USSD request shapes in Developer Center.

Serial then PIN

Queue: kit at kiosk → USSD serial → hold PIN SMS → short PIN after OK → voice if USSD times out.

Write acceptance: staff canary, no PIN before serial, appeals isolated, spare on the kiosk table.

Activation lanes

Cost and ownership

Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Developer is 25,000 SMS per year. USSD retries and PIN SMS still cost operator credit. Starter, Professional, and Business list Unlimited SMS as platform send volume; that is not unmetered carrier SMS.

Assign who tops the kiosk SIM. Free 300 lifetime SMS is a lab.

Operations

Mornings: pairing, battery, tech canary, USSD dry-run, PIN queue gated, voice if session dies.

After OEM updates, re-canary a staff USSD session you can watch.

Name an on-call who can reach the kiosk phone.

Security and compliance

Protect API keys. No national IDs in the PIN body. STOP applies to appeals.

Never auto-reply into PIN SMS. Verify webhook signatures.

Decision guide

Ship android sms gateway scenario 694 when a PIN-before-serial is a named escalate. Delay if techs type serials from memory.

If zero phone ops is mandatory, evaluate CPaaS plus a kit API — if one exists.

Checklist

• USSD before PIN.
• Staff canary.
• Appeals off kiosk SIM.
• No ID numbers in SMS.
• Developer Center checked.
• Airtime for USSD + SMS.
• OEM sleep disabled.
• Kiosk on-call named.

Next steps

Return to practitioner guide, compare device and SMS volume pricing, open device setup guide, and confirm APIs in SMS API documentation.

Deep dive: production hardening

Serial USSD is a table ritual. If the phone lives in a drawer, morning kits are theatre.

Battery exemptions and OEM killers dominate after the first convoy.

Spare charged devices beat brochure SLAs. Airtime surprise bills happen when retry loops ignore radio pace.

Never claim unlimited free cloud SMS credits with no device or volume meter. Name an on-call owner before unattended kiosks go live.

Canary on staff numbers before beneficiary PINs. Cross-link Setup, Pricing, Developer Center.

Document who owns SIM top-ups. Webhook signature verification is non-negotiable.

Prefer honest latency over global SLA claims. If zero phone ops is mandatory, evaluate CPaaS.

OTP/PIN and marketing must stay on separate lanes. Contact lists need consent metadata.

Dual-SIM routing fails when slot maps drift after reboot. Multi-device failover only helps if spare phones stay charged and paired.

Weighbridge radios must not share the kiosk pair.

Deep dive: scaling and failure modes

Scale sites by docked phones, not by implying unmetered carrier SMS after a flat fee.

Distribution days are queue events. Hold PINs if USSD ages out.

Retry storms burn credit. Cap USSD sessions in the worker.

Multi-village programs may need a phone per kiosk. Still devices + volume.

Do not load-test against beneficiary lists. Use staff cohorts.

Raise OEM/Android SMS rate ceilings carefully. Carrier fair-use still applies.

Measure serial-to-PIN, not HTTP 200.

A second kiosk device is cheaper than a warehouse mismatch.

Watch prepaid during two-way CONFIRM. Inbound is another surface.

Document the escalate runbook where the field lead can find it. If only a contractor knows the pairing PIN, you do not have USSD.

Deep dive: integration discipline

Hold the Bearer in the logistics worker, never in a public kiosk widget. Idempotent kit IDs prevent duplicate PINs. MCP, if used, wraps the same REST — it is not a second SMS network.

Store gateway session IDs on the kit row. Staff should not grep the phone.

Confirm live parameters in Developer Center. Sample JSON is not the contract.

Prefer feature flags. Enable serial USSD for one village first.

Keep examples conceptual until Developer Center confirms live request shapes. Budget airtime for retries.

Radio reality still wins. Cross-link hub cornerstones instead of rewriting the product overview.

Isolate PIN SMS from appeal drips. Verify USSD callbacks before convoy traffic.

Scenario success needs owners for phones, SIMs, templates, and on-call. That is android sms gateway scenario 694.