From a monitoring alert to a ringing phone
Five steps, and the anti-spam check that keeps the platform from being used to reach someone who hasn't agreed to be called.
1. Create an account and verify your phone
Sign up and confirm a phone number by SMS or voice OTP. That number becomes your account's default verified destination, and your account is topped up with a small free credit to test with.
2. Verify every destination you'll dial or text
Add and verify any other on-call numbers from the console before they can be used. This is deliberate: an integration's API key can never add or verify a destination on its own, so a leaked key is still limited to numbers you've personally confirmed.
3. Connect your monitoring system
Issue an API key from the console, then point your monitoring tool at the dial or SMS webhook with that key in a header. Use the ready-made Zabbix plugin, or a generic webhook for anything else.
4. Alerts go out automatically
When your monitoring system fires, it calls the webhook with a destination and message. Call Alert checks the number is verified and the destination country is enabled, then places the call or sends the SMS and bills your balance.
5. Track everything in the dashboard
See balance over time, call vs SMS volume, and spend by destination, plus a full log of every call and SMS with delivery status.
Supported integrations
| Zabbix | Native media type plugin - import a YAML template, add your API token as a secret macro, and assign it to on-call users. |
| Prometheus Alertmanager | Point a webhook_configs receiver at the dial or SMS endpoint with your API key. |
| PagerDuty / Opsgenie | Use their generic webhook / custom action integration to call the same endpoint. |
| Anything else | If it can send an HTTP POST with a JSON body and a header, it can trigger Call Alert. |