Skip to main content
Twilio is Vortex IQ’s programmable comms layer for SMS, WhatsApp, and voice, used when an alert has to reach a human who is away from their laptop, or when an ecommerce event has to trigger a customer-facing message in real time.

​
What is Twilio?

Twilio is the API-first communications platform for SMS, voice, WhatsApp, and email (via its SendGrid acquisition). It is the dominant developer platform for transactional messaging, used by everyone from Uber to Airbnb to retail brands sending order confirmations and shipping pings. Twilio is not a UI you log into for daily ops. It is a programmable network you compose into your own workflows. That composability is exactly what Vortex IQ needs from a notification layer that has to reach phones, not just channels.

​
Why Vortex IQ uses Twilio as an alert channel

Two things drive Vortex IQ’s use of Twilio. First, internal paging that survives a laptop being closed. When a sev1 revenue-at-risk incident fires at 02:00 local, a Slack post is not enough. SMS or a voice call from Twilio reaches the on-call commercial owner, the head of operations, or the founder, depending on the escalation policy. It is a complement to PagerDuty, not a replacement, useful for non-engineering stakeholders who do not live inside the on-call tooling. Second, customer-facing notification flows. Vortex IQ detects ecommerce events (a delayed shipment, a back-in-stock SKU, a high-value cart abandonment) and can trigger Twilio-driven SMS or WhatsApp flows that talk to the end customer, not just internal staff. That blurs the line between an alert channel and a marketing surface, which is exactly what programmable comms is for.

​
What gets delivered

Vortex IQ pushes the following alert types through Twilio:
  • Sev1 incident pages via SMS to nominated commercial stakeholders.
  • Voice calls for sev1 events when SMS is not acknowledged within N minutes.
  • WhatsApp messages for ops teams in regions where WhatsApp is the primary mobile channel.
  • Customer-facing transactional flows triggered by ecommerce events: shipment delay alerts, back-in-stock notifications, abandoned high-AOV cart nudges, fraud-hold notices.
  • Verification flows (one-time passcodes) for sensitive operator actions inside Vortex IQ.
Each message uses Twilio Messaging Services for sender pool management, with brand-registered numbers where regulation requires it.

​
How it integrates

  • Auth model: Twilio Account SID and Auth Token (or API Key/Secret pair) stored encrypted, scoped to a dedicated Vortex IQ Messaging Service per customer where possible.
  • Formatting: Plain SMS for paging (concise, severity-prefixed, with a tracking link). Approved WhatsApp templates for customer-facing flows. TwiML for voice calls, including text-to-speech runbook playback.
  • Routing: Per-recipient policy with quiet hours, rate caps, and per-region sender selection. Voice escalation only fires for sev1 and only after SMS goes unacknowledged.
  • Delivery semantics: At-least-once submission, status callback ingestion (queued, sent, delivered, failed), retry on transient Twilio errors with exponential backoff, and short-code/long-code fallback per region.
  • Acknowledgement: Inbound SMS replies (ACK, RESOLVE, SNOOZE) parsed by a Vortex IQ webhook to update incident state. Voice calls capture DTMF input as acknowledgement.

​
Operational diagnostics

Twilio is treated as a regulated, cost-bearing channel. Tracked KPIs:
  • Message delivery rate by region and channel (SMS, WhatsApp, voice) over 24h and 7d.
  • Median time to delivered status.
  • Inbound acknowledgement rate per recipient.
  • Per-message cost trend and budget consumption against the customer’s Twilio account.
  • Carrier filtering rate and blocked-number incidents.
  • Sender reputation health on Messaging Services.
If Twilio delivery degrades or the customer’s account hits a hard limit, Vortex IQ falls back to the configured backup channel and raises a connector pulse so ops leadership sees the gap before the next page.

​
Get started

Connect Twilio from Settings, Sources, paste your Account SID and Auth Token, pick a Messaging Service for outbound traffic, and define escalation recipients. Open Vortex IQ or ask Ask Viq to map a paging and customer-flow policy for your brand.