Orders & delivery
Updating customers when a courier is delayed
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
Dispatch knows about a delay while the customer still expects the old time. The update should contain confirmed information rather than an unsupported prediction.
Build the solution
After the dispatcher’s decision, the CRM creates a delay event. Include the revised window, a brief reason when appropriate and a contact number. Store the notification version so repeated requests do not announce the same change several times.
Check before launch
Check whether the old message is still queued and cancel it where possible before sending the update. Do not promise an exact time without a reliable estimate.
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.
