Orders & delivery
Agreeing a new delivery time
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
When a customer cannot receive an order, sending one update is not enough to reschedule. Replies need to reach both your system and the responsible person.
Build the solution
Send a proposed window and invite a reply to the same number. Save the incoming webhook as a CRM case linked to the customer. A staff member or your application’s business logic confirms the final time; the gateway itself does not provide these automatic rules.
Check before launch
A phone number can belong to several orders. Escalate ambiguous replies to staff. Do not treat every incoming word as acceptance of a new slot.
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.
