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
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.
Containment is not resolution, and optimising the first destroys the second
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
Since 2 August 2026 this is a legal requirement in the EU, and similar rules exist elsewhere. It is also, independently, what makes automated support tolerable. One line, in the right place, does it.
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.
Arabic-first is not translation
Using Arabic as the worked example: direction, numerals, names, SMS encoding and register. A localised product differs from a translated one within the first minute — and the same checks apply to any right-to-left or non-Latin-script audience.
The real cost of an unofficial transport
Unofficial protocol implementations are cheaper, faster to launch and genuinely useful. They also transfer a risk to the business using them that should be priced and disclosed.