Android SMS Gateway Scenario 754: NGOs USSD requests in practice

Summary

Android SMS gateway server scenario 754 is NGO USSD for community-health-worker medicine stock-out confirmation before restock 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 box looks empty. The clerk already queued tickets. Until USSD returns the SKU as out, those texts are fiction.

Earlier USSD pieces covered laminated menus, airtime, borders, wallets, KYC, vouchers, school feeding, water trucks, clinic slots, cash float, grain scales, and solar serials. This article stays at the CHW post.

Key takeaways

• Android SMS gateway server scenario 754 is NGO USSD for CHW medicine stock-out 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), or solar serial (694).
• Do not send the restock ticket until USSD confirms the SKU is actually empty. A guessed stock-out 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 CHW SIM. PIN/ticket SMS stays after the stock session, never before.
• Developer Center owns live USSD fields; this page is the post habit.

Related reading

Android SMS gateway server, USSD gateway, transactional SMS, USSD.

CHW context

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

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

Stock then ticket

Queue: empty box → USSD SKU → hold ticket SMS → short ticket after OK → voice if USSD times out.

Write acceptance: staff canary, no ticket before SKU, appeals isolated, spare on the post table.

Restock 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 post SIM. Free 300 lifetime SMS is a lab.

Operations

Mornings: pairing, battery, CHW 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 post phone.

Security and compliance

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

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

Decision guide

Ship android sms gateway server scenario 754 when a ticket-before-SKU is a named escalate. Delay if clerks type stock from memory.

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

Checklist

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

Next steps

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

Deep dive: production hardening

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

Battery exemptions and OEM killers dominate after the first clinic hours.

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

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

Solar-serial radios must not share the CHW pair.

Deep dive: scaling and failure modes

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

Outbreak weeks are queue events. Hold tickets if USSD ages out.

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

District programs may need a phone per post. 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 SKU-to-ticket, not HTTP 200.

A second post device is cheaper than a warehouse mismatch.

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

Document the escalate runbook where the supervisor 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 SKU IDs prevent duplicate tickets. MCP, if used, wraps the same REST — it is not a second SMS network.

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

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

Prefer feature flags. Enable stock USSD for one post 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 clinic traffic.

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