Appointments & services
Appointment reminders
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 customer booked ahead and may forget the visit. A reminder should reflect the current booking rather than an old copy of the schedule.
Build the solution
Your CRM scheduler checks the booking before sending and creates an SMS with date, time and contact details. Rescheduling or cancellation removes unsent jobs. Keep a separate event identifier for each booking version.
Check before launch
Exclude diagnoses or other sensitive details. Check local time zones and late cancellations. The scheduler runs in your application, not in the gateway.
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.
