Install the app on a transmitter phone — every incoming SMS lands in the right chat, inbox or webhook. Server alerts, team OTPs, customer messages — no VPN, no code.
Five common scenarios our customers ship
Monitoring SMS land on a personal number and get lost in other texts.
An old Android sits next to the server — every hosting SMS lands in the DevOps chat instantly.
Couriers get order messages on personal numbers; the dispatcher sees nothing.
SMS from the courier SIM go to a shared Telegram channel. No SMS gateways, no code.
The verification code lands on the corporate number — but the phone is with someone on vacation.
SMS from the work SIM hit a private team chat. First one in enters the code.
One person holds the business card, but accounting and the CFO need to see every transaction.
Bank SMS are mirrored to the accounting inbox and the finance Slack channel. Originals stay on the phone.
An employee runs two SIMs — work and personal — and important messages get lost in the noise.
Only work-SIM SMS are forwarded. Personal ones stay on the phone — no one else sees them.
Not a feature list — what you actually get
Open the admin panel, scan the QR in the Android app. No tokens, configs, or SSH.
Each SIM forwards to its own channel. Nobody on the team sees personal messages from the second SIM.
Filter by sender, keywords, SIM card, and time of day. Bank SMS → finance chat. Google OTP → team chat.
One SMS goes to Telegram, Email and webhook simultaneously. Handy for redundancy and on-call.
HTTPS through Cloudflare. No open router ports, static IPs, or ngrok tunnels.
A foreground service starts on Android boot. Phone rebooted — forwarding picks back up on its own.
Three steps from signup to first forwarded message
Create an account with Google or email, scan the QR code in our Android app. Done — the device is paired.
Add a Telegram bot, X2Chat, Email or Webhook. The test button validates the setup instantly.
Create a rule (e.g. "bank SMS → Telegram channel"). You can test it against a real SMS.
Cancel any plan in one click. No hidden fees.
Start with 30-day Pro trial, no card
30-day Pro trial free on signup
For teams of 3+
Honest comparison. Where competitors win, we say so.
| Free APKs SMS2Tg, Forward SMS |
Roll-your-own (Twilio + n8n) | SMS Sender 24 | |
|---|---|---|---|
| Setup | 15–30 min per channel | 2–8 hours of code | 2 minutes, scan a QR |
| Multi-device | 1 phone | whatever you build | up to 5 (Pro) / 20 (Business) |
| Flexible rules | basic filters | whatever you build | sender, keywords, SIM, time |
| Channels | usually Telegram only | anything, if you write it | Telegram, Email, Webhook, Slack, Discord, X2Chat |
| Logs and history | none | if you set it up | 7–365 days + search |
| Support | GitHub issues | Stack Overflow | email + Telegram, under 24h |
| Price | €0 | $25+ Twilio + hosting + your time | €0–€29 |
Don't see your question? Email [email protected]
Your SMS are visible only to you in your private admin panel and to the channels you've configured. Accounts are isolated — other users and our staff don't have access to the contents.
Yes. The app detects which SIM the message came from. You set separate rules — for example, work SMS to Slack, personal SMS nowhere.
Yes — Wi-Fi or mobile data is needed to send SMS to the server. If the connection drops, messages queue and ship as soon as the internet returns.
Yes. In a rule, specify the sender (Chase, Wells Fargo) or keywords (code, OTP). Other SMS are not forwarded and stay only on the phone.
Twilio and similar handle outgoing SMS — you send to customers. SMS Sender 24 handles incoming SMS: it takes messages arriving on your phone and routes them to chats and systems. Opposite jobs.
While the phone is off, SMS arrive on the SIM but aren't forwarded. On boot the app starts automatically. Anything missed while offline stays only in the phone's memory.
Yes — the Business plan is built for teams: up to 20 phones and multiple admins per account. A good fit for agencies, courier services, shared OTP accounts and finance teams.