Every promotional SMS sent in the UAE must carry a specific prefix before the sender name or the message will not be delivered. The prefix is "AD-" and it has been mandatory since November 3, 2020, under TDRA regulation. A sender ID registered as "ACMELOGISTIC" cannot be used for promotional messages. It must be registered and submitted as "AD-ACMELOGISTIC." A sender ID without the "AD-" prefix will not be approved for promotional use, and promotional messages sent without it are likely to fail or be blocked at the carrier level. Most teams building UAE programs for the first time discover this requirement at sender ID registration, not during planning.
Business SMS in the UAE is governed by the Telecommunications and Digital Government Regulatory Authority (TDRA) under a framework that requires sender ID registration with both major operators, separate treatment of promotional and transactional traffic, and explicit documented consent under the UAE Personal Data Protection Law. All promotional sender IDs must carry the "AD-" prefix. International organizations face a registration timeline of up to 25 business days. Penalties for non-compliance can reach 400,000 AED, approximately $109,000 USD, per violation, making the UAE one of the highest-stakes compliance environments in the markets covered in this series.
The UAE's telecoms environment is a two-operator duopoly. e& (formerly Etisalat) and du (Emirates Integrated Telecommunications Company) are the only licensed operators. Every sender ID registration must be completed separately with both carriers, through e&'s CMS portal and du's ESP portal respectively. A sender ID approved only on e&'s network will not deliver correctly to du subscribers, and vice versa.
The AD- prefix requirement applies to all promotional sender IDs regardless of the organization's size, sector, or local versus international status. Transactional sender IDs, used for OTPs, account alerts, appointment confirmations, and other service messages arising from a user-initiated action or an existing service relationship, do not require the AD- prefix and carry no category designation requirement.
The practical effect of the prefix is visible to recipients: a message arriving from "AD-HEALTHCO" is immediately identifiable as advertising or marketing content. The TDRA framework also allows recipients to opt out of promotional messages from specific categories by texting "AD-BrandName B" to 7726, or to block all promotional messages by texting "B ALL" to the same shortcode. Marketing categories that require TDRA pre-approval before messages can be sent include banking, real estate, health services, education, retail, tourism, and charitable services. Organizations in these categories should confirm current TDRA requirements with their provider before the first promotional send.
The sender ID itself must consist of alphanumeric characters. Numeric-only sender IDs are not supported for commercial A2P messaging in the UAE. The sender name must match the organization's registered company name, trademark, or a recognizable abbreviated form that the TDRA can verify against submitted documentation.
Sender ID registration with e& and du is not a fast process for international organizations. Local UAE-registered entities can generally expect five to ten business days. International companies should plan for the process to take up to 20 to 25 business days from submission of complete documentation, with no guaranteed fast-track option.
Documentation requirements typically include a No Objection Certificate (NOC) letter on company letterhead signed by an authorized representative and stamped with the company seal, a completed carrier-specific sender ID registration form, proof of identity for the authorized signatory, and a trademark certificate if the sender ID does not clearly resemble the registered company name. International sender IDs also carry a monthly recurring charge, currently around USD 40 per sender ID per month. This is a cost the program must budget for on an ongoing basis rather than a one-time registration fee.
TDRA's sender ID approval process assigns a unique verification record to each approved sender name, used to authenticate the sender at the carrier level as part of the UAE's broader anti-fraud framework for SMS.
Registration is infrastructure, not administration. In a market where a non-compliant promotional message can attract a penalty of up to 400,000 AED, and where carrier filtering makes unregistered sender IDs effectively non-functional, sender ID approval is the prerequisite for any UAE program. The 20-to-25-business-day international registration timeline means that for a program with a launch date, sender ID registration must begin at least six weeks prior.
The UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) sets the data protection framework for SMS programs alongside the TDRA's telecommunications-specific regulations. Consent for promotional messaging cannot be inferred from an existing customer relationship. It must be explicitly obtained, documented with a timestamp and source, and retained for as long as necessary to demonstrate compliance and satisfy applicable regulatory expectations.
If TDRA requests evidence of consent for a specific contact, organizations should be able to provide it promptly upon request. Consent documentation architecture is not a compliance afterthought in the UAE. It is a live operational requirement.
Opt-out handling must be honored. The TDRA framework requires organizations to process opt-out requests and remove contacts from marketing lists promptly. The TDRA's category-based opt-out mechanism, which allows recipients to block entire marketing categories rather than only specific senders, means that a contact who opts out of "real estate" promotions may not be reachable for real estate marketing even if they have given prior consent to a different organization in the same category.
Sending hours for promotional messages are restricted to 7 AM to 9 PM UAE time (UTC+4). Messages sent outside this window are generally subject to carrier blocking. Transactional messages arising from user-initiated actions have more flexibility on timing.
WhatsApp messaging, including text, images, and file sharing, works fully in the UAE. The UAE is one of the few markets where WhatsApp messaging is ubiquitous while WhatsApp voice remains restricted. WhatsApp voice and video calls are restricted at the carrier network level, as the TDRA requires VoIP services to operate through licensed UAE operator infrastructure. WhatsApp Business API for business-to-consumer messaging is available and operates normally within the UAE. For organizations running customer notifications, appointment reminders, transactional messages, and service communications, WhatsApp through the Business API is a legitimate and widely used channel in the UAE.
For voice communications, the TDRA licenses a set of approved VoIP applications. Botim is currently the dominant licensed calling and messaging application in the UAE, having grown from a simple VoIP tool into a full super-app with payments, remittances, and shopping features. GoChat, operated by e&, and C'Me are also TDRA-approved. These applications operate through the licensed telecom infrastructure rather than over unlicensed internet paths.
For organizations already using Botim for customer or workforce communications, or exploring it as a messaging channel for UAE audiences, the landscape is developing. Telerivet does not currently have a Botim channel integration, but organizations exploring this path are welcome to reach out to discuss what a potential integration would require and how it might fit alongside existing SMS and WhatsApp programs.
The UAE is a market where channel choice matters as much as compliance. High smartphone penetration and widespread WhatsApp adoption mean many organizations achieve the best results by reserving SMS for critical transactional notifications such as OTPs, payment alerts, and appointment reminders, while using WhatsApp Business for richer customer conversations. Compliance determines whether messages can be sent. Channel strategy determines whether customers engage with them.
The penalty ceiling of 400,000 AED per violation is the headline figure, but the full enforcement picture is broader. TDRA-defined violations include sending promotional SMS without an approved "AD-" sender ID, sending messages outside permitted hours, sending without valid documented consent, including prohibited content, and misclassifying promotional content as transactional to bypass registration requirements. Platform-level compliance is also part of the framework: SMS platforms operating in the UAE are expected to enforce TDRA rules through routing, filtering, and controls, which means the compliance responsibility is shared between the sending organization and its SMS provider. Using a provider without proper UAE carrier relationships and TDRA compliance posture creates exposure regardless of how carefully the sending organization has documented its own consent. Additional consequences may include sender ID suspension and account-level restrictions depending on the provider and operator.
The UAE's compliance framework is among the most structured in the Middle East and North Africa region. Operators building multi-market programs that include the UAE alongside European markets such as France or the UK will recognize the double-layer architecture: a telecoms regulator (TDRA, equivalent to ARCEP or Ofcom) setting carrier-level requirements, and a data protection framework (PDPL) running in parallel for personal data obligations. The key differences from European markets are the AD- prefix requirement for promotional SMS, the category pre-approval system, the aggressive penalty structure, and the 20-to-25-business-day international registration timeline.
BYOC architecture matters in the UAE for the same reason it matters in every high-compliance market. Your consent records, registration documentation, and suppression lists should belong to the organization and sit above the connectivity layer. When you change SMS providers or add a channel, the compliance assets travel with the program. For UAE specifically, the blockchain-verified sender ID is registered to your organization through the operator portals, not to a specific SMS platform. That portability is worth preserving from the outset.
For channel decisions in the UAE, the knowledge base guide on channel selection covers how to sequence SMS alongside WhatsApp and other channels for a Middle Eastern audience. The UAE is a high-smartphone, high-WhatsApp-messaging market where channel orchestration across SMS and WhatsApp generally outperforms either channel alone.
What is the AD- prefix requirement for UAE SMS? All promotional sender IDs in the UAE must include "AD-" before the brand name, such as "AD-ACMELOGISTIC". This has been mandatory since November 3, 2020, under TDRA regulation. Sender IDs without the AD- prefix will generally not be approved for promotional use. Transactional sender IDs, used for OTPs and service messages, do not require the prefix.
How long does sender ID registration take in the UAE? For local UAE-registered entities, typically five to ten business days. For international companies, up to 20 to 25 business days with no fast-track option. Documentation requirements include a No Objection Certificate letter, carrier-specific registration forms, proof of identity, and potentially a trademark certificate. International sender IDs carry a monthly recurring cost of approximately USD 40 per sender ID.
Does WhatsApp work in the UAE? WhatsApp messaging, including text, images, and file sharing, works fully in the UAE. WhatsApp voice and video calls are restricted at the carrier level. WhatsApp Business API for business-to-consumer messaging operates normally. For voice communications, TDRA-licensed alternatives such as Botim, C'Me, and GoChat are used.
What are the penalties for non-compliant SMS in the UAE? TDRA can impose penalties of up to 400,000 AED (approximately $109,000 USD) per violation. Violations include missing AD- prefixes on promotional messages, sending outside permitted hours, sending without documented consent, prohibited content, and misclassifying promotional traffic as transactional. Additional consequences may include sender ID suspension and account-level restrictions depending on the provider and operator.
Can I send SMS to UAE recipients if I am based outside the UAE? Yes, but international organizations face specific requirements: the registration process that can take up to 20 to 25 business days, monthly recurring charges for international sender IDs, and full compliance with both the TDRA regulatory framework and the UAE PDPL for data protection. Organizations sending messages into the UAE should assume the applicable UAE regulatory framework applies to those communications regardless of where the sending organization is based.
This article provides general operational information and should not be considered legal advice. Organizations should consult qualified legal or telecommunications professionals regarding their specific compliance obligations under UAE law.
Talk to our team about building a compliance-ready messaging program for the UAE and across your global markets from one platform