We use optional, privacy-safe analytics to understand which pages help visitors. Nothing optional runs until you choose. Privacy policy

Internal operations

When the dashboard isn't enough, message the human

Monitoring that only writes to a dashboard assumes someone is looking. Internal operations messaging pages the right person, collects an acknowledgement, and records the exchange — from backup failures to approval requests.

Try the interactive demo

The communication problems

Critical alerts discovered on the next dashboard glance
On-call rotations wired through consumer messaging apps
Approvals stuck waiting for someone to open a laptop
No record of who was notified of what, when

Recommended workflows

System alerts

Backups, queues, deploys — severity-routed to on-call.

Acknowledgement loops

Reply ACK closes the alert; no reply escalates.

Approval requests

Reply YES approves routine operations from anywhere.

Daily digests

Morning status summaries to leads who live off-dashboard.

CRITICAL: nightly backup failed on db-2. Reply ACK.Deploy to production requested by CI. Reply YES to approve.Morning digest: 3 warnings, 0 critical, queue healthy.

Architecture

Internal systemsMonitoring, CI, cron jobs
Alert rulesSeverity → recipient → escalation
SendiMessage APIPOST /send-message to staff numbers
Staff memberPage + ACK/YES reply
System actionWebhook closes, escalates, or executes

The API request

send message

curl -sS https://api.sendimessage.com/v1/send-message \
  -H "X-API-Key: $SENDIMESSAGE_KEY" \
  -H "X-API-Secret: $SENDIMESSAGE_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "number": "+15555550123",
    "content": "CRITICAL: nightly backup failed on db-2. Reply ACK.",
    "status_callback": "https://your-endpoint.example.com/status?alert_id=al_2210&severity=critical"
  }'
# → {
#   "status": "QUEUED",
#   "message_handle": "4e828182-a640-483f-bfe9-17ffcaa51d48",
#   "to": "+14155550123",
#   "service": null,
#   "is_outbound": true,
#   "error_message": null,
#   "date_sent": null
# }

Channel behavior and replies

Internal paging standardizes on SMS for predictable delivery to any staff device. iMessage delivery is available on supported messaging lines and destinations. Recipients without iMessage receive SMS when fallback is configured — never assume universal iMessage availability.

The ACK/approval loop runs on receive: your handler matches the alert id, closes or escalates, and the audit trail writes itself.

Line setup, availability, and pricing

One internal line for the engineering/ops org; alert-heavy teams sometimes separate paging from digests.

Line availability varies by country and channel. Run a preliminary availability check, and the team confirms final availability during onboarding review. Check preliminary availability →

Pricing is per active line, billed monthly, with usage per your agreement — confirmed for your countries and volume during managed onboarding. How pricing works →

Frequently asked questions

Why not just use a chat app?

Chat apps work until the person is off that app. SMS reaches any phone, replies are structured data, and the webhook trail gives you an audit record — useful at 3 AM and in postmortems.

Can approvals be safe over SMS?

For routine, low-risk operations with your own staff — yes, with the alert id matched server-side. High-risk approvals should stay in authenticated tooling; the review covers where the line is.

Ready to build this?

Request the setup, or book an integration review and the team will map it to your systems.

Book an Integration Review