Updated 3 min read

SMS or push notification: which converts the best in Morocco

SMS vs push notification: honest comparison, factual criteria and clear recommendation according to your case.

You have just launched your start-up’s new mobile app in Morocco. The development has cost you hundreds of thousands of dirhams. One of the first requests from your marketing team is obvious: *”Let’s stop paying for sending SMS campaigns, let’s use free push notifications on iOS and Android to get our users back!”*

The calculation seems unstoppable. Mobile Push Notification (FCM/APNs) is technically free (without infrastructure costs), visually rich, and native. Yet, a few months later, the conversion stagnates and you are forced to return to the SMS API. Why does what was meant to kill the SMS not do it in Morocco?

Opt-in push problem: many users reject it

The Achilles heels of push notification is the friction of acquisition (The famous "Opt-In").

For a customer to receive a Push, it is necessary to align the stars: 1. he must have an iOS or Android smartphone. 2. he must search and download your app (more than 80% of users uninstall a non-vital app after 3 months). 3. upon first opening, he must click on "Allow notifications".

According to global statistics for the mobile industry (Airship, Urban Airship), the Push opt-in rate ranges around 40% to 50%. This means that out of 10,000 people who have installed your app (a figure already difficult to reach), you have the legal and technical ability to contact only 5,000 of them.

The universal reach of SMS: no app required

In contrast, the power of SMS lies in its standardization by telecom operators (IAM, inwi, orange).

  1. No installation: If you have the valid telephone number of the customer (and his/her CNDP consent to be contacted you can reach him/her instantly on his/her native app "Messages".
  2. No system blocking: There is no pop-up "The operator wants to send you notifications". The SMS is enabled by default at 100%.
  3. Passive visibility: In Morocco, SMS is perceived as urgent.The opening and reading rate often reaches 98% within the first 5 minutes.

Cost and Deliverability: The Real Battle

The Push: Push sending via Firebase Cloud Messaging is free, but its delivery is highly unstable. Android phones (especially the most popular brands in Morocco such as Xiaomi, Oppo or Huawei) have aggressive energy-saving system layers that “keep” the app in the background. The result: you send an urgent push, but the customer will only receive it the next day when he opens the app manually. The latency is unpredictable.

The SMS (A Per-Message Cost for Confirmed Delivery): The SMS has a variable cost (e.g. 0.65 MAD per message, Starter rate with a validated Sender ID).It is a corresponding budget (OpEx).But the SS7 gateway’s Delivery Report confirms that the phone received it.

Use cases: when to combine the two channels (Fallback)

If the SMS consistently converts louder into absolute mass, don’t throw the push away (it’s still great for an ultra-engaged daily user).

The strategy of the leaders of the Food-Delivery or VTC in Morocco (Glovo, Yango) is the Smart Fallback (La Cascade), managed by the backend:

  1. Your system is trying to send the transaction alert (“Your delivery is down”) by Push Notification.
  2. Your server monitors Firebase’s recognition.
  3. If Firebase does not return a read confirmation after 30 seconds, or if the user has not enabled Push, the backend automatically triggers a WebHook SMS via an external API to ensure that the customer does not forget his order.

This architecture reduces SMS billing by approximately 40% (supported by the free Push), while guaranteeing a 100% conversion on critical alerts (supported by the Fallback SMS).

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.