Appointments & services
Confirming an appointment from a customer reply
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
Staff need to know whether the customer accepted a proposed time. Sending an SMS is not itself appointment confirmation.
Build the solution
Ask for a short agreed reply and route it to the CRM through a webhook. Implement reply matching and final booking changes in your application. Retain the reply and event for staff review.
Check before launch
Handle typos, multiple bookings and replies from another number. Do not update a booking automatically when the answer is ambiguous; provide manual review.
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.
