Skip to content
  • There are no suggestions because the search field is empty.

Understanding The Android Gateway

How it enables SMS in any market, without a carrier contract. 

In most markets, setting up a business SMS service means working through a carrier or aggregator: applying for a number, waiting for approval, signing a contract, and configuring an API connection. In some markets, that process takes days. In others, it takes weeks. In a handful of markets, it's not available at all. The Android Gateway removes that barrier entirely.

Install the Telerivet Gateway app on an Android phone with a local SIM card, and that phone becomes your SMS route. Messages you send from Telerivet go out through the SIM. Messages people send to that number come into Telerivet, where they can trigger automated workflows, update contact records, or route to your team.

You can be running in minutes, not weeks, with nothing more than a phone you likely already have.


What it is

The Android Gateway turns a standard Android phone into a working SMS route. Install the Telerivet Gateway app on an Android phone with a local SIM card, connect it to your Telerivet project, and that phone becomes the bridge between your local mobile network and everything Telerivet can do: two-way conversations, polls, scheduled campaigns, contact data collection, and reporting.

From your contacts' perspective, they're exchanging messages with a local number. From yours, you're running a fully managed messaging programme from Telerivet's web interface with the same capabilities available on any other route type.


When it's the right choice

The Android Gateway fits a specific set of circumstances well.

It's well suited to organizations that need a working route in a market where Telerivet doesn't have a pre-configured aggregator connection. It's also the practical starting point for teams that want to get up and running quickly without committing to a carrier contract, and for any programme where receiving inbound messages is central to how things work -- field data collection, payment confirmations, survey responses, or two-way communication with contacts.

One less obvious fit: organizations receiving SMS from devices rather than people. GPS trackers and fleet management hardware that transmit location data via SMS can send directly to an Android Gateway number, where Telerivet captures and processes the messages like any other inbound SMS. If your operation involves connected devices sending data through SMS, this is worth knowing about.

Volume is the main constraint to plan around. A single Android Gateway is recommended for programmes sending up to around 1,000 messages per day. If your volume is higher, you can connect multiple Android phones to the same Telerivet project, each running its own SIM, to increase capacity. For programmes that consistently exceed this scale, a virtual number or aggregator route will typically be a better fit. The article on choosing your SMS route covers how to make that decision.


What you can send and receive

The Android Gateway supports two-way SMS on any network with cellular coverage. Beyond standard SMS, it also handles:

  • MMS - images, audio, video, and PDF files. Requires Android 5.0 or higher and MMS support from your mobile network.
  • RCS inbound - receive RCS messages with attachments up to 50 MB.
  • Inbound call notifications - receive alerts when a call comes in and trigger automated responses to missed calls.
  • USSD - send USSD commands to your mobile network, for example to check airtime balance.
  • Airtime top-up - on over 450 mobile networks, top up the gateway phone's airtime directly from Telerivet's dashboard. For field deployments where keeping a phone topped up manually isn't practical, this matters.

What you need

Any Android phone running Android 4.4 or higher will work. Note that Android Go devices are not recommended even if they meet the version requirement.

One thing worth knowing before you buy hardware: several phone brands common in emerging markets are not recommended because they may terminate background apps unexpectedly -- Huawei, Tecno, ZTE, Oppo, and Xiaomi fall into this category. Samsung, LG, and Google devices run the app reliably without special configuration. If your budget constrains you to brands on the not-recommended list, the user guide troubleshooting section covers workarounds, but the tradeoff in reliability is real.

The phone doesn't need to be carried around. It works best in a fixed location, plugged into power, with a stable internet connection -- both Wi-Fi and mobile data if possible. The dual connection means it stays online even if one network drops.

You'll also need a local SIM with SMS capability and airtime. For prepaid SIMs, Telerivet can send email alerts if the gateway goes offline or encounters errors, so you can address issues before they affect your programme.


Getting started

  1. Create a Telerivet account at telerivet.com if you don't have one.
  2. Download the Telerivet Gateway app from Google Play or directly from telerivet.com/gateway.
  3. Open the app, log in with your Telerivet credentials, and follow the on-screen steps to connect the phone to your project.
  4. Configure your phone's battery and background app settings following the recommendations in the user guide for your phone model.
  5. Send a test message to confirm the route is working, then begin building your first Service or campaign.

For full setup instructions, recommended phone settings by model, and guidance on increasing your sending rate limit, see the Android Gateway section of the user guide.


Not sure if the Android Gateway is the right route for your setup? Our Solution Engineers can help.