Does open-source USSD include free airtime for voucher agents?

No. Sessions consume the prepaid pack on that SIM. We do not sell carrier credit. Platform fees are devices plus SMS volume.

Can a donor blast share the voucher-redemption phone?

No. Fundraising is promotional. It will block agents walking a PIN menu on distribution morning.

Is unused voucher SMS a credit we refund?

No. We do not cash out unused SMS. Refunds cover platform plan fees only, never operator airtime.

Android SMS Gateway Scenario 1882: NGOs USSD requests in practice

Key Takeaways

Cash-voucher USSD is an agent-float problem: empty prepaid means the menu dies, not the “open source” stack.
Keep donor SMS off the redemption handset. Timeouts are the carrier tree.
Do not log voucher PINs. The API only triggers the local Android session.
You bring phones and operator credit. We meter devices plus SMS send volume. Free is 1 / 300 lifetime / 300 contacts.
Developer is 25,000 SMS per year. Paid tiers uncap platform volume; devices still meter 2 / 5 / 15.
Name who tops agent float before a distribution day. Developer Center owns live request shapes.

Summary

Voucher redemption over USSD dies when agent float is empty — not when a GitHub repo is “down.” Scenario 1882 keeps cash-transfer menus on a local Android and a topped-up SIM. Donor SMS stays off that handset. You bring phones and operator credit. Open-source here is process, not free airtime.

When the orange bar empties, USSD is not an outage — the prepaid pack is.

If HQ ships an “open source” playbook and forgets who tops the agent SIM, distribution morning is a spinner.

Voucher-float menu

Layer	Runs on	You fund	Keep off
Voucher PIN menu	Local Android + local SIM	Agent prepaid float	Donor appeals
Trigger API	Control plane	Device + volume plan	Expecting it to be the modem
Safety SMS	Transactional SMS	Operator parts	Voucher PIN in logs
Fundraising	Marketing SMS	Separate SIM + STOP	Redemption handset

Key takeaways

Cash-voucher USSD dies when agent float is empty, not when a repo is “down.”
Keep donor SMS off the redemption handset.
Do not log voucher PINs.
You bring phones and operator credit. We meter devices plus SMS send volume.
Free is 1 / 300 lifetime / 300 contacts. Developer is 25,000 SMS per year.
Name who tops agent float before a distribution day.

Context

Distribution desks blame the repo when the voucher menu dies. The prepaid float on the agent Android is the real ledger.

Radio reality still wins: offline phones and OEM killers break scenarios overnight.

Cross-link hub cornerstones instead of rewriting the product overview.

Keep examples conceptual until Developer Center confirms live request shapes.

Budget airtime for retries — failed loops still cost operator credit.

Core scenario guidance

For android sms gateway open source scenario 1882, map each customer moment to a device pool and fallback path.

Separate configuration mistakes from radio failures during incidents.

Write acceptance criteria before seasonal or clinic-hour traffic.

Prefer gradual rollout with feature flags when automation is involved.

Cost and ownership

Agent float is operator prepaid. Platform volume is a separate bill. Unused voucher texts are not credits we refund.

Failed retries still burn credit during scenario experiments.

Assign who owns SIM top-ups and spare handsets.

Keep marketing spend out of OTP device pools.

Operations

Daily checks: pairing health, battery, queue depth, and DLR anomalies.

After OEM updates or SIM swaps, re-test the scenario path end to end.

Keep a spare charged device ready for failover drills.

Name an on-call owner before unattended sends go live.

Security and compliance

Protect API keys per environment; rotate after contractor access ends.

STOP and consent still apply on promotional scenario lanes.

Avoid logging full OTP bodies into shared chat.

Verify webhook signatures and TLS on every callback path.

Decision guide

Ship android sms gateway open source scenario 1882 when owners, metrics, and fallbacks are written.

Delay if you cannot explain offline-phone behavior during peak hours.

If zero phone ops is mandatory, evaluate CPaaS for that lane.

If local SIM economics matter, harden the Android path and monitor airtime.

Checklist

Scenario moments listed with owners.
OTP vs marketing isolation confirmed.
Spare device funded and paired.
Canary on staff numbers passed.
Developer Center checked if API-shaped.
Webhook/DLR monitoring ready.
Airtime budget includes retries.
On-call owner named.
Rollback path documented.
Hub cornerstone reviewed.

Next steps

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

Deep dive: production hardening

Restaurant reservation SMS still needs STOP on marketing lanes.

SaaS onboarding OTPs should canary on staff numbers before paid scale.

Field-service dispatch needs two-way inbox ownership so techs are not double-booked.

Marketplace seller alerts need multi-device failover when a single phone is the SPOF.

NGO outreach must separate fundraising blasts from operational alerts.

Appointment businesses live on reminder deliverability the morning of the visit.

Bulk CSV import needs validation before radio send; bad rows burn airtime.

Scheduled SMS must survive device sleep and timezone mistakes.

Auto-reply and STOP protect promotional lanes — never auto-reply into OTP threads.

Dual SIM routing fails when slot maps drift after reboot without re-pair.

Multi-device failover only helps if spare phones stay charged and paired.

MMS attachments inherit carrier size and APN limits.

USSD requests are carrier- and region-sensitive; treat timeouts as expected.

Contact lists need consent metadata stored with the number.

OTP priority queues fail when marketing blasts share the same device pool.

Spare charged devices matter more than brochure SLAs when phones send the SMS.

Airtime surprise bills happen when bulk loops ignore radio pace.

OTP and marketing must stay on separate lanes on every scenario.

Never claim unlimited free cloud SMS credits with no device or volume meter.

Name an on-call owner before unattended schedules go live.

Canary on staff numbers before customer OTP.

Battery exemptions and OEM killers dominate overnight reliability.

Cross-link Setup, Pricing, Downloads, and Developer Center with keyword-rich anchors.

If zero phone ops is mandatory, evaluate CPaaS for that lane instead.

Webhook signature verification is non-negotiable for scenario automation.

Document who owns SIM top-ups for multi-site scenario rollouts.

Prefer honest latency expectations over marketing claims about global SLAs on SIM paths.

Scenario playbooks still bill by devices and SMS send volume. You bring the Android phone and operator SMS credit.

Developer Center owns live API parameters. Scenario blogs teach process and failure modes, not endpoint catalogs.

Ecommerce webhooks must verify signatures before they trigger SMS sends.

Clinic reminders need consent records and STOP handling even when messages feel transactional.

Logistics ETAs should degrade gracefully when devices go offline mid-route.

Edtech OTP spikes at exam windows — capacity plan devices before the semester starts.

Fintech OTP is high-stakes: isolate devices, rotate keys, and avoid logging full codes.

Real-estate nurture is promotional; keep it off OTP SIMs and honor quiet hours.