Outbound calling in Oman under the 2026 TRA rules

Article 16 allows promotional calls and promotional messages only between 08:00 and 21:00 Oman time. The rule binds the licensed operator, the local subscriber and the international subscriber alike, so a team dialling Muscat from abroad is held to the same clock. Messages sent inside the window whose delivery is delayed by a technical problem do not count as a breach.

The window covers promotional traffic only. Service messages, which the regulation defines to include service information, transaction notifications, electronic authentication and one-time passwords, are not brought within it. Keep OTPs and delivery updates in separate campaigns from offers, so the 21:00 cut-off stops only promotional traffic.

The regulation states "Oman time" without citing a UTC offset, so set the time zone in your dialler settings rather than hard-coding it into scripts. In DialerBee the calling window is configured per tenant and per campaign and checked before every call is placed. Oman does not ship as a ready-made jurisdiction pack (the packs cover UAE TDRA, KSA CST, Jordan TRC and Bahrain TRA), so you enter the 08:00 to 21:00 window yourself.

The full text of the regulation contains no day-of-week or public-holiday carve-out. Oman has worked a Sunday-to-Thursday week with a Friday and Saturday weekend since 2013 (workweek reference), so most teams leave both days off their calling calendar as a matter of courtesy rather than law.

The timing of the transition makes Ramadan 2027 a planning issue. Ramadan is expected to begin around 8 February 2027, subject to moon sighting, with Eid al-Fitr expected around 9 to 10 March 2027. The Omani conformity deadline of about 17 February 2027 falls inside the fasting month. Finish the sender ID, caller-name and opt-out changes before Ramadan starts, then switch to your Ramadan calling hours, lighter frequency caps and the Eid holiday calendar. The GCC Ramadan playbook walks through those settings.

No public one. Instead, Article 17 requires every licensed operator to run a TRA-approved way for users to stop promotional calls, promotional messages or value-added services, with blocking of all senders or chosen ones, confirmation, complaints handling and re-enablement, and to build a unified database with the other operators. The regulation does not say when that database goes live or how advertisers connect to it; the transition period to February 2027 is the build window.

Your own duty comes from the data protection side, and it is strict. Oman's PDPL has no legitimate-interests basis, so marketing rests on consent alone. Article 10 requires explicit consent that you can prove, and Article 22 requires written consent before any advertising, marketing or commercial material. You must also name the channel, give a way to stop, and stop immediately and free of charge on request. No consent expiry period is published, so set your own.

In DialerBee, consent is created, updated and revoked as auditable records, and a revocation takes effect on the next call attempt, not the next list refresh. Operator opt-out lists can be imported into your do-not-call list, which is checked on every attempt.

Recording needs a legal basis. Article 68 bis of the Telecommunications Regulatory Act makes recording a telephone message without legal basis an offence carrying up to six months and/or a fine up to OMR 2,000. A recording is also personal data under the PDPL. The 2026 regulation has no "this call is recorded" announcement rule; confirm with the TRA before relying on that.

Cross-border transfer is the largest exposure. Under PDPL Article 23, before Omani personal data leaves the country you need the person's explicit consent, a recipient whose protection is no lower than Omani law, and a written transfer risk assessment, which MTCIT can ask to see. A breach carries OMR 100,000 to 500,000. Include your contact-centre platform in that assessment; DialerBee's implemented and planned controls are listed on the Trust Center.

You also need a published data protection officer, breach notification within 72 hours and answers to data-subject requests within 45 days. DialerBee's call recording has configurable retention, legal hold, per-tenant isolation and an auditor export.

Most Omani callers speak Gulf Arabic (Khaleeji),, whose greetings, numbers and polite forms differ from Modern Standard Arabic. English is the common second language in business. DialerBee's AI voice agent handles Gulf, Levantine and Egyptian Arabic plus ten more languages, including English, Urdu and Hindi; AI answering machine detection and transcription cover the same 11 languages. See the Arabic AI voice agent page for how to test dialect handling with your own callers, for example asking for a slot "after Maghrib" or on "Thursday evening", which is the last evening of the Omani working week.

An AI voice agent calling Omani numbers is an automated call, so caller-name display and the 08:00 to 21:00 window apply to it. For inbound, an AI receptionist can take calls after 21:00 or over the Friday and Saturday weekend, since the window limits promotional outbound traffic only.