Appointments & services
Rescheduling without conflicting 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
An old reminder may remain queued after the date changes, giving the customer two conflicting messages.
Build the solution
Store the booking version and notification ID in your backend. On rescheduling, cancel the waiting SMS and create a new confirmation. Clearly state that this is a replacement date, not an additional appointment.
Check before launch
Treat already sent messages as history that cannot be recalled. Test rapid successive changes and delayed carrier reports.
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.
