Learn · every claim sourced
Understand CPaaS, step by step
Plain-language guides, use cases and research from the community, with a source for every claim. New here? Begin with the five short reads below.
The library
In-app chat 101: conversations inside your own product
In-app chat puts messaging inside your own mobile or web app through an SDK: support chat between customers and your team, and chat between your users in marketplaces and communities. You keep the context, the design and the data, and you also take on what platforms usually carry for you: moderation, safety and data rules.
Push notifications 101: alerts people allowed
Push notifications are short alerts from your own app or website, carried by the platforms' notification services (Apple's APNs, Google's FCM, Huawei's Push Kit and the browsers' push services). Sending is free or nearly free; the real price is permission, which people can refuse or withdraw at any time.
Consent is a data model, not a checkbox
A single yes/no field cannot answer the questions a regulator or a customer will ask — when, for what, on which channel, and how. A simple ledger can, and it keeps more customers reachable.
The five layers of a communications stack, and which one you are actually shopping for
Most evaluations compare transport — getting a message to a phone — which is the commodity layer. The four layers above it are where programmes succeed or fail, and where switching gets expensive.
Peer-to-peer video: what it removes, and what it does not
For small calls, a media server is optional. When it stops being optional — and what a hosted video service gives you in exchange for its price — is the whole decision.
WebRTC in plain terms
What the browser gives you for free, what it does not, the three acronyms you cannot avoid, and where the real costs and support load sit.
Choosing a channel per message, not per programme
The channel decision belongs at send time, driven by intent, region, consent and where the person actually reads — not to a procurement meeting eighteen months earlier.
When to build messaging infrastructure, and when not to
A layer-by-layer decision framework based on what actually breaks in production and who is accountable for it, rather than on a feature comparison.
Latency you can actually feel
For messages, the network is rarely the slow part: queues, carriers and handsets dominate, and most of it is chosen at purchase. For live calls, a few hundred milliseconds decides whether a conversation feels natural.
The support queue as a system, not an inbox
Ownership, state, two clocks, routing that survives staff changes, and the ways messaging channels break email-era ticketing — the machinery that separates a support function from a shared mailbox.
A consent architecture that survives an audit and a vendor migration
A schema, a set of invariants, and the three queries every send path and every regulator eventually asks.
Federating systems without merging them
When several products serve genuinely different audiences, consolidation can destroy what made each one good. Published contracts can do the same job with less loss, at a real operational cost.
The gap nobody fills: service-to-service identity
Messaging platforms issue credentials to people and to applications. Few can express 'system A is acting on behalf of customer B, with these permissions, until this moment'.