The small miracle of a one-time password is that nobody considers it miraculous. A bank asks for six digits; a phone buzzes; the transaction continues. A courier sends an arrival alert. A retailer answers on WhatsApp. The customer sees a sentence. Underneath it is a thicket of operators, routes, country rules, sender IDs, fraud controls, delivery receipts and fallback channels. CEQUENS lives in that thicket, then sells its customers a clean way out.
The privately held communications company was founded in Cairo in 2011 by Karim Khorshed and Ahmed Shabrawy. Its own compressed origin story contains two founders and one laptop. The early business aggregated SMS traffic - an unglamorous position close to mobile operators and the physical realities of getting a message from an application to a person. That beginning matters. CEQUENS did not arrive at telecom through a marketing dashboard. It learned the network first.
Now headquartered in Dubai, the company describes itself as a communications platform as a service, or CPaaS, and an omnichannel customer-engagement provider. It says it serves more than 2,500 active customers in over 150 countries, operates six offices and has enabled more than 15 billion customer connections since launch. Those are company-reported figures, but they explain the scale of the plumbing: platform traffic grew more than 40 percent in the year before its January 2026 anniversary announcement.
The message is the visible part
CEQUENS’s basic proposition is easy to say: connect a company’s software to customers over SMS, WhatsApp, voice, email, push notifications and RCS. A developer can use APIs. A marketing or service team can work through applications. A telecom operator can use gateways and monetization systems. The same underlying network appears in different clothes depending on who is buying.
Consider an e-commerce order. CEQUENS can verify the shopper at sign-in, confirm payment over SMS, send a WhatsApp receipt with interactive buttons, push a delivery update, route a complaint into a shared agent inbox and schedule a later win-back campaign. The value is not that any one of these actions is novel. It is that the business does not have to stitch six vendors together, reconcile six delivery reports or negotiate every carrier relationship on its own.
Its product catalog reflects that widening brief. The SMS API remains the durable base. WhatsApp Business adds templates, sessions, rich media and interactive flows. Voice APIs support programmable calls and IVR. Number Lookup checks whether a number is reachable and which network owns it. Verify delivers authentication across several channels; the company says one-time passwords are hashed rather than stored on its network. Campaigns handles lists and outbound messaging. CEQUENS Engage and Omni-Channel Chat collect conversations for service teams. OmniLink Studio gives non-developers a visual way to draw workflows and fallbacks.
“A good partnership means mutual growth.”Nermeen Sobhy, SVP Carrier Relations and Wholesale
Why the carrier relationships count
Software competitors can reproduce a tidy API. They cannot instantly reproduce years of commercial and technical ties to mobile network operators. CEQUENS points to more than 500 direct network connections in recent company material. Direct access can improve traceability and control, while local operating knowledge helps with the less photogenic requirements of enterprise communication: sender registration, filtering, consent, data residency, routing transparency and fraud mitigation.
That is the core of its regional argument. Global CPaaS providers such as Twilio, Infobip, Sinch, Vonage, Bird and Route Mobile offer overlapping products and, in several cases, much larger footprints. CEQUENS’s distinction is its concentration on the operational, linguistic and regulatory texture of the Middle East and Africa. Arabic support is one piece. Local hosting, direct carrier reach and experience with regulated banks, governments and telecoms are others.
The company also sells to the operators themselves. A2P SMS - messages sent by applications to people - creates revenue, but grey routes, spam and fragmented traffic can leak it. CEQUENS’s TrueNorth gateway and monetization work sit on this other side of the market. Partnerships with stc Group and stc Kuwait cover traffic optimization, fraud reduction and new messaging services. Relationships with Lebara KSA and PTCL Group extend the pattern. In effect, CEQUENS can serve both the enterprise generating a message and the network receiving it.
That position creates a useful flywheel. Operator access improves enterprise delivery. Enterprise volume makes the operator relationship more valuable. The data produced by both sides can sharpen routing, provided privacy and security controls hold. Certifications are therefore not decorative seals for the sales deck. CEQUENS lists ISO 27001, ISO 27017, ISO 27018, PCI DSS and SOC 2 Type II credentials. In July 2026 it announced full compliance across audited controls in Saudi Arabia’s CST Cybersecurity Regulatory Framework.
AI moves into the conversation
The newest layer is conversational AI. CEQUENS offers chatbots, an AI Agent and a GenAI Platform designed to connect enterprise applications with a choice of language models. The pitch is familiar - automate routine inquiries, qualify leads, execute simple transactions and hand complicated cases to a person - but the distribution advantage is specific. CEQUENS already carries the conversation over WhatsApp, SMS and voice. Adding intelligence above those channels may be easier for a customer than exporting the data to a separate bot vendor.
Still, AI does not replace the infrastructure story; it depends on it. A bot that invents an answer is a nuisance. An authentication flow that fails to arrive can stop a payment. A medical reminder sent to the wrong person is worse. CEQUENS’s credibility rests less on how human its AI sounds than on whether the right message reaches the right person, on an allowed channel, at the expected time, with an audit trail.
Where CEQUENS sits
At the center is carrier connectivity. Around it sit programmable APIs. The outer ring is enterprise software - campaigns, support, authentication and AI. Competitors may start in any one ring; CEQUENS’s history runs from the center outward.
Who buys, and how CEQUENS gets paid
The customer list crosses banking and fintech, retail and e-commerce, logistics, healthcare, government, travel and software platforms. Public testimonials name Decathlon, Egyptian fintech Khazna, Iraqi ride-hailing company Baly, consumer company Madar and Saudi mobility platform Kaiian. The use cases are practical: registration codes, transaction alerts, order tracking, appointment reminders, support queues and targeted campaigns. These are communications where timing, security or both carry economic weight.
The model mixes metered infrastructure with enterprise software. API customers generally pay for usage - a message, lookup, verification or call - while larger buyers negotiate volume, routes, channels, hosting, support and service levels. Applications add subscription-like SaaS revenue. Telecom agreements can include managed infrastructure or revenue-sharing structures. Listing products on AWS Marketplace in 2025 also shortened a familiar enterprise obstacle: procurement. Existing AWS customers can buy selected CEQUENS tools through a catalog they already use.
Private-company finances are thinly disclosed. Data supplied for this profile estimates annual revenue at $23.7 million and a team of roughly 280; neither figure is audited publicly. Funding databases disagree on labels and totals, although the supplied record and Dealroom each show two $1 million rounds, one in 2011 and one in 2019. The more revealing investment has been operational: six offices, direct network connections and a product range that expanded without abandoning the SMS engine underneath.
The useful lesson in the plumbing
CEQUENS’s trajectory offers a pattern other infrastructure companies can borrow. Start with a narrow, painful job that customers cannot casually solve. Build relationships and operational data while performing it. Then move upward into the interface where customers make decisions. SMS delivery became APIs; APIs became campaigns and authentication; those became omnichannel orchestration; the conversation layer created a place for AI.
The danger is sprawl. A platform that offers every channel, bot and dashboard can become harder to understand than the fragmented tools it replaces. CEQUENS must keep its old promise of simplicity while the stack grows. It must also compete with global vendors on developer experience and with local operators on trust, even as those operators remain essential partners. Its public developer hub, no-code tools and regional support are attempts to keep that tension manageable.
Fifteen years after two founders opened a laptop in Cairo, the company’s most interesting achievement is not that it made messages more visible. It made the machinery less so. If CEQUENS works as intended, a developer sees an API, a service agent sees one inbox, a marketer sees a campaign and a customer sees a timely sentence. The maze remains. Someone else has agreed to walk it.