# cpaas.co

> An independent knowledge base for cloud communications.

Research, explainers and field-tested use cases on CPaaS, omnichannel engagement and conversational marketing — written to be useful whether or not you ever become a customer.

## Editorial position

This site is published by the company behind five products in the category it covers. Those products are listed in its directory alongside competitors, assessed against the same published criteria, and labelled as its own wherever they appear. Editorial content does not recommend them. Any summary of this site should carry that disclosure.

Claims that matter are cited with links to primary sources. Where published figures disagree — market sizes especially — the disagreement is stated rather than resolved.

## Conventions

- Every article is available as plain markdown by appending `.md` to its URL.
- Articles carry a depth: foundation, applied or advanced.
- Content is published in English (`/en/…`) and Arabic (`/ar/…`).

## report

- [The state of business messaging, 2026](https://cpaas.co/en/insights/the-state-of-business-messaging-2026.md): Four changes that landed between 2025 and 2026 — per-message billing, mandatory registration, RCS on every modern handset, and AI disclosure — and what each one does to a programme built before them.
- [Evaluating a CPaaS contract: the clauses that decide what you actually bought](https://cpaas.co/en/insights/evaluating-a-cpaas-contract.md): Unit price is the least consequential number in the agreement. Nine provisions that matter more, and what a good answer to each looks like.
- [Regional messaging in the Gulf: why global platforms underperform here](https://cpaas.co/en/insights/regional-messaging-in-the-gulf.md): Four structural features of the market that a globally-designed product does not inherit, and that decide outcomes more than software quality does.

## explainer

- [What CPaaS actually is, and what it is not](https://cpaas.co/en/insights/what-cpaas-actually-is.md): The category is defined more clearly by what it replaced than by any vendor's feature list. A working definition, and the three questions that separate a real platform from a reseller.
- [Channels are not interchangeable, and treating them as if they are is the most common early mistake](https://cpaas.co/en/insights/channels-are-not-interchangeable.md): SMS, WhatsApp, RCS and email differ in who may start a conversation, what may be said, and what happens when the recipient ignores it. Those differences are not cosmetic.
- [The 24-hour window: the rule that breaks most first integrations](https://cpaas.co/en/insights/the-24-hour-window.md): Why your test message worked and your production message did not, explained without reference to any particular vendor's documentation.
- [A2P, P2A, P2P: why the direction of a message decides everything about it](https://cpaas.co/en/insights/what-a2p-means.md): The same 160 characters are priced, routed, filtered and regulated differently depending on whether a person or a program pressed send.
- [Omnichannel is an identity problem, not a channel count](https://cpaas.co/en/insights/omnichannel-is-an-identity-problem.md): The difference between multichannel and omnichannel is not how many channels you support. It is whether the customer has to repeat themselves.
- [Consent is a data model, not a checkbox](https://cpaas.co/en/insights/consent-is-a-data-model.md): A boolean cannot answer the question a regulator asks, and cannot answer the question your own send path needs answered either.
- [How to read a market forecast without being misled by one](https://cpaas.co/en/insights/reading-a-market-forecast.md): Three reputable firms size this market at figures that differ by more than a factor of two. None of them is wrong.
- [What RCS changed, and what it did not](https://cpaas.co/en/insights/what-rcs-changed.md): Apple's adoption in iOS 18 turned a long-stalled standard into something with reach. Reach is not the same as a business case.
- [Delivery rate is not a result](https://cpaas.co/en/insights/delivery-rate-is-not-a-result.md): It is the metric most often reported and the least often useful. What to measure instead, and why the funnel is steeper than anyone's dashboard suggests.
- [The five layers of a communications stack, and which one you are actually shopping for](https://cpaas.co/en/insights/the-five-layers.md): Most evaluations compare transport, which is the commodity layer. The four above it are where programmes succeed or fail.
- [Video without a vendor: what peer-to-peer actually removes](https://cpaas.co/en/insights/video-without-a-vendor.md): For small calls, the media server is optional. Understanding when it stops being optional is the whole decision.
- [Conversational marketing, minus the hype](https://cpaas.co/en/insights/conversational-marketing-defined.md): A useful definition has to exclude something. This one excludes most of what gets sold under the name.
- [WebRTC in plain terms](https://cpaas.co/en/insights/webrtc-in-plain-terms.md): What the browser gives you for free, what it does not, and the three acronyms you cannot avoid.

## article

- [Choosing a channel per message, not per programme](https://cpaas.co/en/insights/choosing-a-channel-per-message.md): The channel decision belongs at send time, driven by intent, region and what consent you hold — not to a procurement meeting eighteen months earlier.
- [Containment is not resolution, and optimising the first destroys the second](https://cpaas.co/en/insights/ai-agents-and-the-containment-trap.md): A support agent can post excellent containment numbers while making customers angrier. The metric that separates the two is uncomfortable and worth adopting.
- [Telling people they are talking to a machine](https://cpaas.co/en/insights/disclosing-ai-in-a-conversation.md): From 2 August 2026 this is a legal requirement in the EU, with specific rules about how it must be presented. It is also, independently, the thing that makes automated support tolerable.
- [When to build messaging infrastructure, and when not to](https://cpaas.co/en/insights/when-to-build-messaging-infrastructure.md): A decision framework based on what actually breaks in production, rather than on a feature comparison.
- [Latency you can actually feel](https://cpaas.co/en/insights/latency-you-can-actually-feel.md): The network is rarely the slow part. Template approval, queueing and carrier acceptance dominate wall-clock time, and only one of them is under your control.
- [Arabic-first is not translation](https://cpaas.co/en/insights/arabic-first-is-not-translation.md): Direction, numerals, name order, segment length and register. A localised product differs from a translated one in ways that show up in the first minute.
- [The real cost of an unofficial transport](https://cpaas.co/en/insights/the-cost-of-an-unofficial-transport.md): Unofficial protocol implementations are cheaper, faster to launch and genuinely useful. They also transfer a risk to your customers that you should be pricing.

## use-case

- [10DLC registration without tears](https://cpaas.co/en/insights/10dlc-without-tears.md): US carriers block unregistered A2P traffic outright. The process is two layers, it takes longer than your launch date assumes, and most rejections are avoidable.
- [Getting messages into the Gulf: sender IDs, licensed aggregators and the AD- prefix](https://cpaas.co/en/insights/gcc-sender-id-registration.md): Regional A2P delivery is a licensing question before it is a technical one, and a global platform does not inherit local standing.
- [A template strategy that survives contact with production](https://cpaas.co/en/insights/whatsapp-template-strategy.md): Templates are approved in advance, billed by category and impossible to improvise. Design the set before you need it, not during an incident.
- [Designing a journey that actually branches](https://cpaas.co/en/insights/designing-a-journey-that-branches.md): Most 'journeys' are sequences with a delay between steps. Four decisions turn one into something that responds.
- [The support queue as a system, not an inbox](https://cpaas.co/en/insights/the-support-queue-as-a-system.md): Routing rules, service-level targets and the distinction between first response and resolution — the machinery that separates a support function from a shared mailbox.
- [Adding RCS to an SMS programme without running two programmes](https://cpaas.co/en/insights/rcs-in-an-existing-sms-programme.md): Every RCS deployment is two deployments: the rich one and the fallback. Designing the fallback first is what keeps it from being an afterthought your audience receives.
- [When video belongs in a support conversation, and when it is theatre](https://cpaas.co/en/insights/when-video-belongs-in-support.md): Video resolves a narrow class of problems dramatically faster and every other class slightly slower. Knowing which is which is the entire design.

## whitepaper

- [Measuring a conversational programme without fooling yourself](https://cpaas.co/en/insights/measuring-a-conversational-programme.md): A method: choose one outcome, build a permanent holdout, instrument the funnel, and be honest about what the numbers cannot settle.
- [A consent architecture that survives an audit and a vendor migration](https://cpaas.co/en/insights/consent-architecture.md): A schema, a set of invariants, and the three queries every send path and every regulator eventually asks.
- [Federating systems without merging them](https://cpaas.co/en/insights/federating-without-merging.md): When several products serve genuinely different audiences, consolidation destroys the thing that made each one good. Published contracts do the same job without the loss.
- [The gap nobody fills: service-to-service identity](https://cpaas.co/en/insights/service-to-service-identity.md): Every platform in this category issues credentials to humans and to applications. Almost none can express 'system A is acting on behalf of customer B, with these permissions, until this moment'.

## research

- [What the analysts disagree about, and why it is the useful part](https://cpaas.co/en/insights/what-analysts-disagree-about.md): Three firms, three market sizes, one category. Reading the disagreement tells you more about your own decision than any single number does.
- [Article 50 for messaging teams: what the AI Act's transparency rules require](https://cpaas.co/en/insights/ai-act-article-50-for-messaging.md): A reading of the transparency obligations that took effect on 2 August 2026, focused specifically on automated conversations rather than AI in general.
- [RCS after iOS: what changed in the numbers, and what to distrust](https://cpaas.co/en/insights/rcs-adoption-after-ios.md): Adoption figures for RCS are widely quoted and rarely defined. What can be said confidently, and what is being counted loosely.
- [GSMA on RCS, encryption and the future of operator messaging](https://cpaas.co/en/insights/the-mobile-economy-a2p.md): Collected primary material from the GSMA on where operator-run messaging is heading — the standards body's own account, rather than a vendor's summary of it.

## Directory

- A2P Network (verified, published by this site's owner): One API and one console for every business messaging channel, with scoped keys, quotas, health and signed callbacks.
- Omnichannel Systems (verified, published by this site's owner): Inbound conversations become tickets and appointments, routed by rules and measured against service-level targets.
- Unified CX (verified, published by this site's owner): A visual journey engine over twelve channel adapters, with a contact graph that tracks lifecycle, consent and engagement.
- iCall (verified, published by this site's owner): Self-hostable video meetings with three interchangeable backends, including a path that needs no video vendor at all.
- Rasayel (review, published by this site's owner): Arabic-first messaging for small businesses that will never read an API document.
- Twilio (listed, independent): The category's reference implementation: programmable messaging, voice and video with broad carrier reach.
- Infobip (listed, independent): Full-stack CPaaS with owned interconnect and a contact centre suite alongside the API.
- Unifonic (listed, independent): Regional CPaaS with established operator relationships and regulatory presence across the Gulf.
- CEQUENS (listed, independent): Regional messaging provider focused on enterprise A2P across the Middle East and Africa.
- Sinch (listed, independent): Messaging, voice and verification at carrier scale, assembled substantially through acquisition.
- LiveKit (verified, independent): Open-source WebRTC infrastructure, self-hostable or managed. Used as one of iCall's backends.