Orders & delivery
Order dispatched notifications
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 dispatch update should follow a real handover to the courier. Printing a shipping label does not prove that goods left the warehouse.
Build the solution
Use a confirmed handover event from your warehouse system. Send the order reference and a tracking link on your verified domain, if one exists. Select deviceId by business or warehouse and use the handover event for idempotency.
Check before launch
Do not invent a tracking reference. Test partial shipments and repeated handovers. Route incoming replies to a responsible employee rather than leaving them unnoticed on the phone.
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.
