When setting up your [SMS API] (/fr/api-sms-maroc/) for the Moroccan market, one of the first technical and marketing decisions you need to make concerns the identity of the sender (the Sender ID).
In Morocco, you can choose between two formats: 1. Alpha-numeric (e.g. Your MARK), which displays text. 2. Digital (e.g. 0612345678 or a shortcode), which displays a telephone number.
Choosing the wrong format can reduce your customer confidence, increase your integration costs, or worse, block your customers’ ability to respond to you.
Technical differences between the two formats
The Sender ID Alfanumeric (Text) - Format: Up to 11 characters (letters and numbers). - Mode of operation: It is a channel unidirectional (One-way). The customer receives the message, but he has no "Respond" button on his phone, or if he tries to respond, the phone will display an error. - Moroccan Contract: Requires a manual whitelisting procedure from IAM, Orange and inwi (15 to 30 days).
The Sender Digital ID (Telephone Number) - Format: An international long number (+2126XXXXXX) or a short number (Shortcode of 4 or 5 digits). - Mode of operation: It is a potentially bidirectional (Two-way) channel. If the number belongs to you and is configured for receipt, the customer can respond to the SMS. - Moroccan counter: Using a standard long number (Longcode) usually does not require complex manual validation, routing is immediate (ideal for Sandbox mode tests).
When to use a brand name (alphanumeric)
This is the standard for 90% of professional B2C shipments in Morocco.
You must imperatively use an alfanumeric Sender ID for: 1. Authentication (OTP / 2FA): Receiving a security code from an unknown number 06X... is suspicious.Receiving from Your BANK reassures the user immediately.2. SMS Marketing campaigns: For branding, the user must identify the sender within a fraction of a second even before reading the content.3. Urgent transaction alerts: Fraud alerts, payment confirmation, delivery status.
Business impact: Studies show that the rate of openness and trust generated by an OTP sent via a branded Sender ID is significantly higher.
When a number is preferred (OTP case, customer response)
The alphanumeric is aesthetic, but it has a major disadvantage: it prohibits conversation. You must choose a Digital Sender ID (Virtual Longcode or Shortcode) in the following cases:
- B2B or medical appointment confirmation: If you send "RDV reminder tomorrow at 2 p.m. Answer YES to confirm or NO to cancel", you must use a digital number in order for the customer to respond.
- Interactive customer service: If you are managing SMS support tickets or want to migrate the conversation to hybrid logic (SMS to call).
- Native opt-out: Although the CNDP requires that "STOP at 06XX" be included in the alfanumeric text body, having a digital number allows the customer to answer directly "STOP".
Legal and technical limits of each option
Alpha-numerical limits: - Administrative implementation time. - Risk of blocking if the content is deemed inappropriate by the operators (the operator blocks the entire brand).
Digital limits (shared long code): - If you use a shared long number provided by a foreign platform (e.g. a +44 or +1), Moroccan carriers massively filter these shipments for fraud (smishing).Your delivery rate will collapse. - If you use a real Moroccan mobile number (+212) behind a GSM gateway (SIM Box), this is strictly prohibited by ANRT.Your SIM card will be blocked from the first mass shipments.
Architecture Recommendation: For a modern project (e-commerce, SaaS, mobile app), use a hybrid approach. Request a Sender ID alfanumeric for all your one-way streams (OTP, critical alerts). For customer service or conversational transaction, switch to the WhatsApp Business API that natively manages two-way with a verified business identity.
Frequently asked questions
What is the routing latency on the IAM, Inwi and Orange networks?
On our local routes to Maroc Telecom (IAM), Orange and inwi, the median time to carrier confirmation is 11–17 s (measured in October 2026).
How does the platform manage the format of Moroccan numbers?
EnvoiSMS automatically normalizes the numbers entered (06..., 07..., 00212...) to the E.164 standard (+212) to avoid any delivery failure.