↗
From your own number
Send SMS through your connected Android phone and keep a familiar point of contact with customers.
YOUR NUMBER. YOUR SIM.
Your work phone.
Now your
SMS gateway.
Send order updates from the number your customers already know. Connect Android to SIM Bridge and manage SMS from your CRM or application.
250 SMS/month · 1 phone · No credit card
SIM BRIDGE / LIVE CONNECTION● Online
09:41 ▰
◈ SIM Bridge
✓
Phone connected
Ready to send through your SIM
YOUR NUMBER. YOUR SIM.
One request from your CRMAPI → Android → SMS
Service illustration
Your phone already sends SMS. Give it an API.
Messages go through your carrier. Customers see your work number and can reply to it.
↙
Replies in your system
Receive incoming SMS and status changes through signed webhooks with delivery retries.
⌘
For your applications
HTTP API, separate access keys and company isolation. Connect your CRM and your own services.
Three steps to your first message.
Create your account
Sign up with Google to get a separate workspace for your phones and messages.
Connect Android
Install the APK, enter a pairing code from your dashboard, and allow SMS and background operation.
Download APK ↓Send a message
Send your first SMS from the dashboard or connect the API to your application.
API documentation ↗Pricing
Start free. Grow at your own pace.
One monthly service price. Your carrier charges for SMS according to your SIM plan.
Free
€0 / month
- 250 SMS/month
- 1 devices
- HTTP API + Webhook
- Incoming SMS
Starter
€7.49 / month
- 1,200 SMS/month
- 2 devices
- HTTP API + Webhook
- Incoming SMS
Pro
€14.99 / month
- 5,000 SMS/month
- 5 devices
- HTTP API + Webhook
- Incoming SMS
Scale
€39.00 / month
- 15,000 SMS/month
- Unlimited devices
- HTTP API + Webhook
- Incoming SMS
The quota counts outgoing messages accepted by the service per calendar month (UTC). Your carrier may bill a long SMS as several segments. Unused quota does not roll over.
Free registration is open. Stripe payments for paid plans are being configured.
SIM BRIDGE
Solutions & use cases
40 practical guides, from order notifications to secure corporate integration.
Orders & delivery
Order status notifications
A customer placed an order but cannot tell whether it is being processed. Routine status calls distract staff, while manually typing the same updates adds work.
Read article ↗
Appointments & services
Appointment reminders
A customer booked ahead and may forget the visit. A reminder should reflect the current booking rather than an old copy of the schedule.
Read article ↗
Integrations
Your first CRM SMS integration
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.
Read article ↗
Reliability
Why a phone disconnects with the screen off
Android and manufacturer settings can restrict background apps. If opening the app restores connectivity, check phone settings as well as the server.
Read article ↗
Integrations
Receiving message statuses by webhook
An API response shows a job was created, not the final result. Your CRM needs a separate stream of status changes.
Read article ↗Reliability
SMS quotas and choosing a plan
An integration can hit its monthly quota during the working day. A limit error should not turn into endless repeated requests.
Read article ↗Before you connect
Does the phone need to stay on?
Yes. Sending requires an Android phone that is on, a SIM and internet access. Allow background operation and adjust battery settings.
Can I connect my CRM?
Yes. Create an API key in the dashboard and use HTTP API to pair phones, send SMS and get statuses.
What if the internet disconnects?
New jobs stay queued. A job already received but not acknowledged by the phone becomes unknown and is not automatically retried.
Where are messages stored?
SMS history and numbers are stored on the SIM Bridge server. API keys are stored as hashes.
Connect your work phone to your system
Start with Free and test one workflow on your Android.