Voice covers spoken one-time passcodes, IVR menus, programmable outbound calls, text-to-speech and AI voice agents. Unlike the messaging channels, voice is provisioned with our account team: there are no public voice endpoints in the REST API, and your configuration is built around your numbers, countries and call flows.
What you can build#
| Capability | What it does | Typical use |
|---|---|---|
| Voice OTP | Reads a one-time passcode aloud in a phone call. | Users on landlines, users who did not receive the SMS, accessibility. |
| Flash call | Verifies a number with a short missed call. | Low-friction phone number verification. |
| SMS-to-voice fallback | Places a voice call with the code when an SMS is not delivered. | Raising OTP completion rates in hard-to-reach markets. |
| IVR | Multilingual phone menus that route and serve callers. | Routing callers, self-service, after-hours lines. |
| Outbound calls | Programmable calls with recorded or synthesised messages. | Appointment reminders, delivery notices, payment reminders. |
| Text-to-speech | Converts text to natural speech, including Arabic. | Dynamic messages such as amounts, dates and codes. |
| AI voice agents | Conversational agents, including in Arabic, that answer and place calls and hand over to a human. | Front-line support, bookings, qualification calls. |
| Contact centre | Inbound queues, predictive, progressive, power and preview dialers, answering-machine detection, recording and transcription, voicemail drop. | Sales and collections teams, customer care. |
| Bring your own carrier | Connect your existing SIP trunks. | Keep current carrier contracts and numbers. |
Resellers can offer voice under their own brand with the same white-label, multi-tenant setup as the messaging channels.
How provisioning works#
Voice depends on caller IDs, number ranges and local telecom rules, so it is configured with you rather than through a self-serve API:
- Scope. Tell us the use case (OTP, reminders, IVR, agents), destination countries, expected call volumes and languages.
- Numbers and caller ID. We agree caller IDs and number ranges for each country, within local rules.
- Call flows. Our engineers build your IVR menus, prompts, text-to-speech voices or AI agent behaviour with you.
- Integration. We agree how your systems trigger calls and receive call outcomes, for example through events to your webhook.
- Testing. Calls go to your own verified numbers before any production traffic.
- Go live. Production routes are switched on once compliance checks are complete.
Combining voice with messaging#
Voice works best as part of a channel plan, not in isolation:
- OTP: send the code by SMS or a WhatsApp authentication template first, then fall back to a voice call if delivery fails. See SMS and WhatsApp.
- Reminders: send a WhatsApp or SMS reminder, and call only the customers who did not confirm.
- Support: let an AI voice agent resolve routine calls and pass the conversation to a human agent with context.
What to prepare#
- Use cases and sample scripts, in each language you need.
- Destination countries and expected daily and peak call volumes.
- The caller ID you want to present, and any numbers you already own.
- Where call outcomes should go in your systems.
- For SIP trunks you bring: your carrier and trunk details.
Request voice access#
Request access and mention voice, or ask the engineer working on your messaging integration. We scope voice together with your other channels so the fallbacks and reporting fit together.
Next steps#
- Quickstart: start with messaging while voice is provisioned.
- SMS API: the usual first channel for OTP, with voice as fallback.
- Webhooks: how status events reach your systems.
Ready to send your first message?
Request test credentials. An engineer sets up your account, and test sends go to your own verified numbers.
Request test access