Android SMS Gateway Scenario 382: NGOs USSD requests in practice

Featured illustration for Android SMS Gateway Scenario 382: NGOs USSD requests in practice

Android SMS Gateway Scenario 382: NGOs USSD requests in practice. Scenario-based article #382 combining vertical and feature contexts under hub D. Must stay unique via specific workflow and failure case. Priced by devices and SMS send volume; BYO phone and operator credit.

Written by the SMS Gateway team for operators who run phones and airtime themselves — not for theoretical cloud SMS demos.

InformationAndroid SMS GatewayScenarioHub D
Article
Published
January 30, 2025
Updated
February 6, 2025
Reading time
16 minute read

Key Takeaways

  • Scenario 382 is ORS sachet claim on *770# then a receipt SMS — not bednet *750#, borehole *730#, cook-oil *690#, or seed *360#.
  • A hung *770# tree is not an API 502. Retrying it like HTTP will empty the prepaid SIM before the first sachet is issued.
  • Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 300 SMS lifetime, 1 device. Developer is 25,000 SMS per year.
  • Starter is 2 devices; the clinic spare still counts.
  • Hold donor-appeal CSV until ORS receipts drain.
  • Canary *770# at 05:25, not at last night’s HQ health check.

Summary

Scenario 382 is ORS sachet intake: a caregiver dials *770#, then a receipt SMS returns the claim id. Donor CSV waits until trees complete. 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.

If the cage is open and the receipt never landed, you did not issue a sachet. You burned prepaid on a hung menu.

Not a CodeCanyon “NGO USSD” pack. Device meters apply — Twilio vs Android SMS gateway.

Key takeaways

  • Scenario 382 is ORS sachet claim on *770# then a receipt SMS — not bednet *750#, borehole *730#, cook-oil *690#, or seed *360#.
  • A hung *770# tree is not an API 502. Retrying it like HTTP will empty the prepaid SIM before the first sachet is issued.
  • Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 300 SMS lifetime, 1 device. Developer is 25,000 SMS per year.
  • Starter is 2 devices; the clinic spare still counts.
  • Hold donor-appeal CSV until ORS receipts drain.
  • Canary *770# at 05:25, not at last night’s HQ health check.

USSD balance and menu automation, how an Android SMS gateway works, device setup, WHO diarrhoeal disease.

Context

First issue is 05:45. Enumerators open the cage at 05:35. Fundraising still wants a donor CSV.

Free (300 SMS lifetime) is a rehearsal clinic. Developer is 25,000 SMS per year.

Core scenario guidance

05:45 is *770# ORS, not bednet *750# or chlorine *730#. Timezone is the clinic, not HQ.

ORS USSD roles

RoleWhenTypical fail
*770# ORS claimClinic local, before first issuePhone in a locked sachet cage after 05:00
Receipt SMSOnly after a completed treeSent on a hung session
Staff OTPTransactional, own poolDumped onto the clinic radio
Donor appealHeld until last receipt DLRReleased at 05:05 into ops SMS

Cost and ownership

Priced by devices and SMS send volume. You use your own phone and operator SMS credit. The clinic spare is a billed device. Hung trees still burn prepaid.

Name a 04:45–08:45 on-call for issue windows, not only weekday HQ.

Operations

05:25 canary. Abort: hold donor CSV, keep staff OTP, skip a second “all households” blast. Do not loop *770# like HTTP.

Security and compliance

Claim ids only. No names in SMS. Authenticate MIS hooks. Donor lists are promotional.

Decision guide

Ship when 05:25 canary completes a tree and receipts DLR. Delay if the phone sleeps in the sachet cage. If handsets are forbidden, CPaaS for staff OTP.

Checklist

  • Clinic SIM paired before 04:45.
  • 05:25 *770# canary.
  • Receipt DLR watched.
  • Staff OTP isolated.
  • Donor CSV held.
  • Prepaid before 04:45.
  • Battery exemptions.
  • Clinic locale.
  • Issue-window on-call named.
  • Device cap includes spare.

Next steps

Review device and SMS volume pricing, device setup, SMS API documentation.

Deep dive: production hardening

Night charging that never happens is an outage at 05:45. Treat USSD timeouts as expected.

Deep dive: scaling and failure modes

Multi-clinic mornings add devices before inventing a hidden unlimited-handset SKU. Raise OEM ceilings; fair-use remains.

Deep dive: integration discipline

Idempotency on claim_id + kind (ussd|receipt). Incomplete tree does not write a sachet. Live fields in Developer Center.

Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

05:25 *770# drill

Canary. Complete one tree. Confirm receipt DLR. Hold donor CSV during the wave.

Jump to the live product docs for this topic—not another long-form article.

FAQ

Frequently asked questions

Direct answers about android sms gateway app scenario 382.

Does USSD include extra airtime?

No. 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. Menu hops and receipt SMS both spend operator credit.

Should *770# share the fundraising radio?

No. A 05:05 donor CSV will starve ORS receipts. Pin ops deviceIds.

Is Developer unmetered for a 30-household morning?

No. Developer is 25,000 SMS per year. Free is 300 lifetime and 300 contacts.
Keep learning

Topically related guides—chosen by subject overlap, not a fixed sitewide footer.

Information
android sms gateway ussd

Android SMS Gateway USSD requests: Api usage

Android SMS Gateway ussd requests — api usage. Feature deep dive on USSD requests (api usage). Unique examples and failure modes; link matching /features path when exists. Priced by devices and SMS send volume; BYO phone and operator credit.

Apr 10, 202516 min
Read article
Information
android sms gateway app how to avoid spammy wording

Android App: How to avoid spammy wording

Android App: How to avoid spammy wording. Actionable guide on how to avoid spammy wording in context of android sms gateway app. Include prerequisites, steps, limits, and internal links. Priced by devices and SMS send volume; BYO phone and operator credit.

Aug 5, 202516 min
Read article
Information
android sms gateway app how to choose prepaid vs postpaid sims

Android App: How to choose prepaid vs postpaid SIMs

Android App: How to choose prepaid vs postpaid SIMs. Actionable guide on how to choose prepaid vs postpaid SIMs in context of android sms gateway app. Include prerequisites, steps, limits, and internal links. Priced by devices and SMS send volume; BYO phone and operator credit.

May 17, 202616 min
Read article
Information
android sms gateway app how to design otp templates

Android App: How to design OTP templates

Android App: How to design OTP templates. Actionable guide on how to design OTP templates in context of android sms gateway app. Include prerequisites, steps, limits, and internal links. Priced by devices and SMS send volume; BYO phone and operator credit.

Dec 31, 202516 min
Read article

Browse the full Android SMS gateway knowledge base or return to how an Android SMS gateway works.

Get started

Test the gateway on your own Android phone

Install the app, pair one device, and validate your API flow before choosing a paid plan.

You supply the phone, SIM, and operator SMS credit.