Skip to content

The SMSFabric mobile app

The SMSFabric app turns a phone into part of your SMS setup. What it can do depends on the phone’s operating system.

Android: the phone is a gateway.
iPhone: the app is a companion.
Android iPhone
Role Gateway Companion
Sends SMS for your API and dashboard Yes, from its own SIM cards, without you touching the phone No
Forwards incoming SMS Yes, with the direct build No
Shows your phones and their status Its own status, on the Gateway tab All your phones, on the Overview tab
Sends a message by hand No need: send from the dashboard Yes, through the Messages app, after you tap Send

An Android phone does the real work. An iPhone can’t: iOS doesn’t let apps send SMS without your tap, read incoming SMS or run USSD codes. The iOS companion page explains what the iPhone app does instead.

Once you pair an Android phone with your organization, it:

  • keeps a connection open to SMSFabric, with a small notification that says the gateway is running,
  • sends each message the server hands it, from the SIM card the server picks,
  • reports every message’s status (sending, sent, delivered or failed) back to the server,
  • reports its SIM cards when it starts, and its battery level and signal at every check-in,
  • forwards incoming SMS to your dashboard and webhooks (the direct build only).

The phone sends only what your dashboard or API queues for it. It never decides on its own to send a message.

  1. Your code calls POST /v1/messages, or someone clicks send in the dashboard.
  2. SMSFabric queues the message and picks a phone and a SIM: the one you named, or your default SIM, or the next phone in a pool.
  3. The server pushes the message to that phone over its open connection. The phone accepts it, or declines it if it’s paused.
  4. The phone hands the message to Android, which sends it over the mobile network from the chosen SIM.
  5. Android reports the result. The phone passes sent, then delivered or failed, back to the server.
  6. SMSFabric updates the message and calls your webhooks.

If the phone loses its connection, the server keeps the message queued, or moves it to another online phone in the same pool. If the server can’t be reached when a status comes in, the phone stores the report and uploads it later.