Reliability
Understanding an unknown SMS status
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
The phone may receive a job but fail to acknowledge the result in time. You cannot confidently say it was sent or not sent.
Build the solution
Show unknown as a separate state. Before resending, staff check phone and order history. The service does not automatically resend these jobs, to avoid duplicates when an acknowledgement was lost.
Check before launch
Do not relabel unknown as failed for reporting convenience. Test late results in your CRM and document the manual resend decision.
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.
