Skip to content
OmniChannels.ai
Menu

Bulk SMS in Jordan: TRC, Sender ID and Data Law Guide

Bulk SMS Jordan guide: TRC sender ID registration with annual renewal, Zain, Orange and Umniah routes, PDPL 2023 consent and Arabic Unicode.

Updated 10 min read

By OmniChannels.ai Editorial Team · Reviewed by BroadNet Messaging Solutions Team

SMS & OTP

Short answer

To send bulk SMS in Jordan, use a provider with direct routes to Zain, Orange and Umniah, register an alphanumeric sender ID (up to 11 characters, Latin or Arabic) with the TRC through the operators, and send marketing only with clear, documented consent under Jordan's Personal Data Protection Law (Law No. 24 of 2023). Keep OTPs separate from promotions and expect Arabic text to use Unicode at 70 characters per message.

On this page
  1. What rules apply to bulk SMS in Jordan?
  2. What does Jordan's Personal Data Protection Law require?
  3. Which operators carry SMS in Jordan?
  4. How does sender ID registration work in Jordan?
  5. How should you separate OTP, alerts and promotions?
  6. How do Arabic and English affect SMS length in Jordan?
  7. How do you keep consent records and handle withdrawal?
  8. When should you send?
  9. A worked example: a Jordanian retail bank
  10. What are the common mistakes?
  11. How can WhatsApp complement SMS in Jordan?
  12. Launch checklist for Jordan
  13. How OmniChannels.ai helps

Key takeaways

  • The regulator is the Telecommunications Regulatory Commission (TRC). Our regulation data lists sender ID registration as required, one ID per use case per entity, renewed annually, with a typical lead time of 5 to 7 business days.
  • Law No. 24 of 2023 on personal data protection took effect on 17 March 2024; it requires prior consent that is clear, written, and states its purpose and period, and it gives people the right to withdraw consent.
  • Our coverage data lists three mobile networks with direct routes: Zain Jordan (416-01), Umniah (416-03) and Orange Jordan (416-77).
  • Our regulation data asks you to keep consent records for at least 12 months and to produce them if the TRC asks.
  • Arabic is Unicode at 70 characters per message (67 per part); plain English fits 160 (153 per part) in GSM-7.

This guide is for banks, retailers, universities, government-adjacent services and operations teams that want to send business SMS to mobile numbers in Jordan: OTPs, payment alerts, reminders and promotions. It explains who regulates what, how sender IDs work on Zain, Orange and Umniah, what Jordan's 2023 data protection law means for consent, and how Arabic text changes message length. It is a practical overview, not legal advice; confirm requirements with Jordanian counsel and the operators before launch.

What rules apply to bulk SMS in Jordan?

Three layers apply: the TRC and the operators for telecom and sender IDs, the Personal Data Protection Law for consent, and your own consent records. We found no single statute named for bulk SMS.

Layer What it covers Where to check
TRC and operators (Zain, Orange, Umniah) Telecom regulation, sender ID registration, routes, filtering trc.gov.jo
Personal Data Protection Law, Law No. 24 of 2023 Consent, data subject rights, supervision Clyde & Co summary
Our regulation data Opt-in evidence, opt-out, sender ID rules Jordan sender ID page

Our regulation data lists the Telecommunications Regulatory Commission as regulator and records that opt-in is verifiable, with records kept for at least 12 months and produced on TRC request. It also records a one-step STOP or ايقاف opt-out honoured network-wide.

What does Jordan's Personal Data Protection Law require?

It requires prior consent for processing personal data unless another law permits it, and that consent must be clear and written, state a purpose and a period, and be easy to understand. Law No. 24 of 2023 was published in the Official Gazette on 17 September 2023 and took effect six months later, on 17 March 2024. Article 4(a) sets the consent rule, according to the Clyde & Co summary.

People also have rights to access and correct their data, to withdraw consent, to limit processing, to object, to erasure under conditions and to be told of breaches. A unit within the Ministry of Digital Economy and Entrepreneurship monitors compliance, and a Personal Data Protection Board considers complaints. Implementing instructions continue to develop, so ask counsel for the current position.

The law does not mention direct marketing specifically in the summary we reviewed, so apply it as the baseline: a phone number is personal data, and a marketing SMS list needs a lawful basis. For marketing, that means consent. Our opt-in consent generator drafts Arabic and English wording, and opt-in consent across channels shows how to record it.

Which operators carry SMS in Jordan?

Three mobile networks appear in our coverage data, each with a direct route.

Operator MCC-MNC Route
Zain Jordan 416-01 Direct
Umniah 416-03 Direct
Orange Jordan 416-77 Direct

Read delivery reports per operator rather than as one blended rate. Our Jordan market page summarises our channels there, and improving SMS delivery rates shows how to diagnose a weak network.

How does sender ID registration work in Jordan?

Business SMS uses an alphanumeric sender ID of up to 11 characters, Latin or Arabic. Our regulation data says registration is required with Zain, Orange and Umniah, one ID per use case per entity, with annual renewals and a typical lead time of 5 to 7 business days. Treat the lead time as typical, not guaranteed.

Step What to do
1. Classify List your use cases (OTP, payment alert, promotion) and plan one ID for each
2. Choose names Use your registered business name; avoid names that imitate banks, operators or ministries
3. Prepare documents Company registration and an authorisation letter naming your sender IDs and provider
4. Submit Your provider files with the operators and tracks every approval
5. Test Send each traffic type to Zain, Orange and Umniah handsets
6. Renew Diary the annual renewal so IDs never lapse mid-campaign

Draft the letter with the sender ID letter generator and check the position with the sender ID checker. We can prepare and file the registration with you (registrations); approval decisions stay with the operators and regulator. Background on formats: sender ID types explained.

How should you separate OTP, alerts and promotions?

Give OTPs and payment alerts their own transactional ID, and put promotions on another. Because registration is per use case, the separation also matches the rules.

Traffic Example Practice
Transactional OTP, payment confirmation, balance alert No offers; own ID; any hour
Promotional Campaign, loyalty offer, new branch Consented numbers only; opt-out line; daytime schedule
Mixed "Payment received. Apply for a card today" Avoid; the offer makes it promotional

See the OTP authentication messages guide for code design and fraud controls.

How do Arabic and English affect SMS length in Jordan?

Arabic is sent as Unicode: 70 characters in one message and 67 per part. Plain English fits GSM-7: 160 (153 per part). One Arabic letter converts the whole message to Unicode. See GSM-7 and concatenated SMS.

Encoding Single message Per part when concatenated
GSM 7-bit 160 characters 153
Unicode (UCS-2) 70 characters 67

Synthetic examples counted against the limits:

Message Encoding Characters Parts
Amman Bank: your code is 615027. Never share it. GSM-7 48 1
بنك عمان: رمز التحقق 615027. لا تشاركه مع أحد. Unicode 46 1
Amman Bank: payment of 25.000 JOD received on 05/11. Ref 88213. GSM-7 63 1
بنك عمان: وصلتنا دفعتكم بتاريخ 05/11. المرجع 88213. Unicode 51 1

Both languages fit one part here. Promotions are the risk: add an offer, a link and an opt-out line to Arabic text and you pass 70 characters quickly. Check copy in the SMS character counter and read SMS character limits and Unicode.

Store, for every number, the exact wording shown, the purpose and period stated, the date and time, the channel and the source. Our regulation data asks you to retain this for at least 12 months and produce it if the TRC requests it. Withdrawal should be as easy as sign-up: a STOP or ايقاف reply, a link or a branch request, with the number added to one suppression list the same day.

A practical test is to pick a number at random and answer three questions in under a minute: when did this person agree, to what exactly, and have they withdrawn since? If your systems cannot answer, fix that before scaling volume. Re-check the list after every import, because merged databases often bring back people who opted out.

When should you send?

We have not found a regulator-published time-of-day window for promotional SMS in Jordan, and our regulation data records none. Send promotions in local daytime (Jordan time, UTC+3), avoid late evenings and early mornings, and let OTPs and alerts run 24/7. Check Ramadan and holiday timing with the Ramadan messaging guide, use the send time planner, and compare other markets in SMS marketing rules by country.

A worked example: a Jordanian retail bank

"Amman Bank" (synthetic) wants OTPs, payment confirmations and an occasional offer.

  • It registers three sender IDs, one each for OTP, payment alerts and offers, and tests on Zain, Orange and Umniah.
  • Customers give written consent in the app and branch forms, naming the purpose and how long it lasts; the bank keeps the evidence for at least 12 months.
  • OTPs and alerts are short, with no offers, and are sent in Arabic with English as an option.
  • Offers go only to opted-in numbers, in daytime, with a clear STOP line.
  • A diary entry reminds the team to renew every ID each year.

What are the common mistakes?

  • Letting a sender ID lapse. Annual renewal is easy to forget.
  • One ID for several use cases. Registration is per use case, and mixing risks filtering.
  • Vague consent. The law expects a clear purpose and period.
  • Ignoring withdrawal. People can withdraw consent; suppress at once and across channels.
  • Unicode surprises. A 71-character Arabic message costs two parts.
  • Treating lead times as promises.

How can WhatsApp complement SMS in Jordan?

SMS reaches every handset and suits OTPs and fallback. WhatsApp suits two-way service, documents and rich media for opted-in customers. Label each WhatsApp template with its Meta category (marketing, utility or authentication) and keep content consistent. See the best WhatsApp Business API provider in Jordan and channel fallback strategy.

Launch checklist for Jordan

  1. List use cases and split transactional from promotional.
  2. Register one sender ID per use case; diary the annual renewal.
  3. Build Arabic and English consent wording with purpose and period; store evidence for at least 12 months.
  4. Count characters in both languages.
  5. Test on Zain, Orange and Umniah handsets.
  6. Schedule promotions for local daytime.
  7. Suppress opt-outs and withdrawals immediately across all channels.

How OmniChannels.ai helps

OmniChannels.ai is powered by BroadNet, which has direct routes to Zain, Orange and Umniah in our coverage data, and an office in Amman. BroadNet is licensed in every country where it operates. We prepare and file sender ID registration with you, support Arabic Unicode SMS and give you per-operator delivery reports. For indicative list prices, see the Jordan SMS pricing page, then book a demo.

Frequently asked questions

Is bulk SMS legal in Jordan?

Yes. Businesses in Jordan send OTPs, alerts and marketing by SMS through licensed routes. The TRC oversees telecoms, operators enforce sender ID rules and Law No. 24 of 2023 governs personal data. Use registered sender IDs, hold documented consent for marketing, honour opt-outs and confirm details with Jordanian counsel.

Do I need to register a sender ID in Jordan?

Plan on it. Our regulation data lists registration as required on Zain, Orange and Umniah, with one ID per use case per entity and annual renewals. The typical lead time is 5 to 7 business days, but that is not a promise. Add buffer, and set a renewal reminder so an ID does not lapse.

What does Jordan's data protection law say about consent?

Law No. 24 of 2023 requires the data subject's prior consent for processing unless another law allows it. Consent must be clear and written, state a purpose and a period, and be offered in easy language. People can withdraw consent at any time. The law took effect on 17 March 2024.

Who supervises Jordan's personal data law?

A data protection unit within the Ministry of Digital Economy and Entrepreneurship monitors compliance, and a Personal Data Protection Board chaired by the minister approves standards, issues licences and considers complaints. The TRC remains the telecom regulator for SMS routes and sender IDs. Check both when you design a programme.

How many Arabic characters fit in one SMS?

Seventy. Arabic is sent as Unicode (UCS-2), which holds 70 characters in one message and 67 per part when split. English-only text uses GSM-7 with 160 characters (153 per part). A single Arabic letter in an English message switches the whole message to Unicode, so count before you send.

Can I send OTPs and promotions on the same sender ID?

You can, but you should not. Our regulation data lists one ID per use case per entity, which points to separate IDs for separate purposes. A promotion that is filtered or reported can damage the reputation of the ID that carries your login codes. Keep OTPs and alerts on their own transactional ID.

Sources

  1. Telecommunications Regulatory Commission (TRC), Jordan
  2. Jordan issues first personal data protection law, Clyde & Co
  3. 3GPP TS 23.038: Alphabets and language-specific information

Keep reading

More guides