How to whitelist your Sender ID at IAM, Orange and inwi

You configure the API, you set sender: "MAMARQUE", and the result is frustrating: the SMS arrives in some of your employees, but not in others. Why? Because routing in Morocco depends on three separate networks (Maroc Telecom, Orange, inwi), and your brand authorization must be configured on the firewalls of the three operators.

Here’s how this complex process takes place behind the scenes and how to manage validation asymmetries.

The Moroccan telecom infrastructure does not have a "central database" for business Sender IDs. Each operator (IAM, inwi, Orange Morocco) has its own SS7 (SMS Firewall) filtering system and its own compliance teams (NOC - Network Operations Center).

To protect their subscribers from phishing (fraudulent SMS of the type “Your package is blocked”), each operator requires to manually verify that the company “Alpha S.a.r.l” has the right to send SMS under the name “AlphaPromo”.

As a business, you do not directly contact IAM or Orange for this. This is the role of your gateway provider (Gateway SMS).

The typical validation stream: 1.You submit your Commitment Letter (NOC) and your RC via the EnvoiSMS.ma console 2.Our routing engineers verify technical compliance (length < 11 characters, permitted characters). 3.We officially forward your company file, through our routing partners, to the 3 Moroccan operators. 4.The operators configure their filters to accept traffic from our routes under this specific Sender ID.

The absence of synchronization creates a “grey zone”: each operator moves at its own pace, and your Sender ID can be live on one network several days before the others. End to end, approval takes 15 to 30 days:

• Inwi Network: validates on its own schedule.
• Maroc Orange Network: a very strict process, on its own schedule.
• IAM Network (Maroc Telecom): as a leading operator concentrating huge traffic, manual configuration times are sometimes longer.

The typical developer error: Testing the campaign on your own Orange phone as soon as the Sender ID goes through there, seeing that it works, and launching the overall campaign.Result: All IAM customers get nothing, and the DLR rate "Failed/Rejected" explodes.

During the "grey zone" phase (e.g. inwi and orange have validated, but IAM is waiting), how to communicate?

1. Don’t launch your global marketing campaigns. Wait for the official confirmation from the provider that all 3 sights are green.
2. Use the "Sender ID default" fallback for OTP: If you are incorporating urgent validation codes, configure your code to detect an error 403 Forbidden or a DLR Rejected.

// Exemple logique de fallback Node.js (Pseudo-code)
async function sendImportantOtp(userPhone, code) {
  try {
    // Tentative avec le Sender ID de marque en cours de validation
    await smsApi.send({ to: userPhone, body: `Code: ${code}`, sender: "MAMARQUE" });
  } catch (error) {
    if (error.statusCode === 403 || error.code === 'SENDER_ID_REJECTED') {
      console.warn("Sender ID bloqué (sûrement IAM en attente). Fallback...");
      // Nouvel essai avec le Sender ID de secours pré-approuvé
      await smsApi.send({ to: userPhone, body: `Code: ${code}`, sender: "ENVOISMS" });
    }
  }
}

The key to robust routing is to always anticipate that the network operator has the last word.

To check whether the gap you see between carriers is normal, compare it with the per-carrier delivery rates measured in our benchmark.