Question 1

Getting Started with EnvoiSMS.ma

Accepted Answer

Welcome to EnvoiSMS.ma. Our platform allows you to send SMS and WhatsApp Business sessions directly to mobile phones in Morocco using direct Tier-1 carrier connectivity. To get started, create a free account on our console. Once your information is verified, your account will be credited with 5 free SMS to test our routes in Sandbox mode. Within your dashboard, you will find your secret API access keys in the Developer tab. Keep them secure and never share them publicly.

Question 2

How to Send your First SMS

Accepted Answer

You can send your first message in two ways: directly from the dashboard UI or via the API. From the dashboard: Go to the "New Message" tab, enter the phone number in international format (e.g., +212600000000), type your text, select an approved Sender ID, and click send. You will see the delivery status update in real-time. Via the API: Make an HTTP POST request to the `/v1/messages` endpoint with your Bearer Token. The request body must include the recipient phone number, message body, and Sender ID.

Question 3

Sender ID Registration in Morocco

Accepted Answer

In Morocco, sending SMS with a custom sender name (alphanumeric Sender ID, e.g., "MyBrand") is strictly regulated to prevent spoofing and identity theft. Every Sender ID must be registered with all three Moroccan carriers (Maroc Telecom, Orange, inwi). To register, submit a request via our dashboard accompanied by your ICE or RC business registration documents, and a signed authorization letter. Approval typically takes 24 to 48 business hours. Generic Sender IDs (such as "SMS", "INFO", or "ALERT") are systematically rejected by local carriers.

Question 4

Choosing SMS vs. WhatsApp API

Accepted Answer

The choice of channel depends on your message requirements. SMS is perfect for urgent offline alerts because it does not require an active internet connection on the recipient's phone. WhatsApp Business API allows rich media contents (images, documents, interactive buttons) and boasts an engagement rate 5x higher than traditional SMS. Budget-wise, SMS is charged per single unit sent. WhatsApp uses 24-hour conversational sessions initiated by the business, which is often more cost-effective for support or interactive user flows.

Question 5

Business Account Verification

Accepted Answer

For regulatory compliance in Morocco and to prevent spam network abuse, all business accounts must be verified before sending live production traffic. To verify your account, go to the "Settings > Verification" tab and upload: a copy of your ICE or RC business certificate, and a valid ID of the legal representative. Our compliance team reviews submissions within 2 business hours. Once approved, all sandbox limits are removed and your account is ready for production.

Question 6

API Key Security & Management

Accepted Answer

Your EnvoiSMS.ma API key provides full access to your account funds and allows sending messages. Treat it with the same level of security as a password. Never commit your API keys to version control systems or public repositories (like GitHub). Always use secure environment variables (.env) on your production servers. If you suspect your API key has been exposed, generate a new one immediately from the Developer tab in your dashboard. The old key will be revoked instantly.

Question 7

Moroccan Pricing, Taxes & Invoices

Accepted Answer

EnvoiSMS.ma is a Moroccan platform. All prices are denominated in Moroccan Dirhams (MAD) excluding tax. In compliance with Moroccan tax regulations, credit top-ups are subject to the national Value Added Tax (VAT) of 20%. A legal invoice containing the net amount, 20% VAT, and your business details (ICE, RC) is automatically generated after each purchase. You can download this PDF invoice anytime from the "Billing" tab for your accounting records.

Question 8

Supported Payment Methods

Accepted Answer

We offer several convenient payment options tailored to the Moroccan market to fund your balance: 1. Credit Card: Secure online payment processed via CMI (supports both local Moroccan and international cards). Balance is updated instantly. 2. Bank Transfer: Transfer funds to our Moroccan bank account (RIB). Your credits are updated within 24 hours of receiving the transfer. 3. Cash via CashPlus: Generate a payment slip code from your dashboard and pay in cash at any CashPlus branch in Morocco. Credits are added instantly.

Question 9

Do you charge for undelivered messages?

Accepted Answer

Billing depends entirely on the messaging channel used. For SMS: Moroccan telecom carriers charge for every single message submission attempt to the network, regardless of whether the recipient's device is turned off or out of coverage. We follow this carrier rule. However, we do not charge for SMS sent to invalid or malformed numbers that our system blocks before sending. For WhatsApp: Charges are session-based (24-hour window). You are only billed if the conversation-starting message is successfully delivered to the user's handset.

Question 10

API Authentication & Request Format

Accepted Answer

The EnvoiSMS.ma API is a secure REST API. All requests must be made over HTTPS. To authenticate your requests, include your secret API key in the request headers using the Bearer Token format: `Authorization: Bearer YOUR_API_KEY`. Requests must specify the header `Content-Type: application/json` and request payloads must be valid JSON. By default, we apply a rate limit of 60 requests per minute in sandbox, which can be increased for production plans.

Question 11

Sending OTP & Transactional SMS

Accepted Answer

Transactional SMS (such as OTP codes or order updates) require maximum deliverability and sub-second latency. To ensure delivery in less than 2 seconds, send requests to our `/v1/messages` or `/v1/verify` endpoints. Always format Moroccan phone numbers in international format (e.g., +212600000000). Our gateway automatically handles local prefix normalization. Ensure your OTP messages comply with the GSM-7 character set. A standard SMS is limited to 160 characters. Using emojis or non-GSM characters switches the message encoding to Unicode, reducing the limit to 70 characters per SMS segment.

Question 12

Configuring Delivery Webhooks

Accepted Answer

Webhooks allow your application to receive real-time delivery reports (DLR) from Moroccan mobile carriers without polling our API continuously. To set up a webhook, go to the "Webhooks" tab in your dashboard, enter your server's public URL (e.g., https://api.yoursite.com/envoisms-webhook), and select the events to listen to (e.g., `message.delivered`, `message.failed`). Each webhook notification is sent as an HTTP POST request containing a JSON payload with the `message_id`, recipient phone number, delivery status, and timestamp.

Question 13

Securing Webhooks with HMAC

Accepted Answer

To prevent malicious third parties from sending fake delivery notifications to your server, EnvoiSMS.ma cryptographically signs every webhook request. We append an `X-EnvoiSMS-Signature` header to every outgoing POST request. This signature is calculated using the HMAC-SHA256 algorithm with the raw request body and your secret API key as the shared secret. On your server, you should compute the HMAC-SHA256 hash of the received raw request body using your API key and verify that it matches the header signature before processing the event.

Question 14

WooCommerce SMS Integration

Accepted Answer

Notifying your customers via SMS about their order status is an effective way to decrease checkout abandonment and build trust for e-commerce stores in Morocco. To connect EnvoiSMS.ma with WooCommerce, use our official plugin or hook into WordPress actions (e.g., `woocommerce_order_status_completed`) via your theme's `functions.php` using standard cURL requests. Set up clean automated notifications: purchase confirmation, shipping alerts containing local tracking links, and customer OTP validations during registration.

Question 15

Why are my SMS not delivered?

Accepted Answer

When an SMS fails to reach a recipient, our console displays the exact delivery status reported by the local carrier. PENDING status: The message reached the carrier network but cannot be delivered to the handset yet. Common reasons include: device turned off, out of network coverage, or full SIM SMS inbox. The carrier will retry delivery for 48 hours before marking the message as expired. FAILED status: The carrier rejected delivery. Common causes are: invalid or inactive phone number, unrecognized Sender ID, or spam filtering blocks.

Question 16

Carrier Filtering & Anti-Spam Rules in Morocco

Accepted Answer

Moroccan telecom carriers enforce strict spam filtering algorithms to protect consumers from unsolicited commercial messages. Sending Windows: Promotional and marketing SMS inside Morocco are prohibited during night hours (typically between 9:00 PM and 8:00 AM) and on official national holidays. Marketing SMS sent during these hours will be queued or blocked. CNDP Compliance: All marketing broadcasts must contain a clear opt-out mechanism (such as "STOP SMS" text). Sending promotional campaigns without an opt-out choice violates personal data protection laws and risk permanent blocking of your Sender ID.

Question 17

Error 1: Unknown Subscriber / Invalid Number

Accepted Answer

Error 1 is returned directly by the recipient's carrier database (IAM, Orange, or inwi) when the requested number is not recognized on their network registry. Common causes: The customer mistyped their phone number, the number points to a landline phone (cannot receive standard SMS), or the mobile subscription has been terminated and deactivated. Action: Clean your contact lists and remove this phone number immediately to avoid spending credits on delivery attempts that will always fail.

Question 18

Error 2: Absent Subscriber / Device Unavailable

Accepted Answer

Error 2 indicates that the carrier tried to locate the subscriber's device on the cellular network but received no response. Common causes: The recipient's handset is switched off, set to airplane mode, or currently located in an area with zero signal coverage. Behavior: This error is only finalized after the carrier's retry window expires (usually 48 hours). During this period, the message stays in Pending state. If the handset is turned on or reconnects to the network within 48 hours, the SMS is successfully delivered.

How can we help you?

Popular questions

Getting Started

Developer & API

Delivery & Troubleshooting

Cannot find what you need?