Skip to content
Voxa Docs

Telephony (SMS / voice)

Why it’s not shipped yet

Section titled “Why it’s not shipped yet”

South African WhatsApp penetration is high enough that WhatsApp-only has been the right scope for Voxa’s first year. SMS and voice become interesting when:

  • You need to reach contacts who don’t use WhatsApp (older demographics, rural, feature phones).
  • You need OTP delivery outside the WhatsApp ecosystem.
  • You want outbound voice prompts for accessibility.

What we’re evaluating

Section titled “What we’re evaluating”

Provider candidates under consideration:

  • Twilio — largest ecosystem, global reach, per-message pricing.
  • Vonage (Nexmo) — strong SA presence, comparable pricing.
  • MessageBird — good developer experience, EU-headquartered.
  • Local aggregators — lower per-message cost for SA-only sends.

No commitment on any of them yet.

What to expect when it ships

Section titled “What to expect when it ships”

Based on the WhatsApp integration pattern, when telephony lands the shape will be:

  • A channels abstraction (today implicitly single-channel WhatsApp).
  • Per-tenant credential storage for each channel (encrypted).
  • New flow-node behaviour per channel — e.g., an SMS message node is capped at 160 chars, no media, no interactive buttons.
  • Campaigns get a channel field; a single campaign belongs to one channel today.

What to do in the meantime

Section titled “What to do in the meantime”
  • If you have a hard SMS requirement, tell us — hello@voxa.software. Customer demand drives roadmap order.
  • If you can route the SMS step externally and use Voxa for the rest of the flow, do that. Voxa’s webhooks and entry-export are already API surfaces you can integrate against.
Section titled “Related”