Jordan SMS Guide: Compliance, Regulations & API Integration Best Practices

Sending SMS messages to Jordan requires understanding specific regulatory requirements and carrier guidelines. This guide covers everything you need to know about Jordan SMS regulations, including TRC compliance, alphanumeric sender ID registration with Zain, Orange, and Umniah networks, time restrictions for promotional messages, and API integration best practices.

Jordan SMS Market Overview

Market Conditions: Jordan has a vibrant mobile communications market with three major operators: Zain, Orange, and Umniah. As of early 2024, Jordan has approximately 9.14 million active cellular mobile connections, representing 80.4% of the total population – an increase of 407,000 connections (+4.7%) from early 2023. SMS remains a crucial communication channel for businesses, particularly for authentication, notifications, and marketing. While OTT messaging apps like WhatsApp dominate personal communication, SMS maintains its position as the most reliable channel for business communications due to its universal reach and high open rates.

Operator Comparison

Key SMS Features and Capabilities in Jordan

Jordan supports most standard SMS features, including concatenated messages and alphanumeric sender IDs, though two-way SMS functionality is limited and MMS messages convert to SMS with URL links.

Two-way SMS Support

Two-way SMS is not supported in Jordan through major SMS providers. You cannot receive replies to your messages through standard SMS APIs.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation works for most sender ID types.

Message length rules: Messages exceeding 160 characters split into multiple segments when using GSM-7 encoding.

Encoding considerations:

• GSM-7 encoding: 160 characters per segment (English and basic characters)
• UCS-2 encoding: 70 characters per segment (Arabic and special characters)

Practical example:

• English message "Your verification code is 123456" = 35 characters (1 segment)
• Arabic message "رمز التحقق الخاص بك هو 123456" = 32 characters (1 segment)
• Mixed message exceeding 160/70 characters splits into multiple segments

Characters that trigger UCS-2 encoding:

• Arabic script (ا ب ت ث ج ح خ…)
• Emojis (😊 🎉 ✅)
• Special symbols not in GSM-7 (€ « » " ")

Billing implications: Each segment counts as one message. A 161-character GSM-7 message splits into 2 segments and costs 2× the single-message price.

Optimization tips:

• Keep English messages under 160 characters to avoid segmentation
• Keep Arabic messages under 70 characters for single-segment delivery
• Avoid emojis and special characters unless necessary
• Test message length before sending bulk campaigns

MMS Support

MMS messages are not directly supported in Jordan. MMS content automatically converts to SMS with an embedded URL link where recipients can view the multimedia content.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Jordan. Users can keep their phone numbers when switching between mobile operators. Messages route properly to the current carrier regardless of the original operator.

Sending SMS to Landlines

SMS to landline numbers is not supported in Jordan. Attempts to send messages to landlines result in failed delivery and trigger a 400 response error (error code 21614) from SMS APIs. These messages will not appear in logs, and your account will not be charged for the attempt.

Common error codes:

• 21614: Invalid phone number (landline or non-mobile)
• 21408: Permission to send not enabled for region
• 30007: Message filtered (content blocked)
• 30008: Unknown destination (invalid number format)

Compliance and Regulatory Guidelines for SMS in Jordan

The Telecommunications Regulatory Commission (TRC) of Jordan oversees SMS communications and enforces specific guidelines for business messaging. Comply with both TRC regulations and individual mobile operator requirements to ensure successful message delivery and regulatory compliance.

Consent and Opt-In

Obtain explicit consent before sending any marketing or promotional messages to users in Jordan. Best practices for obtaining and documenting consent include:

• Collect written or electronic opt-in confirmation
• Maintain detailed records of when and how you obtained consent
• Clearly state the types of messages users will receive
• Provide transparent information about message frequency
• Document the specific phone number that gave consent

Compliant opt-in form example:

<form>
  <input type="checkbox" id="sms-consent" name="sms-consent" required>
  <label for="sms-consent">
    I agree to receive promotional SMS messages from [Brand Name]
    at the phone number provided. Message frequency varies.
    Reply STOP to opt out at any time. Message and data rates may apply.
  </label>
  <input type="tel" name="phone" placeholder="+962 7X XXX XXXX" required>
  <button type="submit">Subscribe</button>
</form>

Consent documentation checklist:

• ✅ Phone number
• ✅ Consent timestamp
• ✅ Consent method (web form, verbal, written)
• ✅ IP address (for web opt-ins)
• ✅ Message category (promotional, transactional, both)

HELP/STOP and Other Commands

Include clear opt-out instructions in all marketing messages. Support STOP commands in both English and Arabic.

Required keywords to honor:

• STOP / إيقاف
• CANCEL / إلغاء
• UNSUBSCRIBE / إلغاء_الاشتراك

Process opt-out requests within 24 hours.

Example opt-out message:

[Brand Name]: Your promotion ends tomorrow! Get 20% off. Reply STOP to opt out or إيقاف لإلغاء الاشتراك

Do Not Call / Do Not Disturb Registries

Jordan does not maintain a centralized Do Not Call registry. However, you must:

• Maintain your own suppression lists
• Honor opt-out requests immediately
• Keep records of opted-out numbers for at least 12 months
• Implement systems to prevent messaging to opted-out numbers

Suppression list implementation guidance:

Database design recommendation:

CREATE TABLE sms_suppression_list (
  id SERIAL PRIMARY KEY,
  phone_number VARCHAR(20) NOT NULL UNIQUE,
  opted_out_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  opt_out_method VARCHAR(50), -- 'SMS_STOP', 'WEB_FORM', 'CUSTOMER_SERVICE'
  campaign_id VARCHAR(100),
  notes TEXT
);

CREATE INDEX idx_phone_number ON sms_suppression_list(phone_number);
CREATE INDEX idx_opted_out_at ON sms_suppression_list(opted_out_at);

API integration pattern:

// Before sending SMS, check suppression list
async function sendSMS(phoneNumber, message) {
  const isOptedOut = await checkSuppressionList(phoneNumber);

  if (isOptedOut) {
    console.log(`Skipping ${phoneNumber} - opted out`);
    return { status: 'skipped', reason: 'opted_out' };
  }

  // Proceed with SMS sending
  return await smsProvider.send(phoneNumber, message);
}

async function checkSuppressionList(phoneNumber) {
  const result = await db.query(
    'SELECT 1 FROM sms_suppression_list WHERE phone_number = $1',
    [phoneNumber]
  );
  return result.rows.length > 0;
}

Time Zone Sensitivity

Jordan enforces strict time-based restrictions for promotional messages:

• Promotional messages: Send only between 7:00 AM and 9:00 PM Amman time (GMT+3)
• Transactional messages: Send 24/7 – no time restrictions apply
• Best practice: Send messages between 9:00 AM and 8:00 PM local time for optimal engagement

Penalties for violating time restrictions:

• Message blocking by carriers
• Account denylisting or suspension
• Sender ID revocation
• Financial penalties from TRC (amount varies by violation severity)
• Legal liability under Jordan telecommunications law

Timezone-aware sending implementation:

// Using moment-timezone with Twilio
const moment = require('moment-timezone');
const twilio = require('twilio');

const client = twilio(accountSid, authToken);

async function sendPromoSMS(phoneNumber, message) {
  const jordanTime = moment().tz('Asia/Amman');
  const hour = jordanTime.hour();

  // Check if current time is within allowed window (7 AM - 9 PM)
  if (hour < 7 || hour >= 21) {
    // Schedule for next available time slot
    const nextSendTime = hour >= 21
      ? jordanTime.add(1, 'day').hour(9).minute(0)
      : jordanTime.hour(9).minute(0);

    console.log(`Scheduling message for ${nextSendTime.format()}`);

    return await client.messages.create({
      to: phoneNumber,
      from: 'advYourBrand',
      body: message,
      scheduleType: 'fixed',
      sendAt: nextSendTime.toISOString()
    });
  }

  // Send immediately
  return await client.messages.create({
    to: phoneNumber,
    from: 'advYourBrand',
    body: message
  });
}

# Using pytz with Sinch
from datetime import datetime
import pytz
from sinch import SinchClient

def send_promo_sms(phone_number: str, message: str):
    jordan_tz = pytz.timezone('Asia/Amman')
    jordan_time = datetime.now(jordan_tz)
    hour = jordan_time.hour

    # Check if current time is within allowed window (7 AM - 9 PM)
    if hour < 7 or hour >= 21:
        print(f"Outside allowed hours ({hour}:00). Message blocked.")
        return {"status": "blocked", "reason": "time_restriction"}

    # Send immediately
    client = SinchClient(api_key="YOUR_API_KEY")
    return client.sms.send(
        to=phone_number,
        from_="advYourBrand",
        body=message
    )

Phone Numbers Options and SMS Sender Types for Jordan

Long Codes

Support:

• Domestic long codes: Not supported
• International long codes: Supported but convert to alphanumeric sender IDs

Sender ID preservation: No, international long codes typically overwrite

Provisioning time: N/A

Use cases: Not recommended for Jordan – use registered alphanumeric IDs instead

Short Codes

Support: Not currently supported in Jordan

Provisioning time: N/A

Use cases: N/A

How to Register Alphanumeric Sender IDs in Jordan

Pre-register alphanumeric sender IDs with Jordan mobile networks before sending SMS messages. The registration process and requirements differ for local and international companies.

Registration Decision Tree

Start: Where is your company headquartered?
│
├─ Jordan (Local Company)
│  └─ Register with all three operators (Zain, Orange, Umniah)
│     └─ Timeline: 7 business days
│     └─ Required: Trade license + business registration + samples
│     └─ Fee: None
│
└─ Outside Jordan (International Company)
   └─ Which network do you need?
      │
      ├─ Zain only
      │  └─ Pre-registration required
      │     └─ Timeline: 3 business days
      │     └─ Required: Company details + message samples
      │     └─ Fee: None
      │
      └─ Orange or Umniah
         └─ No pre-registration needed
            └─ Timeline: Immediate (dynamic sender IDs)
            └─ Required: Valid sender ID format
            └─ Fee: None

Registration Timeline and Requirements

Operator network capability: Fully supported across all three major carriers (Zain, Orange, Umniah)

Local companies (headquarters in Jordan):

• Registration time: 7 business days across all networks
• Required documentation: Sender ID, company name, website, message content samples, trade license, and business registration
• Registration fee: None

International companies:

• Zain network: 3 business days registration time (pre-registration required)
• Umniah-Orange networks: Dynamic alphanumeric sender IDs allowed without pre-registration
• Required documentation: Sender ID, company name, website, and message content samples

How to submit registration:

For Zain:

• Email: enterprise@jo.zain.com
• Submit: Completed sender ID registration form (available on request)
• Include: All required documentation as PDF attachments

For Orange Jordan:

• Contact: Business Solutions department at +962 6 464 2020
• Submit: Via business account portal or email to business.support@orange.jo
• Include: Company registration documents and sender ID request form

For Umniah:

• Email: business@umniah.com
• Portal: Register through Umniah Business Portal (business.umniah.com)
• Include: Company details and message samples

Key Registration Rules

Sender ID format: 3–11 alphanumeric characters, case-sensitive, containing the brand name

Message type requirements:

• Promotional messages: Must include "adv" prefix (e.g., "advBrandName")
• Transactional messages: Use registered sender IDs without the "adv" prefix

Prohibited sender IDs: INFO, SMS, NOTICE, and similar generic IDs are not allowed

Sender ID preservation: Yes, registered IDs preserve across networks

Valid sender ID examples:

• ✅ advAcmeShop – Promotional, includes required "adv" prefix
• ✅ AcmeBank – Transactional, brand-specific
• ✅ MyApp123 – Alphanumeric with numbers, 8 characters
• ✅ JO_Express – Contains underscore, 10 characters

Invalid sender ID examples:

• ❌ AB – Too short (minimum 3 characters required)
• ❌ VeryLongBrandName – Too long (maximum 11 characters)
• ❌ INFO – Generic, prohibited keyword
• ❌ SMS-Alert – Contains hyphen (alphanumeric only)
• ❌ BrandName – Promotional content without "adv" prefix
• ❌ adv Brand – Contains space (not allowed)

Common rejection reasons:

1. Generic terminology – Using INFO, SMS, ALERT, NOTICE
2. Missing "adv" prefix – Promotional content without required prefix
3. Length violation – Under 3 or over 11 characters
4. Invalid characters – Contains spaces, hyphens, or special symbols
5. Misleading content – Sender ID doesn't match brand/company name
6. Trademark infringement – Using another company's brand name

Appeal process: If your sender ID gets rejected:

1. Contact the operator's business support team
2. Request specific rejection reason
3. Revise sender ID based on feedback
4. Resubmit with corrected information
5. Typical appeal response: 2–3 business days

Content Acknowledgment

According to regulations enforced by AWS and other major carriers, acknowledge that registered sender IDs will be used exclusively for transactional messages. Promotional content requires sender IDs with the "adv" prefix and must comply with time restrictions (7 AM – 9 PM).

Transactional vs. Promotional Content:

Transactional message examples:

YourBank: Your OTP code is 582914. Valid for 5 minutes. Do not share this code.

ShopExpress: Your order #12345 has shipped. Track: https://track.shop/12345

RideApp: Your ride with Ahmed will arrive in 3 minutes. Toyota Camry, Plate: 12345.

Promotional message examples:

advFashionStore: Flash Sale! 40% off all summer collection. Shop now: https://fashion.jo/sale Reply STOP to opt out

advRestaurant: New menu launching Friday! Reserve your table today. Call 06-123-4567 or visit restaurant.jo إيقاف STOP

advGymFit: Join today and get 2 months free! Limited slots. https://gym.jo/offer Text STOP to unsubscribe

Content filtering and blocked keywords:

Jordan operators filter messages containing certain keywords to prevent fraud and abuse.

Commonly blocked keywords:

• Gambling terms (casino, poker, betting)
• Adult content references
• Cryptocurrency scams
• Fake prize/lottery claims
• Phishing attempts ("verify your account immediately")

Message approval process:

1. First-time sender IDs undergo content review
2. Operators may request message samples before approval
3. Significant content changes may require re-approval
4. High-volume senders receive ongoing monitoring

Best practices to avoid filtering:

• Use clear, professional language
• Include your brand name in the message
• Provide legitimate contact information
• Avoid excessive capitalization or urgency
• Don't use URL shorteners that mask destination

Frequently Asked Questions About Jordan SMS

How long does sender ID registration take in Jordan?

Registration timelines vary by company location and carrier. Local companies (with headquarters in Jordan) require 7 business days for registration across all networks. International companies need 3 business days for Zain network registration, while Umniah-Orange networks allow dynamic alphanumeric sender IDs without pre-registration.

What time can I send promotional SMS messages in Jordan?

Send promotional SMS messages in Jordan only between 7:00 AM and 9:00 PM Amman time (GMT+3). Violating this restriction results in message blocking and potential account denylisting. Send transactional messages 24/7 without time restrictions.

Do I need to add "adv" prefix to my sender ID in Jordan?

Yes, all promotional messages sent in Jordan must use a sender ID with the "adv" prefix (e.g., "advBrandName"). The Telecom Regulation Commission of Jordan requires this. Transactional messages using registered sender IDs do not require this prefix.

Is SMS to landline supported in Jordan?

No, SMS to landline numbers is not supported in Jordan. Attempts to send messages to landlines fail with a 400 error (error code 21614), will not appear in logs, and will not incur charges.

What mobile operators serve Jordan?

Jordan has three major mobile operators: Zain, Orange, and Umniah. All three support SMS messaging, though registration requirements and capabilities vary slightly between carriers. Number portability is available, ensuring messages reach recipients regardless of their current carrier.

Is there a fee for Jordan sender ID registration?

No registration fee applies for sender ID registration in Jordan. However, standard per-message SMS charges apply when sending messages.

Can I use two-way SMS in Jordan?

No, two-way SMS is not supported in Jordan through major SMS providers. You cannot receive replies to your messages through standard SMS APIs.

Quick Reference: Jordan SMS Compliance Checklist

Use this checklist to ensure your SMS campaigns comply with Jordan regulations:

Pre-Launch Requirements:

• Obtain explicit consent from all recipients
• Register alphanumeric sender ID with carriers
• Verify sender ID format (3–11 characters, alphanumeric)
• Add "adv" prefix for promotional messages
• Implement suppression list database
• Configure timezone checks (GMT+3 Amman time)

Message Content:

• Include brand name in sender ID
• Add opt-out instructions in promotional messages
• Support STOP/CANCEL keywords in English and Arabic
• Verify message length (160 GSM-7 / 70 UCS-2 per segment)
• Test for blocked keywords or filtered content
• Include working customer support contact

Sending Rules:

• Send promotional messages only 7 AM – 9 PM
• Honor opt-out requests within 24 hours
• Check phone numbers against suppression list
• Avoid sending to landline numbers
• Maintain consent documentation for 12+ months
• Monitor delivery reports and error codes

Ongoing Compliance:

• Update suppression list regularly
• Review message performance and delivery rates
• Renew sender ID registration as needed
• Audit consent records quarterly
• Train team on TRC regulations
• Monitor for regulation changes

Recap and Additional Resources