Reliability
Replacing a phone without breaking routing
Implementation scenario · This is an example implementation, not a story about a named customer. Results depend on your integration, phone, network and carrier.
AI-generated scenario illustrationThe problem
A new phone gets a different deviceId. If the CRM keeps the old mapping, jobs will not reach the intended device.
Build the solution
Pair the new Android and test it with your own number. Update the business-to-deviceId mapping in your backend, then disconnect the old device. Keep message history with original IDs rather than rewriting it for the new phone.
Check before launch
Review the old queue before disconnecting. Do not copy a phone token to another device. Check all workers that use the routing map.
How SIM Bridge works
Your backend creates a job through the API, and the connected Android sends SMS through your SIM. Store the message ID in your system and receive status changes through a webhook. A queued job is not yet a sent message: the phone must be available and the carrier must accept it.
Start with your own test number. Check Android permissions, screen-off connectivity, retries with the same Idempotency-Key, and unknown-status handling. Keep API keys out of browser code and public repositories.