Saltar al contenido
Operaciones 7 de noviembre de 2026 10 lectura de minutos

Formatos de números móviles del CCG para listas del discador

Clean GCC call lists before you dial: E.164 formats for UAE, Saudi, Kuwait, Qatar, Bahrain and Oman mobiles, leading zeros, lengths and Arabic-Indic digits.

D
7 de noviembre de 2026

Respuesta rápida

Store GCC mobiles in E.164: plus sign, country code, then the national number with no leading zero. Per ITU-published regulator notices, UAE (+971) and Saudi Arabia (+966) mobiles have 9 digits after the country code. Kuwait (+965), Qatar (+974), Bahrain (+973) and Oman (+968) mobiles have 8. Convert Arabic-Indic digits to 0 to 9 first, keep the column as text, and validate on length rather than a fixed prefix list.

A call list is only as good as its phone column. A missing digit, a leftover trunk zero or a number written in Arabic-Indic digits all produce the same result on the floor: a failed attempt, a wrong-number disposition or a carrier error that nobody traces back to the spreadsheet. When the list covers six Gulf states with different lengths and leading digits, the errors multiply.

This guide is a cleaning reference for GCC dialer lists. It uses the numbering-plan communications that regulators file with the ITU, notes the date of each so you know how fresh it is, and sets out a checklist to run before import. It does not replace the regulator's current plan, which you should consult for ranges newer than the notices cited here. For calling rules rather than number formats, see our Guía de cumplimiento para llamadas salientes del GCC.

Why bad formats waste attempts

Every dial attempt on a malformed number costs something: carrier minutes on an attempt that fails fast, an agent's time if it connects to the wrong party, and clean data in your reporting. They also feed the failure-code noise that makes real problems harder to see. Our guide to SIP error codes on outbound calls explains why malformed destinations often appear as generic failures. Cleaning at import is cheaper than diagnosing after the campaign, and it improves the contact-rate numbers you report. See Cómo mejorar las tasas de contacto saliente for the other levers.

E.164 in one paragraph

E.164 is the international format for telephone numbers. In practice, a number stored for dialing is: a plus sign, the country code, and the national significant number, with no spaces, hyphens, brackets or leading zeros. Example (illustrative format, not a real subscriber): +971 then nine digits becomes +971XXXXXXXXX. If a source writes the number in a national style with a leading 0, that 0 is not part of the national significant number. The Saudi notice shows this clearly: its ranges are written nationally as 0575XXXXXX, ten characters, while the table states a national significant number length of 9.

Country by country

The table lists only what the ITU-published notices state. "Date" is the communication date. Where a country has several notices, the most recent is listed first. These notices list the ranges allocated at the time, so a number that does not match may still be valid under a later allocation.

PaísCodeMobile leading digits in the noticeDigits after codeNotice date
Emiratos Árabes Unidos+97150, 52, 55, 5699 June 2009
Arabia Saudita+96651 and 57 series (e.g. 0510, 0575 nationally)926 July 2026; 6 Dec 2021
Kuwait+96541, 5, 6, 9830 Aug 2021 (restated 20 Sep 2022)
Catar+9743, 5, 6, 7827 Mar 2023
Bahréin+973Mobile blocks beginning 32 to 39, plus some "universal (mobile)" blocks beginning 64 and 66814 Dec 2023
Omán+96871, 72 and 74 to 79; 90 to 99814 Sep 2025

Notes per country

  • UAE. The notice is from 2009, so it predates later allocations. The operator names in it (Etisalat for 50 and 56, du for 52 and 55) record who each range was allocated to at the time. Treat it as the baseline for the 9-digit length and check the current TDRA plan for newer mobile ranges. Landline area codes in the same notice (2, 3, 4, 6, 7 and 9) have 8-digit significant numbers, so mixing landlines into a mobile list shows up as a length mismatch.
  • Arabia Saudita. The 2026 notice allocates further mobile ranges, including 57 series blocks for operators and virtual operators. The notice describes them as non-geographic mobile numbers of 9 digits.
  • Kuwait. The notice lists 8-digit mobile numbers starting 41, 5, 6 and 9, and fixed telephony starting 2. Its overall minimum number length is 3 digits because short codes are listed too.
  • Katar. The overall maximum in the notice is 10 digits, because some non-geographic ranges (for example M2M and IoT) are longer. Mobile ranges are 8 digits. This is a reason to validate by number type, not by a single country length.
  • Bahréin. The notice lists mobile ranges as numbered blocks of different sizes, such as 32000000 to 32099999 and 39000000 to 39999999, all 8 digits. It also lists some "universal numbers (mobile)" blocks that begin 64 and 66, so a valid mobile number does not always start with 3.
  • Omán. The 2025 notice lists operator ranges, all 8 digits. The 7 series in it covers 71, 72 and 74 to 79; 73 is not listed. It also lists a 12-digit IoT range beginning 4, which belongs in neither a mobile nor a landline list.

Beyond the GCC: Egypt, Jordan and Morocco

Many GCC contact centres also call Egypt, Jordan and Morocco, so here is what the ITU pages state for each.

  • Egypt (+20). The 10 September 2017 NTRA communication lists mobile series 10, 11, 12 and 15 with a 10-digit national significant number.
  • Jordan (+962). The TRC communications give the international dialing format for mobiles as +962 7 XXXX XXXX, which is 9 digits after the country code.
  • Morocco (+212). The ANRT communication of 13 July 2026 introduces two new mobile NDCs, 730 and 731, with a 9-digit national significant number. Earlier ranges in the same document, such as 754 and 786, also begin with 7 and have 9 digits.

The Morocco and Saudi notices, both from July 2026, show how quickly the picture moves. Use these figures as a validation baseline, not as a permanent list.

Common list errors

SíntomaCausa probableFix
Digits after code is one too manyLeading national 0 kept after the country codeStrip a single leading 0 before adding the code
Number starts with two zerosAn international call prefix stored in place of the plus signReplace the leading 00 with +, once
Country code appears twiceCode added to a number that already had itCheck whether the number already starts with the code and has the right length
Short numbers on a Gulf listSpreadsheet dropped a leading zero or converted to a numberFormat the column as text before paste or export
Landlines in a mobile campaignMixed source listsCheck length and leading digits; split fixed lines into their own list
Digits show as boxes or fail to parseArabic-Indic digits from the source CRMConvert to 0-9 (see below)

Be careful with the "strip the zero" rule. Only strip a zero when the source is clearly a national-format number from the country you expect. Do not blindly remove zeros from numbers that came with a country code already.

Arabic-Indic and Extended Arabic-Indic digits

CRM exports and web forms in Arabic often store digits as Arabic-Indic characters, not ASCII 0 to 9. They look right on screen and fail every validation rule. The Unicode Arabic chart defines two sets:

SetCode pointsLooks like
Arabic-Indic digitsU+0660 to U+0669٠١٢٣٤٥٦٧٨٩
Extended Arabic-Indic digitsU+06F0 to U+06F9۰۱۲۳۴۵۶۷۸۹

Each character has a decimal value 0 to 9, so you can convert with the language's built-in Unicode digit lookup instead of a hand-written table. In Python, for example:

import unicodedata

def to_ascii_digits(text):
    out = []
    for ch in text:
        value = unicodedata.decimal(ch, None)
        out.append(str(value) if value is not None else ch)
    return "".join(out)

Run this before stripping spaces, before length checks and before any duplicate check, otherwise the same person appears twice in different digit styles. Punctuation is not converted by a digit lookup, so strip all non-digit characters after conversion. Also watch for right-to-left control characters pasted into the field, which are invisible but break matching. See Compatibilidad con árabe y RTL for how the interface handles mixed text.

Validate on length, not on a hard-coded prefix list

Regulators allocate new ranges regularly, as the 2026 Saudi and Moroccan notices show. A validator built on a fixed list of prefixes rejects good numbers the day a new block is released. A more durable order of checks is:

  1. Normalise digits and strip everything except digits and a leading plus.
  2. Resolve the country code, from the number or from the record's country field.
  3. Check the length of the national significant number against that country's expected mobile length.
  4. Use a prefix list only to tag likely mobile versus fixed, and treat a miss as a warning to review, not a reject.
  5. Keep a list of numbers that failed, with the reason, instead of silently dropping them.

Cleaning checklist before import

  • Keep the original file; work on a copy.
  • Set the phone column to text before editing.
  • Convert Arabic-Indic and Extended Arabic-Indic digits.
  • Remove spaces, hyphens, brackets and invisible direction marks.
  • Replace a leading 00 with a plus sign; strip a single national 0 for known national-format sources.
  • Add the country code where it is missing, using the record's country field.
  • Check length by country; flag landline-length numbers in a mobile list.
  • Remove duplicates after normalising, not before.
  • Scrub against your do-not-call list and consent records.
  • Spot-check 20 random rows by hand before upload.

Cómo encaja DialerBee

These are the parts of DialerBee that bear on list quality, as its feature pages describe them.

  • List import. Import accepts CSV and XLSX and shows a preview of how columns mapped before anything is written, with a do-not-call scrub on import. See gestión de clientes potenciales.
  • Phone format check. Numbers are checked against the expected format before they are dialled, so a malformed row is caught rather than dialled. This is a safety net, so still clean the list first. Plan to convert digit styles in your own cleaning step before upload.
  • CRM data. If your numbers come from a CRM, see the Guía de configuración de la integración CRM.
  • Caller ID. Caller ID pools with several selection modes are covered in how to configure caller ID groups and local presence. A number that rings back is also a number that needs a clean DID.
  • Calling hours per jurisdiction. Windows are set per jurisdiction, so a clean country code also decides which window applies. See the controles de cumplimiento.

DialerBee provides compliance-supporting controls. Number formats are one input to them, and the regulator's current plan remains the authority.

Preguntas frecuentes

What is the mobile number format for the UAE in E.164?

The UAE country code is +971. In the 2009 TRA numbering plan notice published by the ITU, mobile numbers use national destination codes 50, 52, 55 and 56 with a 9-digit national significant number. So a mobile number is +971, then 9 digits, with no leading zero. That notice is from 2009, so newer mobile ranges are not in it and need checking against the current TDRA plan.

How many digits is a Saudi mobile number?

Saudi Arabia is +966. The regulator communications published by the ITU (CST, 26 July 2026, and CITC, 6 December 2021) list mobile ranges with a national significant number of exactly 9 digits, for example the 57 and 51 series, written nationally with a leading 0 such as 0575XXXXXX. In E.164 you drop that 0, giving +966 followed by 9 digits.

Do Kuwait, Qatar, Bahrain and Oman all use 8-digit numbers?

For mobiles, yes, according to the ITU-published notices: Kuwait (+965, 2021 notice), Qatar (+974, 2023), Bahrain (+973, 2023) and Oman (+968, 2025) all list 8-digit national significant numbers for mobile ranges. Their leading digits differ, which is why length is a safer validation than a hard-coded prefix list.

Why do spreadsheets break phone numbers?

Spreadsheet programs often treat a column of digits as numbers. Microsoft's own support page says Excel automatically removes leading zeros and converts large numbers to scientific notation. Format the phone column as text before pasting or exporting, and keep the original file untouched so you can compare the cleaned list against it.

How do I convert Arabic-Indic digits in a phone number?

Arabic-Indic digits sit at Unicode code points U+0660 to U+0669 and Extended Arabic-Indic digits, used with Persian and Urdu, at U+06F0 to U+06F9. Each has a decimal value from 0 to 9, so a script can map them to ASCII digits 0 to 9 before any validation. The Unicode Arabic chart lists both ranges.

Should I validate numbers with a list of known prefixes?

Use a prefix list only as a secondary signal. Regulators allocate new ranges: the CST notice for Saudi Arabia is dated 26 July 2026 and the Moroccan ANRT notice 13 July 2026. A fixed list goes stale, whereas a country code plus length check keeps working until a country changes its plan.

Fuentes

  1. ITU, National Numbering Plan of the United Arab Emirates, communications of 9.VI.2009 and 11.VI.2012. itu.int, UAE numbering plan (consultado el 7 de noviembre de 2026)
  2. ITU, National Numbering Plan of Saudi Arabia, communications of 26.VII.2026 and 6.XII.2021. itu.int, Saudi Arabia numbering plan (consultado el 7 de noviembre de 2026)
  3. ITU, National Numbering Plan of Kuwait, communications of 30.VIII.2021 and 20.IX.2022. itu.int, Kuwait numbering plan (consultado el 7 de noviembre de 2026)
  4. ITU, National Numbering Plan of Qatar, communication of 27.III.2023. itu.int, Qatar numbering plan (consultado el 7 de noviembre de 2026)
  5. ITU, National Numbering Plan of Bahrain, communication of 14.XII.2023. itu.int, Bahrain numbering plan (consultado el 7 de noviembre de 2026)
  6. ITU, National Numbering Plan of Oman, communication of 14.IX.2025. itu.int, Oman numbering plan (consultado el 7 de noviembre de 2026)
  7. ITU, National Numbering Plan of Egypt, communication of 10.IX.2017. itu.int, Egypt numbering plan (consultado el 7 de noviembre de 2026)
  8. ITU, National Numbering Plan of Jordan, communications of 13.IX.2017 and 23.VI.2020. itu.int, Jordan numbering plan (consultado el 7 de noviembre de 2026)
  9. ITU, National Numbering Plan of Morocco, communication of 13.VII.2026. itu.int, Morocco numbering plan (consultado el 7 de noviembre de 2026)
  10. Microsoft Support, Keeping leading zeros and large numbers. support.microsoft.com, leading zeros (consultado el 7 de noviembre de 2026)
  11. Unicode Consortium, Arabic code chart (U+0600 to U+06FF). unicode.org, Arabic chart (consultado el 7 de noviembre de 2026)

Lecturas relacionadas

Note: Numbering plans change. This article reflects the ITU-published communications named in the Sources list, checked on November 7, 2026. Confirm current ranges with each national regulator before you rely on them. DialerBee does not provide legal advice or guarantee regulatory compliance.

¿Listo para ver DialerBee en acción?

Solicite una demostración en vivo de 15 minutos o comience una prueba gratuita de 14 días: sin presentaciones, sin compromiso. Las llamadas empiezan en cuanto su propia troncal SIP o PBX está conectada y aprobada.

Prueba gratuita de 14 días · crédito de IA gratuito · sin tarjeta · 11 idiomas · BYOC · controles que apoyan el cumplimiento

Ver el sitio completo en inglés →