Integrations
Your first CRM SMS integration
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 CRM knows the order and customer, but a phone needs a separate secure job channel. Do not expose the API key to the user’s browser.
Build the solution
Create a company key and keep it in your CRM backend secrets. Select deviceId server-side and call /v1/sms/send with phoneNumber and message. Store the response and message ID alongside the order event.
Check before launch
Start with one test device. Check logs for key exposure, handle API errors and retry with the same Idempotency-Key.
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.
