Appointments & services
Acknowledging a service request
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
After submitting a form, a customer may not know whether a case was created. A confirmation needs a real case reference.
Build the solution
Save the case in your application first, then create an SMS with its reference and expected contact channel. Use the saved-event key when retrying. SIM Bridge does not decide response times; your team defines them.
Check before launch
Do not promise a fixed response time that your service cannot meet. Test failed case creation and invalid numbers before sending.
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.
