---
title: "Jordan SMS Guideline"
slug: "jordan-sms-guideline"
updated: 2025-12-12T11:56:53Z
published: 2025-12-12T11:56:53Z
canonical: "academy.insiderone.com/jordan-sms-guideline"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Jordan SMS Guideline

You can refer to the SMS guidelines for Jordan, which will assist you during onboarding.

This article provides details about:

- [Promotional Routes](/v1/docs/jordan-sms-guideline#promotional-routes)
- [Transactional Routes](/v1/docs/jordan-sms-guideline#transactional-routes)

| Locale Name | ISO Code | Region | Dialing Code | Available Routes |
| --- | --- | --- | --- | --- |
| Jordan | JO | Middle East & Africa | +962 | Promotional Transactional |

## Promotional Routes

| Available Sender IDs | Comparison of Sender IDs | Opt-out Options for Sender IDs |
| --- | --- | --- |
| Dynamic Alphanumeric Sender ID | - The sender ID must begin with the prefix "adv," such as "advSenderID" (prefix and sender ID must not exceed 11 characters) - If your Sender Address is not registered, messages will fail to be delivered. - Branded Sender ID - 10 MPS is the default - High deliverability | No opt-out content is required to be added for marketing SMS |

## Transactional Routes

SenderID approval processes are the same for transactional routes to use [SMS transactional API](/v1/docs/send-transactional-sms).