Dual SIM and Multi-Device SMS Routing
A dual SIM SMS gateway turns one phone into two send paths, and a small fleet of phones into a queue that survives a dead battery. This page covers routing strategies, realistic capacity planning, and the failure modes worth designing around.
Bulk queue
Device 26 · Grameenphone
On-net match
Device 26 · Robi
Pinned codes
Device 27 · reserved
Failover only
Device 28 · idle
Five routing strategies that earn their keep
Routing is where a fleet stops being a pile of phones and starts behaving like infrastructure. Most teams combine two or three of these.
- 01
Round robin
Each message goes to the next available SIM in sequence. The simplest way to keep per-SIM volume even. - 02
Weighted split
Give a SIM with a larger operator plan a bigger share of the traffic and a prepaid backup SIM a smaller one. - 03
Operator match
Send to a recipient using a SIM on the same network where on-net rates or delivery are better. - 04
Purpose pinning
Reserve one device for OTP traffic so a long marketing queue can never delay a login code. - 05
Standby failover
A device that sits idle and only receives traffic when a primary device goes offline or hits its limit. - Related
Service pricing
Plans meter devices and SMS send volume. You supply the phone and operator SMS credit.Open →
Sizing your device fleet honestly
Peak hour decides your fleet size, not daily totals. A list of 20,000 that must land inside an hour is a different machine from 20,000 spread across a day.
| Detail | What to expect |
|---|---|
| Messages per SIM per minute | Modest and deliberately pacedHandsets and carriers both dislike bursts. Steady pacing beats a spike that gets throttled. |
| SIMs per phone | One or two, depending on the handsetA dual SIM phone exposes both subscriptions, so one device can hold two send paths. |
| Devices per account | Scales with your plan; pricing follows device count and SMS volume |
| Queue behaviour | A shared queue is distributed across eligible devicesIf one device pauses, its share is picked up by the others rather than stalling the campaign. |
| What raises throughput | More SIMs and more devicesThere is no software switch that makes a single SIM send faster than the carrier allows. |
| What you supply | The phones, the SIMs, and the operator SMS credit on each one |
Work backwards from the deadline. Take your peak-hour message count, divide by what one SIM comfortably sustains in an hour, and round up — then add one device that carries no load. If the number of phones that falls out of that arithmetic looks unreasonable, the honest answer is usually to move the deadline or split the campaign, not to push a SIM harder than the carrier tolerates.
Failover and what actually goes wrong
Device fleets fail in boring, physical ways. Planning for the boring failures is most of the work.
Single device, no plan
- Battery dies overnight and the morning campaign never leaves the queue
- Prepaid credit runs out mid-send with no alert
- Android battery optimisation suspends the app after an OS update
- The phone reconnects to a weak Wi-Fi access point and stops reporting
- One carrier filters your traffic and every message is affected
Two active SIMs plus a standby
- Queued messages redistribute to healthy devices automatically
- Low-credit and last-seen alerts surface the problem before customers notice
- A second operator gives you an independent path when one network filters traffic
- Charging is permanent and the standby is treated as part of the setup, not a spare in a drawer
- Maintenance on one phone becomes routine instead of a scheduled outage
What a dual SIM SMS gateway is
A dual SIM SMS gateway is an SMS gateway running on an Android handset that holds two active subscriptions, each usable as its own send path. Android exposes both subscriptions to apps, so the gateway can address SIM 1 and SIM 2 independently rather than treating the phone as a single channel. Extend that across two or three phones and you have a small fleet: more throughput, more coverage, and somewhere for traffic to go when one path stops working.
This is the part of the Android SMS gateway model that people underestimate. Cloud SMS APIs scale invisibly and charge per message. Here you scale by adding physical send paths, which is cheaper at volume but makes capacity planning your job. The trade is spelled out in the Twilio comparison.
- 01
A dual SIM SMS gateway sends through two operator subscriptions on one handset, which doubles the send path without doubling the hardware.
- 02
Throughput scales with SIM count. No setting makes a single SIM send faster than its carrier permits.
- 03
Pin OTP and transactional traffic to a dedicated device so long marketing queues cannot delay a login code.
- 04
A standby SIM that is charged, online, and funded is what turns a device failure into a delay instead of an outage.
- 05
Replies return to the SIM that sent the message, so conversational traffic should stay on a stable number.
Running a fleet day to day
Five steps that take a single test phone to something you would trust with customer traffic.
- 01
Start with one device and measure
Run your real traffic on a single SIM for a few days. You need an honest baseline of daily volume and peak hour before you buy hardware. - 02
Add a second SIM for the same peak
A dual SIM handset is the cheapest way to double the send path: one phone, one charger, one place to keep it, two subscriptions. - 03
Separate critical from bulk traffic
Pin OTP and transactional alerts to their own device. Marketing queues are long and bursty; login codes are urgent and small. Mixing them is the most common self-inflicted delay. - 04
Add a standby device
The third device does not need to carry load. It needs to be charged, online, and holding credit so that a dead battery or an expired plan is an inconvenience instead of an outage. - 05
Alert on device health, not just on sends
Watch last-seen timestamps, battery level, and signal strength. A phone that stopped reporting an hour ago is a problem even if nothing has failed yet.
Does a dual SIM phone count as one device or two?
One device with two send paths. It occupies a single device slot on your plan while giving you two SIMs and two operator plans to route across.
Can two devices share one campaign?
Yes. A campaign queue is distributed across the devices you allow, so a list finishes in roughly half the time on two SIMs compared with one.
What happens to a queued message if a phone dies mid-campaign?
Messages already handed to the handset stop; anything still queued is redistributed to healthy devices. That is the practical value of a standby SIM.
Do replies come back on the right number?
Replies return to the SIM that sent the original message. If you rely on conversations, pin that traffic to a stable number rather than round-robining it.
Device health is only half the picture — you also want per-message outcomes. Delivery reports tell you whether a specific SIM has started failing, which is often the first sign that credit has run out or a carrier has begun filtering.
Choosing a device from the API
You can address a specific SIM when it matters and let the gateway choose when it does not. Both patterns use the same endpoint in the REST SMS API.
# Split a batch across named devices (deviceIds). Omit to use the primary device.
curl -X POST "https://app.sms-gateway.app/api/v1/messages" \
-H "Authorization: Bearer $SMS_GATEWAY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"to":["+14155552671"],"text":"Your login code is 481920. It expires in 5 minutes.","type":"sms","deviceIds":[3]}'
# Pin OTP: pass a single deviceId, or send with campaign:false (Quick Send).Android's own SubscriptionManager documentation explains how the platform represents multiple SIMs, which is useful background if you are debugging why a handset only exposes one subscription.
Regional notes on SIMs and devices
Procurement, coverage, and filtering behaviour all vary by market.
India
Dual SIM handsets are the norm and on-net rates differ noticeably between operators, which makes operator-match routing worth configuring.
Indonesia
Coverage varies between islands and operators. A second SIM on a different network is as much about reach as it is about throughput.
Pakistan
SIM registration is tied to identity documents, so plan procurement ahead of a launch rather than assuming you can add SIMs in a day.
USA
Carrier filtering reacts to sudden volume changes on a consumer line. Ramp new SIMs gradually and keep message content consistent.
See the regional hub for more markets, or pricing to see how device count maps to plans.
Related features on the same fleet
These run on the same phones, the same account, and the same REST SMS API— no extra product silos.
SMS Contact Management & Lists
Import contacts, build segments, and keep opt-outs clean without a separate CRM.View feature →Scheduled SMS & Campaign Timing
Queue a send for a future date and time, with sensible windows for each recipient.View feature →SMS Auto-Reply & STOP Keywords
Answer common keywords automatically and record opt-outs the moment they land.View feature →Common questions about Dual SIM & multi-device
Straight answers for teams evaluating this feature for production OTP, bulk, or two-way traffic.
Run dual sim & multi-device on your own SIM
Install the Android app, pair a device with operator SMS credit, and test this feature in the panel or over the API. Paid plans are metered by devices and SMS send volume.