CallScribe in Saudi Arabia

Saudi dialects: Najdi, Hijazi, and East-Province Khaleeji

Saudi Arabia is not a single-dialect country. Najdi — the central-plateau variety associated with Riyadh and the Qassim region — is the prestige dialect of government, broadcast, and most large enterprises headquartered in the capital. Najdi is acoustically distinctive: MSA ج (jīm) is realised as [j] or [d͡z] depending on speaker, MSA ق (qāf) is consistently [ɡ], and the kāf affrication ك → [t͡s] in front-vowel environments shows up especially in older or rural speech. A model trained on MSA newscasts mistranscribes Najdi customer-service calls because the phonemic targets are different.

Hijazi — the dialect of Mecca, Medina, Jeddah, and the Red Sea coast — is closer to urban Levantine in some features (the ج tends toward [d͡ʒ], not [j]) but retains a recognisably Saudi morphology and lexicon. Hijazi traffic dominates pilgrim-services lines (Hajj and Umrah operators), Jeddah-headquartered consumer brands, and large parts of the Western Region BPO footprint. Treating Hijazi audio with a Najdi-tuned model produces the same kind of WER inflation that treating Khaleeji audio with an MSA model does.

The Eastern Province — Dammam, Khobar, Dhahran, Hofuf — sits in a Khaleeji-overlap zone. Saudi Aramco's headquarters is in Dhahran; the population mixes Najdi-origin speakers with East-Saudi locals whose speech shares features (the kāf affrication, certain vowel realisations) with Bahraini and Qatari Khaleeji. CallScribe handles these as Saudi sub-varieties under the Khaleeji umbrella with country and region tagging. For the linguistic background, the Najdi vs Hijazi split is documented at length in Ingham's *Najdi Arabic: Central Arabian* (1994) and Versteegh's *The Arabic Language* (2014); see the [Khaleeji dialect page](/dialects/khaleeji) for the underlying acoustic-modelling approach we use across the Gulf.

NCA PDPL: what the September 2024 enforcement actually requires

The Saudi PDPL applies to any processing of personal data of individuals residing in the Kingdom, regardless of where the controller is located. Voice recordings are personal data when they identify or can identify a natural person — every call-centre recording falls within scope. Controllers must establish a lawful basis for processing (consent is the default; legitimate interest and contractual necessity are recognised but narrowly), maintain records of processing activity, run data-protection impact assessments for high-risk processing (large-scale call recording qualifies), and register with SDAIA where mandated.

The 2023 amendment relaxed the original cross-border-transfer regime: transfers to jurisdictions with adequate protection are permitted; transfers elsewhere require either explicit consent, contractual safeguards approved by SDAIA, or specific exemptions. CallScribe's default EU processing posture (Hetzner, Helsinki and Falkenstein) is a known posture for Saudi controllers — the EU has been treated as adequate under the implementing regulations for most use cases — but for in-scope sensitive workloads (financial-services, health, government) we offer an enterprise tier with in-Kingdom processing via NCA-approved cloud providers. We tell you upfront which posture your use case needs.

CST call-recording rules and SAMA financial-services overlay

The Communications, Space and Technology Commission (CST, the renamed CITC) sets the licensing and consumer-protection rules for telecom and contact-centre operations. Call recording on licensed services requires customer notification at the start of the call ("هذه المكالمة مسجلة لغرض الجودة"), retention windows scaled to interaction type, and prompt retrieval for dispute resolution and regulator inquiry. Operators integrating CallScribe ingest recordings from their existing CST-compliant recording infrastructure — we sit downstream as the analytics and search layer.

SAMA's Banking Consumer Protection Principles and the Insurance Authority's conduct-of-business rules add a financial-services overlay on top: KYC verbal-verification calls, sales calls for investment products, and dispute calls have longer retention requirements (typically five to ten years) and stricter access controls. CallScribe's retention configuration is per-project so a Saudi bank can keep general support calls for one year and KYC-verification calls for ten without manual re-classification. See [/industries/fintech](/industries/fintech) for the cross-regulator banking detail and [/use-cases/compliance](/use-cases/compliance) for the audit-trail and access-log mechanics.

Vision 2030, BPO investment, and the Riyadh / Jeddah hubs

The Vision 2030 National Transformation Program 2.0 (2021 update) targets a major expansion of the Kingdom's BPO and shared-services sector — including PIF-backed investments in dedicated contact-centre districts and tax incentives for foreign BPO operators establishing Riyadh and Jeddah operations. Sutherland, Concentrix, Teleperformance, and TaskUs have established or expanded KSA delivery centres in the last five years; regional operators like Innovations Group, Raya Contact Center, and ECCO Outsourcing have added Riyadh capacity. Public-sector reporting puts the Saudi contact-centre footprint above 100,000 seats and growing — the largest in the GCC and the natural home for Arabic-first call analytics.

Verticals matter. Banking (Al Rajhi, SNB, Riyad Bank, Alinma), telecom (stc, Mobily, Zain KSA), retail (Almarai, Panda, Jarir), government services (Absher, Tawakkalna, Tafqeet), and Hajj-and-Umrah operations all generate distinct dialect mixes, vocabulary needs, and compliance overlays. CallScribe ships sector-aware vocabulary packs and uses dialect tagging at the project level so a Riyadh-headquartered bank with a Jeddah branch is not forced to a single dialect setting. The contact-centre operations layer — AHT, FCR, CSAT, QA scoring — is documented at [/industries/call-center](/industries/call-center); the GCC BPO buyer perspective is at [/industries/bpo](/industries/bpo).

Telephony partners: stc, Mobily, Zain KSA, and Genesys deployments

stc Group is the dominant fixed and mobile operator and runs stc Cloud Contact Center (the rebranded enterprise contact-centre platform formerly under stc Solutions and Specialized) — many of the largest Saudi enterprises sit on stc-managed Genesys Cloud or Genesys Engage deployments with stc as the network and recording integrator. Mobily (Etihad Etisalat) has a large Eastern Province enterprise footprint and runs Avaya and Cisco-anchored contact-centre stacks. Zain KSA serves the third-operator slot with its own enterprise contact-centre offer and 3CX partner ecosystem.

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 require modification of the recording infrastructure. Most KSA customers feed the daily recording dump from Genesys, Avaya, Cisco UCCE, or NICE into a CallScribe project; transcripts and analytics appear within minutes per call. For banks running on-premise NICE or Verint deployments, the integration is the same — only the source path changes.

Where CallScribe sits for a KSA buyer

CallScribe is not a call-recording system — your existing stc, Mobily, NICE, Verint, or Genesys recording infrastructure keeps recording. CallScribe is not a SAMA-licensed entity either; we are an analytics and audit layer that supports SAMA-aligned controls (encryption, audit logs, retention rules, access controls) and integrates with the regulated firm's existing compliance posture. Saudi BPO customers run CallScribe as the Arabic-first analytics layer over an existing English-trained tool, or as the primary speech-analytics platform when Arabic is the dominant call language.