Aeion Notifications + Twilio SMS
SMS sounds simple ("just send a text") until you encounter GSM-7 vs UCS-2 encoding, segment billing, A2P 10DLC registration, short-code provisioning, STOP keyword compliance, per-country regulations, and two-way reply parsing. Aeion wraps the Twilio Messaging API (SMS / MMS / WhatsApp, RCS via Vonage) across two layers: Notifications sends simple one-way transactional SMS, while Aeion Connect handles A2P 10DLC compliance, opt-out enforcement, and two-way conversation handoff.
What Twilio SMS Integration Provides
`
A2P 10DLC Setup Walkthrough (US)
`
Two-Way Conversation Handoff
```typescript
Compliance Tracking
`
FAQ
Yes. Per-country availability per Twilio. Per-country pricing. Per-country compliance (India DLT, EU per-country).
Yes via Twilio WhatsApp API. Per-template Meta approval. Per-message 24h conversation window.
Yes via Twilio. Per-Android device. Per-fallback to SMS if not supported.
Yes. Per-message image attachment. Per-message $0.02-0.05.
Yes for high-volume tenants. Per-tenant short-code dedicated. 6-12 week approval timeline.
Yes for transactional. Per-toll-free verified status. Faster A2P approval than 10DLC.
Per-message segment count is read back from the provider's response and logged. There's no built-in cost dashboard or per-day/per-month cost rollup today — check your provider's own billing console for spend.
Aeion doesn't run its own GSM-7/UCS-2 detection — segment count comes from the provider's response. Curly quotes, em-dashes, and emojis can still silently push a message into Unicode segments on the provider's side; that's provider behavior, not something Aeion warns about today.
Automatic for conversations that flow through Aeion Connect's compliance engine. Per-recipient suppression, confirmation reply, and audit trail.
Aeion Connect's messaging service supports automatic failover to a backup provider (Twilio, Plivo, Vonage, or Telnyx) when enabled. The simpler Notifications-channel SMS sender picks whichever provider has credentials configured (Twilio checked first) but does not fail over mid-send if that provider's API call fails.