EnvoiSMS wasn't born in a boardroom. It came out of daily friction: reaching a customer in Rabat meant going through platforms that knew neither our carriers, nor our currency, nor our people. We ended up building here what we had been renting elsewhere.
We were already running businesses in Morocco — e-commerce, healthcare, B2B services — and every day brought the same friction: verification codes arriving a minute too late, sender names blocked without explanation, invoices in euros at international rates. To global platforms, Morocco was a row in a coverage table. To us, it was the country where the people we served actually lived.
In early 2026 we stopped waiting for someone else to build it. We built our own gateway: optimized routing to Maroc Telecom, Orange and inwi, priority queues for OTP codes, automatic provider failover when a route degrades, real-time carrier delivery receipts. First for our own products — then for every team hitting the same wall.
A small team operates a full platform out of Casablanca — SMS, WhatsApp Business, OTP verification, campaigns — and remains its first user: every login code from our own products goes through the same API everyone else uses. When a route degrades, we see it in our own products before we read it in a ticket.
Nothing we build for Morocco is specific to Morocco. The same wall stands in Dakar, Abidjan, Lagos and Tunis: routes detoured through another continent, prices quoted in someone else's currency, rules written elsewhere. We move country by country, starting with the one we know best — so that when a team in Dakar hits the same wall, the road is already open.
A message from Casablanca to Rabat has no business detouring through Europe. We route traffic as close to the carriers as possible — IAM, Orange, inwi — with native +212 normalization, public pricing in dirhams and Moroccan invoices. Morocco is not a cell in a global rate card: it is where this starts.
Every route is monitored around the clock, canary tests run day and night, and traffic fails over automatically when a route degrades. Our status page is public — including when the news is bad. We don't promise zero incidents: we measure, we publish, we fix.
Public prices in dirhams, no mandatory subscription. Every message is logged with its exact cost, your balance updates in real time, and a message that fails at the carrier is re-credited automatically. An EnvoiSMS invoice can be read without a magnifying glass.
SMS only works if Moroccans keep opening them. We screen for phishing before sending, enforce STOP opt-outs automatically, and operate within Law 09-08 and CNDP requirements. Refusing a dubious campaign protects the trust every other message depends on.
An API you can integrate in fifteen minutes, documentation that tells the truth, HMAC-signed webhooks, PHP, Node.js and Python SDKs, and a free test mode. And because your tools are changing: a native MCP server so your AI agents can send messages without duct tape.
The platform exists in French, English, Spanish and Arabic. When a page isn't translated yet, we don't publish a machine-generated stand-in: a missing translation is better than a betrayed one.
Every message sent in Morocco should arrive fast, at a fair price, with respect for the person receiving it — and without leaving the continent to get there.
Our own products run on this API. Every OTP from our platforms goes through the same queue as yours — a problem is impossible to ignore.
In French, Arabic or English, you talk to people who operate the platform — not a script. Based in Casablanca, on Moroccan hours.
Real-time status, incident history, a public changelog: the platform evolves in daylight.
See live statusCreate an account in two minutes, or write to us — a member of the team answers, in French, Arabic or English.
5 MAD of free credit · No commitment · No credit card