I'm designing a utility app where a user presses a button and nearby users within roughly 1 kilometer, who have the same app installed, receive an urgent pop-up. The initiating phone has cellular coverage, but the account has no mobile-data plan, no Wi-Fi connection, and no SMS or calling credit. The user must not be charged.
The alert cannot be relayed through Bluetooth, Wi-Fi Direct, mesh networking, or any other phone-to-phone radio connection. Instead, the phone would need to contact a central cloud service, which would identify the nearby users and send them notifications.
I'm wondering whether a carrier-supported reverse-charged SMS, toll-free short code, USSD service, or similar arrangement could allow the network to accept a message from a zero-balance account while the service provider pays the carrier. Are there any carrier-level or international infrastructure options that could make this possible, or is this restricted to emergency-service systems?
4 Answers
If external hardware is allowed, a low-power radio such as LoRa can provide an off-grid link to a phone and potentially cover a kilometer or more depending on terrain, antennas, and local regulations. Devices based on LoRa or similar systems can communicate directly or through relays without cellular data.
That does violate the requirement that the stock smartphone hardware be used alone, though. Under the phone-only constraint, the realistic choices are to allow some connectivity, arrange carrier-sponsored access, or redesign the system around dedicated radio hardware.
For an ordinary Android or iPhone app, there is no software trick that can create connectivity. The app can only use services the operating system and carrier make available. If outbound SMS and mobile data are blocked because the account has no active service or credit, paying for the incoming message on your backend usually does not change that—the carrier normally rejects the originating message before it leaves the phone.
A reverse-charged number could work only if the carrier explicitly supports that product and permits this type of originating traffic. That would require agreements with each relevant carrier and country, and it would likely be expensive and tightly controlled. It is not something an app can enable by itself.
Some banking and payment services receive special carrier treatment, but those are negotiated zero-rated services. They are exceptions implemented in the carrier’s billing and routing systems, not a general loophole available to any application.
Emergency calling and some emergency messaging are different because laws and carrier policies require networks to carry them even without credit, sometimes without a normal subscription. Government emergency broadcasts are also sent from the carrier infrastructure to devices in an area.
A private app cannot reuse those channels for general alerts. To obtain comparable treatment, you would need formal carrier partnerships and possibly regulatory approval in every market. Otherwise, the requirement set is contradictory: a message must leave the phone, but every available path for doing so has been disabled.
A collect call or a free short code might appear promising, but those services still depend on the carrier authorizing the originating subscriber and billing arrangement. The service provider paying for termination does not automatically make an account with barred outbound service eligible.
You could investigate a carrier-managed zero-rated service, USSD access, or a special machine-to-machine plan, but those are commercial integrations rather than universal technical workarounds. They would need to be negotiated and tested separately with every network you support, and unrestricted alerting would also raise obvious spam and abuse concerns.
Exactly—the physical transmission medium cannot be eliminated. If it is not cellular data, SMS, Wi-Fi, Bluetooth, or another radio path, there is nothing available to carry the request to the server.