AI Voice in the UAE 2026: TDRA, Licensed VoIP, and the New Outbound-Call Rules

The UAE is one of the most regulated voice markets globally: every VoIP service must be licensed by TDRA, calls to PSTN must transit through e& or du, and from 2025-2026 every outbound sales call requires advance TDRA approval, a locally registered number, and an explicit identity disclosure. AI voice agents are subject to the same rules as human agents, with fines up to AED 150,000.

How telephony works there

The Telecommunications and Digital Government Regulatory Authority (TDRA), formerly TRA, administers numbering and licensing under Federal Decree Law No. 3 of 2003 and its 2024-2025 amendments. Geographic numbers use 8-digit local + 1-digit area (02 Abu Dhabi, 04 Dubai, 06 Sharjah, 09 Fujairah). Mobile uses 050/052/054/055/056/058. Toll-free is 800 + 5-6 digits.

Voice services are provided exclusively by licensed operators: Etisalat (e&) and du. International calls to PSTN must transit through one of these two carriers; bypass via consumer VoIP (WhatsApp, FaceTime audio) remains blocked. Twilio operates in the UAE via licensed-partner arrangements; the closest media edge is Bahrain or Frankfurt depending on routing, with RTT to Dubai typically 30-60 ms. CLI rules require a UAE-registered number; foreign CLIs on outbound to UAE consumers are commonly rejected.

Regulatory landscape

Three regimes apply. First, TDRA licensing: any VoIP service in the UAE must be licensed; operating without a licence is an offence. Second, the 2025-2026 outbound-call rules: all outbound sales calls require advance TDRA approval, a locally registered phone number, an explicit introduction of who is calling and why, and confinement to 09:00-18:00. Marketing calls outside that window are prohibited. Third, the UAE Do Not Call Registry: must be scrubbed daily; opt-out must be honoured immediately. Fines for violations run up to AED 150,000 per offence.

PDPL (Federal Decree-Law No. 45 of 2021) covers personal data processing including voice; consent must be informed, specific, and revocable. The TDRA-issued "Guidelines for Telemarketing Calls" (2025) make AI disclosure mandatory at the start of every call to a UAE consumer.

CallSphere implementation

Explore a live demo and compare current plans to find the right fit for your business.

Build and launch steps

flowchart LR
 A[Licensed Twilio AE partner subaccount] --> B[Provision 02/04 DID or 800 TF]
 B --> C[TDRA outbound campaign approval]
 C --> D[UAE DNC daily scrub]
 D --> E[AI + identity disclosure first sentence]
 E --> F[09-18 window + PDPL consent log]

1. Set up a Twilio UAE subaccount via the licensed partner; pin media to Bahrain or Frankfurt edge.
2. Provision a UAE local DID (02 Abu Dhabi, 04 Dubai, etc.) or 800 toll-free for inbound.
3. Submit the outbound campaign for TDRA approval; obtain the local-number registration.
4. Subscribe to the UAE DNC and scrub daily; honour opt-out immediately.
5. Capture PDPL consent: timestamp, IP, purpose, base; store ≥ 5 years.
6. Configure AI + identity disclosure in the first sentence; confine outbound to 09:00-18:00; record with announcement.

FAQ

Is consumer VoIP allowed in the UAE? Consumer VoIP (WhatsApp calls, FaceTime audio) is restricted. Business VoIP requires TDRA licensing through e& or du.

Can I use a US number to call UAE consumers? You can dial, but most UAE carriers reject or down-rank foreign CLIs to consumers. Use a UAE-registered number.

What are the outbound calling hours? 09:00 to 18:00 local time. Calls outside that window are prohibited and fineable up to AED 150,000.

Is AI disclosure mandatory? Yes, under TDRA's 2025 telemarketing guidelines. The agent must disclose AI status and the calling brand at the start of every call.

Sources

• TDRA — Telecommunications and Digital Government Regulatory Authority
• TDRA: FAQs
• Frejun: Sales Calls in UAE — what's changing in 2025
• PDPL — Federal Decree-Law No. 45 of 2021

Explore a live demo and compare current plans to find the right fit for your business.

AI Voice in the UAE 2026: TDRA, Licensed VoIP, and the New Outbound-Call Rules: production view

AI Voice in the UAE 2026: TDRA, Licensed VoIP, and the New Outbound-Call Rules sits on top of a regional VPC and a cold-start problem you only see at 3am. If your voice stack lives in us-east-1 but your customer is calling from a Sydney mobile network, the round-trip time alone wrecks turn-taking. Multi-region routing, GPU residency, and warm pools become the difference between "natural" and "robotic" — and it's all infra, not the model.

Serving stack tradeoffs

The big fork is managed (OpenAI Realtime, ElevenLabs Conversational AI) versus self-hosted on GPUs you operate. Managed wins on cold-start, model freshness, and zero-ops; self-hosted wins on unit economics past a certain conversation volume and on data residency for regulated verticals. CallSphere runs hybrid: Realtime for live calls, self-hosted Whisper + a hosted LLM for async, both routed through a Go gateway that enforces per-tenant rate limits.

Latency budgets are non-negotiable on voice. End-to-end target is sub-800ms ASR-to-first-token and sub-1.4s first-audio-out; anything beyond that and turn-taking feels stilted. GPU residency in the same region as your TURN servers matters more than choosing a slightly bigger model.

Observability is the unglamorous backbone — every conversation produces logs, traces, sentiment scoring, and cost attribution piped to a per-tenant dashboard. HIPAA aligned isolation keeps healthcare traffic separated from salon traffic at the storage layer, not just the API.

FAQ

Is this realistic for a small business, or is it enterprise-only? The IT Helpdesk product is built on ChromaDB for RAG over runbooks, Supabase for auth and storage, and 40+ data models covering tickets, assets, MSP clients, and escalation chains. For a topic like "AI Voice in the UAE 2026: TDRA, Licensed VoIP, and the New Outbound-Call Rules", that means you're not starting from scratch — you're configuring an agent template that's already been hardened across thousands of conversations.

Which integrations have to be in place before launch? Day one is integration mapping (scheduler, CRM, messaging) and prompt tuning against your top 20 real call transcripts. Day two through five is shadow-mode running, where the agent transcribes and recommends but a human still answers, so you can compare side-by-side. Go-live is the moment your eval pass-rate clears your internal bar.

How do we measure whether it's actually working? The honest answer: it scales until your tool catalog gets stale. The agent is only as good as the integrations it can actually call, so the operational discipline is keeping schemas, webhooks, and fallback paths green. The platform handles the rest — observability, retries, multi-region routing — without your team owning the GPU layer.

Talk to us

Explore a live demo and compare current plans to find the right fit for your business.