What is an SMS and voice call alert API router?
It is a ready-made service that sits between your software and an SMS and voice gateway. Your software sends one HTTP request; the router checks it, sends the SMS, places the phone call, re-dials if nobody answers, retries a failed SMS, skips duplicates and logs what happened. You do not have to build any of that into your software.
Is this a developer API platform, an auto-dialler or a bulk-SMS panel?
No. It is an alert and notification router for one organisation’s own systems: ERP and accounting software, monitoring, CCTV and access control, logistics, fleet and facilities. It is not an auto-dialler, not a marketing bulk-SMS panel and not a pay-per-message developer platform. It is a hosted service: we run it for you, so there is nothing for you to install.
How does my software send an alert?
With one HTTP POST to the router’s /api/send address, carrying five form fields: user, pass, phone, message and an optional delivery_mode (SMS & Call, SMS only or Call only). Anything that can make an HTTP request can do it: a script, an ERP, a monitoring tool. The reply is plain text that says what was scheduled for each number. The code samples above show curl, PHP and Python.
Which SMS and voice providers does it work with, and whose account is it?
The accounts are yours. You bring your own SMS account and your own voice-call account with your provider, and the router uses them to send. It connects to the API of your SMS service provider and of your voice-call service provider. We provide the software: it receives your system’s request and routes it to the SMS service and the call service. The provider is chosen when your copy of the service is set up, so you are not tied to one vendor. If your provider’s API is not connected yet, we add it during set-up, and we quote that work first.
What does the phone call say?
The call plays a pre-recorded voice message. You put a tag from {A} to {Z} in the message, and the tag chooses which recorded message is played. The tag is removed from the SMS, so your customer reads clean text. The call does not read your SMS aloud. Messages without a tag are not sent.
What happens if nobody answers the call?
The router checks the gateway’s call report every five minutes and dials again if the call was not answered, until someone picks up or the retry window you set is over. A pickup counts only if it lasts a minimum number of seconds. If you send several numbers in one request, they are dialled in order, and the first pickup stops the rotation.
What happens if the SMS fails?
When the gateway rejects an SMS, the router sends it again later. By default it makes up to three attempts at least an hour apart, and both numbers can be changed. It cannot fix a rejection that is permanent, for example a number that does not exist.
How does it stop the same alert flooding a phone?
The same message to the same number inside a time window (180 minutes by default) is skipped, and each skipped repeat is recorded on the first alert’s log entry. Timestamps inside the message are ignored when comparing. A repeat whose text also carries a changing value can slip past, which is exactly what the Insights screen reports as a duplicate leak.
How do I see what was sent and what is wasting credit?
The admin portal has a Logs screen with every alert and the status of its SMS and calls, and a Calls report. The Insights screen analyses your own logs and ranks the sources causing avoidable messages and calls, with a diagnosis for each and a savings simulator. An email watchdog warns your admins when usage looks abnormal.
Can I test it without sending real messages?
Yes. Sandbox mode is a single setting: the router accepts your requests and logs them as usual, but no SMS is sent and no call is placed. Switch it off when you are ready to go live.
How is access protected?
Portal users can turn on two-factor login with an authenticator app, and each user sees only the screens their role allows. Logins and sends are rate limited, sessions expire, and connections to the gateway are checked against its certificate. Backups are encrypted before they leave the server. Each of your systems can have its own API key, with an optional list of allowed IP addresses and its own send limit, so one system can be switched off without touching the others.
Where does it run, and who looks after it?
It runs on our servers as a hosted service, and we look after it. You get a web address for your software to call and portal logins for your team. Each customer has a separate database. You do not receive the source code. The SMS and voice-call accounts with your providers are yours, and they bill you for them directly.
Can it route to APIs other than SMS and voice?
Not out of the box. SMS and voice calls are what it does today. Routing one request to other systems, such as a CRM, an ERP, WhatsApp, email or a ticketing tool, is a custom project built to order by our development team and quoted for your case. See the custom routing section above.
How much does it cost?
It is a subscription service, and the price depends on your alert volume and on whether you want custom integration work, so we quote for each organisation. Send us a message on WhatsApp or request a quote and we will come back with a clear proposal.
