← All engines · Delivery
Twilio SMS adapter
preview
v1.0.0 · last updated 2026-06-06 · source: cybercli.delivery.channels.twilio
§1
What it does
SMS + WhatsApp via Twilio with 160-char digest summary fallback — the channel for installs where the operator's phone needs to ring even when WiFi is down.
§2
Why you care
SMS is the channel that works when nothing else does. WiFi down, mobile data limited, the operator on a flight with only cellular — SMS still gets through. For a regulated SOC where the on-call rotation must be reachable end-to-end, SMS is non-optional.
WhatsApp delivery via Twilio is the same adapter with a different `from`. For installs where the operator's primary channel is WhatsApp (common outside North America), the adapter handles both with one configuration shape.
§3
How it works
The adapter pulls the Twilio account SID + auth token + sender number from the CredentialVault and POSTs to Twilio's REST API. SMS bodies are auto-truncated to 160 chars; the truncated body links back to the engine dashboard via a short URL the operator clicks for the full alert.
WhatsApp variant uses Twilio's WhatsApp-prefixed numbers; the adapter detects the destination's `whatsapp:` prefix and routes correctly. Both variants honor Twilio's per-account rate limits and surface 429s as retry-after to the dispatcher.
§4
Configure & observe
CLI
$ cybercli channels test <destination_id>Send a test SMS / WhatsApp message; verify the operator receives it.
Dashboard surfaces
Configure account SID, auth token (vaulted), sender number, and per-recipient destination numbers.
Audit row shape
notification_sentnotification_failed parameters.channel: twilio + parameters.twilio_sid (the message SID returned by Twilio) + parameters.variant (sms / whatsapp) + parameters.truncated: true|false.
§5
Status
Preview — the adapter is implemented but per-region SMS deliverability + Twilio's WhatsApp-business onboarding (which requires operator-side WhatsApp Business API approval) make 'just works' onboarding harder than the other adapters. Operators willing to do the Twilio + WhatsApp setup get a working channel; the engine doesn't yet hold their hand through the third-party onboarding.
How this engine talks to the rest