CallScribe in the UAE

Emirati Khaleeji — phonology and English code-switching patterns

Emirati Arabic sits within the Khaleeji dialect cluster but has identifiable national features. MSA ج (jīm) is most often realised as [j] in Emirati speech (so "yawāb" rather than the MSA "jawāb"); MSA ق (qāf) is realised as [ɡ] in Bedouin-rooted Emirati speech and occasionally as [d͡ʒ] in some coastal varieties — a notable point of contrast with Najdi Saudi where qāf is consistently [ɡ]. The kāf affrication ك → [t͡ʃ] in front-vowel environments is characteristic of older and rural Emirati speech but less consistent in younger urban Dubai speakers. Holes' *Dialect, Culture and Society in Eastern Arabia* (Brill, 2004-2018) documents these features in detail across the Eastern Arabian peninsula and remains the canonical academic reference.

The acoustically distinctive feature of Emirati call audio is not the dialect alone — it is the rate and pattern of English code-switching. A Dubai contact-centre agent saying "بنعمل reschedule لك ال-appointment لـ Wednesday" mixes English nouns and verbs into Arabic morphological frames mid-utterance. Generic Arabic ASR systems either drop the English entirely or romanise the Arabic on detection of an English token. CallScribe handles segment-level language identification with a bilingual lexicon shared between the Khaleeji and English models — see the [Khaleeji dialect page](/dialects/khaleeji) for the full code-switching architecture. For mixed Arabic-Hindi-Urdu-Tagalog environments, dialect-ID routes the Arabic segments to the Khaleeji model and other languages to fallback transcription paths.

Three jurisdictions: Federal PDPL, DIFC, ADGM

A UAE controller may be subject to the federal PDPL, the DIFC Data Protection Law, the ADGM Data Protection Regulations, or a combination depending on where they are licensed. The federal Decree-Law 45 of 2021 applies to onshore-mainland processing and to processors handling onshore data; it requires lawful basis for processing, controller registration, data-subject rights (access, rectification, erasure, restriction, portability), breach notification, and DPIAs for high-risk processing. Voice recordings that identify a natural person are personal data within scope.

The DIFC Data Protection Law No. 5 of 2020 is GDPR-aligned and operates inside the Dubai International Financial Centre free zone — it has its own Commissioner of Data Protection and applies independently of the federal PDPL for DIFC-established controllers. The ADGM Data Protection Regulations 2021 (replacing the 2015 regulations) similarly operate inside Abu Dhabi Global Market with an independent Office of Data Protection. CallScribe's default EU processing posture (Hetzner, Helsinki and Falkenstein) maps cleanly onto DIFC and ADGM expectations — both treat EU jurisdictions as adequate for cross-border transfer in most cases — and is acceptable under federal PDPL with appropriate contractual safeguards in our standard Data Processing Addendum.

TDRA call-recording rules and the contact-centre cluster

The Telecommunications and Digital Government Regulatory Authority (TDRA) Telecommunications Consumer Protection Regulations require licensed operators to record customer-care calls relating to service activation, contractual changes, and complaints, with retention of at least one year for general calls and longer for disputed transactions. Beyond the licensed operators themselves, financial-services firms regulated by the Central Bank of the UAE (CBUAE), the DFSA, or the FSRA face longer retention windows — DFSA COB Rule 3.4.6 mandates six years for client-order calls, and similar windows apply under FSRA conduct rules.

The UAE contact-centre footprint clusters in Dubai (Dubai Internet City, DMCC, Business Bay, Dubai South), Abu Dhabi (ADGM-cluster fintech CX, government-services hubs, Masdar), and Sharjah. Sutherland, Concentrix, Teleperformance, and TaskUs all run UAE delivery centres; regional operators include Raya Contact Center, ECCO Outsourcing, Innovations Group, and a long tail of fintech and free-zone CX teams. Many of these centres serve wider MENA and even European markets from a UAE base — the dialect mix on a single Dubai call queue can include Emirati, Saudi, Egyptian, Levantine, and Maghrebi callers. CallScribe's dialect-ID router auto-routes per call. Government-services traffic (Smart Dubai, Abu Dhabi government channels, federal entity hotlines) and fintech compliance traffic make up the highest-value verticals — see [/industries/government](/industries/government) for the public-sector mechanics and [/industries/fintech](/industries/fintech) for the cross-regulator banking detail.

Telephony partners: Etisalat (e&), du, Avaya OneCloud, 3CX

Etisalat (rebranded e& in 2022) is the dominant fixed and mobile operator with a large enterprise contact-centre business: Etisalat Business Cloud Contact Center sits on Genesys and Avaya stacks for the largest UAE enterprises, and e& runs the network and recording integration for many federal and emirate-level government deployments. du (EITC) holds the second-operator slot and serves substantial Dubai and Northern Emirates enterprise traffic with its own contact-centre offer. Avaya OneCloud has a strong UAE presence (Avaya's regional headquarters has historically been in Dubai); 3CX has a wide partner ecosystem in mid-market and Northern-Emirates SMB; Cisco UCCE and Genesys Cloud are common in larger deployments.

CallScribe ingests audio from any of these stacks via SFTP drop, S3 push, or REST API — we are not in the call path and do not modify recording infrastructure. UAE customers feed daily recording dumps from Genesys, Avaya, Cisco UCCE, NICE, or Verint into a CallScribe project; transcripts and analytics appear within minutes per call. The compliance audit-trail and access-log mechanics that DIFC and ADGM regulators expect are documented at [/use-cases/compliance](/use-cases/compliance).

Where data is processed for UAE customers

Standard CallScribe deployment processes audio and transcripts on EU infrastructure (Hetzner Helsinki and Falkenstein). For the majority of UAE customers — DIFC-registered fintechs, ADGM-registered asset managers, mainland-licensed corporates — this posture is acceptable under the applicable data-protection regime with our standard DPA in place. For health-data workloads governed by UAE Federal Law No. 2 of 2019 (which generally requires in-UAE processing), and for federal or emirate-level government deployments procuring in-region processing, we offer an enterprise tier with in-UAE processing via approved cloud partners. Procurement teams typically ask for the architecture document upfront — talk to sales for that.

Where CallScribe sits for a UAE buyer

CallScribe is not a call-recording system — your existing Etisalat, du, Avaya, Cisco, NICE, Verint, or Genesys recording infrastructure keeps recording. CallScribe is the Arabic-first analytics and search layer that turns the recording dump into measurable AHT, FCR, CSAT, QA scoring, and audit-ready transcripts. UAE buyers typically run CallScribe on Arabic traffic (where existing English-trained tools degrade on Khaleeji dialect content) and keep the existing tool for English. Many run both side by side on the same audio source.