Android SMS Gateway Scenario 934: NGOs USSD requests in practice

Summary

Android SMS gateway API scenario 934 is NGO USSD for birth-registration confirmation before certificate pickup ticket 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 clerk already queued tickets. Until USSD returns filed, those texts are a second birth record.

Earlier USSD pieces covered laminated menus, airtime, borders, wallets, KYC, vouchers, school feeding, water trucks, clinic slots, cash float, grain scales, solar serials, CHW stock, ration voids, and catch-logs. This article stays at the civil desk.

Key takeaways

• Android SMS gateway API scenario 934 is NGO USSD for birth-registration hold — not laminated menus (34), airtime (94), border (154), wallet (214), KYC (274), voucher (334), school-feeding (394), water trucks (454), clinic slots (514), cash float (574), weighbridge (634), solar serial (694), CHW stock (754), ration void (814), or catch-log (874).
• Do not send the certificate pickup ticket until USSD confirms the record is filed. A guessed file is a duplicate birth.
• 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 registry SIM. Ticket SMS stays after the file session, never before.
• Developer Center owns live USSD fields; this page is the civil-desk habit.

Related reading

Android SMS gateway API, USSD gateway, transactional SMS, USSD.

Registry context

Desks still mix USSD and SMS because the civil vendor has no HTTPS. The last hop is a labeled clerk Android. That is not a CodeCanyon modem pack.

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

Register then ticket

Queue: birth reported → USSD file → hold ticket SMS → short ticket after OK → voice if USSD times out.

Write acceptance: staff canary, no ticket before file, appeals isolated, spare on the desk.

Birth 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 ticket 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 registry SIM. Free 300 lifetime SMS is a lab.

Operations

Mornings: pairing, battery, clerk canary, USSD dry-run, ticket 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 desk phone.

Security and compliance

Protect API keys. No national IDs or baby names in the ticket body. STOP applies to appeals.

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

Decision guide

Ship android sms gateway api scenario 934 when a ticket-before-file is a named escalate. Delay if clerks type registry numbers from memory.

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

Checklist

• USSD before ticket.
• Staff canary.
• Appeals off registry SIM.
• No names or IDs in SMS.
• Developer Center checked.
• Airtime for USSD + SMS.
• OEM sleep disabled.
• Desk on-call named.

Next steps

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

Deep dive: production hardening

File USSD is a desk ritual. If the phone lives in a drawer, morning windows are theatre.

Battery exemptions and OEM killers dominate after the first queue.

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 desks go live.

Canary on staff numbers before pickup tickets. 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.

Ration-void radios must not share the registry pair.

Deep dive: scaling and failure modes

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

Outreach days are queue events. Hold tickets if USSD ages out.

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

Districts may need a phone per window. Still devices + volume.

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

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

Measure file-to-ticket, not HTTP 200.

A second desk device is cheaper than a duplicate record.

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

Document the escalate runbook where the registrar 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 registry worker, never in a public kiosk widget. Idempotent birth IDs prevent duplicate tickets. MCP, if used, wraps the same REST — it is not a second SMS network.

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

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

Prefer feature flags. Enable file USSD for one window 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 ticket SMS from appeal drips. Verify USSD callbacks before window traffic.

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